react-storybook-jsx-starter-kit

react-storybook-rollup-starter-kit

This project is to be used as a template/starter-kit for building React components library using Storybook to document the components and Rollup to build the library for consuption.

This project is bootstrapped with the following

• Create React App
• React Scripts v.3.1.0
• Storybook/react v.5.1.10
• Rollup v.1.19.4
• Airbnb esint config v.18.0.0

Getting Started

In order to get started using the setup, download/pull/fork the repository and start building your components under /src/components.
Each component you create should follow the same setup as per the <Button /> component, where each has:

• .js file for the source code

• .module.scss file for the scss

• .spec.js file for the tests

• stories.js file for including the storybook story for the docs

• index.js file to export the component

• src/components/inde.js file to include all components to be exported

The above configuration is needed to ensure both storybook and rollup are correctly executed.

Available Scripts

In the project directory, you can run:

yarn start and yarn storybook

Runs storybook.
Open http://localhost:6006 to view it in the browser. The page will reload if you make component edits.

yarn lint

Runs airbnb linting config.
Please refer to .eslintrc for more details in rules that are excluded/added from the initial Airbnb configuration, which can be found here

yarn test

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

yarn build

Builds the component library using rollup.
This runs a set of defined configurations under rollup.config.js file.
The exports are built inside build folder which can be used to publish to npm ecosystem.

yarn build-storybook

Builds static files for storybook site. This is so it can be deployed as the docs source for the component library.

Next steps

It is left to the development team who is utilising this starter kit to:

• Modify the project name in package.json to contain your library name and decide where the library will be hosted in the cloud and accordingly include the correct npm credentials/scope into the .npmrc (e.g hosting platoform: npmjs)

• Decide on their releasing strategy and fully use the Semantic Versioning and adding corresponding trace of changes in the CHANGELOG.md file using the Keep a Changelog Method