Notice: You will need to use Node version 6.0 or higher. Verify that you have yarn enabled — if not install yarn globally. These web components are written in ES6 and build routines compile to es5 to encompass more browsers.
$ git clone [email protected]:EberlyODL/EberlyWC.git
$ cd EberlyWC
$ yarn install
$ yarn start$ yarn start- Launch a demo server. This should be continuously running as you develop.
$ wcf element- Create a new component.
$ yarn run rebuild-wcfcache- Rebuild caches as to what web component libraries can be used
$ yarn test- Run tests on ALL EberlyWC.
$ yarn run build- Run build on ALL EberlyWC.
$ yarn run storybook- Run storybook
$ yarn run build-storybook- Build storybook for deployment
$ lerna publish- Publish ALL EberlyWC' elements to npmjs.com
$ lerna run build --no-bail- Run
buildcommand in all projects in the repo, don't bail if there's an issue
- Run
Because this is a monorepo, each web component will need to be independently built in order to actively work on and preview the changes. Every web component has its own Gulp file and Yarn/NPM script.
While still running yarn start in one terminal window (which runs the local server), you will need to open another terminal window, drill into the directory of the web component you'd like to work on, and execute the yarn start command. This command will use gulp tasks to watch the files within that web component directory and will automatically re-run the build command and refresh the browser when you make changes to the web component.
Run wcf element to make a new element. Go to the new element following the directions generated at the end of the element's creation. To work on the new-element run yarn start from it's directory. If you are pulling in another element to use, run yarn add projectname --save.
$ cd /Sites/EberlyWC
$ yarn start
# SHIFT + CTRL + T to open a new tab in Terminal
$ cd elements your-card # or any other web component
$ yarn run devMake a change to the web component and save. The gulpfile will handle transpiling the element down to ES5 and will bring in the HTML and Sass into the template in the web component.
To test all EberlyWC, run yarn test from the root of the repo. If you only want to test the web component you're working on:
$ cd elements/your-card
$ yarn testAlso, if your tests are failing and you want access to a live browser to investigate why, the following flag will keep the browser open.
$ yarn test -- -pThen open the URL that will be printed in the terminal. It looks something like this: http://localhost:8081/components/@@eberlywc/EberlyWC/generated-index.html?cli_browser_id=0.
We've added Storybook to EberlyWC as a way to preview our web components as they are being developed. We'll also use Storybook to export a static site that will be the demo site for EberlyWC.
To run storybook
$ yarn run storybookThis will start a web server on port 9001. Navigate in your browser to http://localhost:9001 to see Storybook in action. Storybook will watch for file changes and reload the browser automatically for you. This is a little slow at the moment, but we'll look into speeding this up.
To export the storybook static site
$ yarn run build-storybookThis places a build of the storybook site in the .storybook_out directory.
For any web component that has a third-party dependency you will need to update the /.storybook/webpack.config.js file. You will need to create an alias for your depedency.
For example:
"../../whatwg-fetch/fetch.js": path.join( // this is the third-party dependency in the EberlyWC
__dirname,
"../node_modules/whatwg-fetch/fetch.js" // this is where it lives in node_modules
)