The use of Bower for dependencies is not sanctioned in Origami v2. Use npm with webpack or browserify instead.
|React||Fast-rendering, composable client-side components.||Powering Up with React|
|React Intl||API to handle translations, format dates, numbers, and strings.|
|Webpack||Bundles npm packages and our JS into a single file. Includes source maps and hot reloading via webpack-dev-server.||Quick Webpack How-to Pluralsight Course|
|Mocha||Automated tests with expect for assertions and React Test Utils for DOM testing without a browser.||Pluralsight Course|
|SCSS||Compiled CSS styles with variables, mixins, and more.||Pluralsight Course|
|npm Scripts||Glues all this together in a handy automated build.||Pluralsight course, Why not Gulp?|
This archetype includes a working example component that puts the above to use.
To hook up your project to Origami continuous integration, a one-time manual process is currently required.
GitHub repositories will integrate with Travis CI, which will publish to the public scope in Pearson's npm organization.
BitBucket repositories will integrate with Solano CI, which will publish to the private scope in Pearson's npm organization.
See the project working before changing anything!
In your local repo:
npm install npm run dev
Navigate to: localhost:8081/demo
Webpack serves your component in memory when you
npm run dev. No physical files are written. When the component is
npm run build, physical files are written to /build.
Additionally, Hot Module Replacement is activated in the webpack dev server; saved changes to /src are automatically reloaded in the browser. Changes to the demo/index.html itself, however, do require a manual page refresh.
npm run build
It is also enabled for the following options:
shallow rendering with React's test utilities
Rendering a component into a detached DOM node in the document, using jsdom
Linting will run automatically prior to executing the test suite.
Determine if your component passes a series of checks for Origami v2 compliance.
npm run verify
It is expected that applications will pass in translated text for dynamic content, and your component simply needs to render whatever is passed in.
For text inherent to the component (e.g. button text or input placeholder), add JSON translations for each supported
locale to the translations folder, and use the
locale configuration parameter.
For public packages only, add the following npm script to the package.json:
"postpublish": "npm access public && echo 'Package scope set to public!'"
Do not manually version or tag your project. Instead, when you are ready to publish an update to npm, manually invoke the release script in the master branch. It handles all of that and invokes CI publishing to npm on behalf of the pearson-ux account.
Additionally, there is no need to manually maintain a change log - if you follow the commitizen conventions for commit messages, a change log will automatically be generated during the release process.
Finally, before you run the following command, ensure that you don't have to manually authenticate every time you perform a network operation with Git.
npm run release
Source maps are enabled for the webpack dev server. Using Chrome dev tools - open the "Sources" tab, navigate to
top/webpack://./, and you will find the original source files for which you can set breakpoints in Chrome's debugger.
Optionally, install React developer tools for additional React debugging support in Chrome dev tools under the "React" tab.