Congrats! You just saved yourself hours of work by bootstrapping this project with Rollup. Let’s get you oriented with what’s here and how to use it.
This setup is meant for developing React component libraries (not apps!) that can be published to NPM. If you’re looking to build a React-based app, you should use
create-react-app,razzle,nextjs,gatsby, orreact-static.
If you’re new to TypeScript and React, checkout this handy cheatsheet
Rollup scaffolds your new library inside /src, and also sets up a CRA-based playground for it inside /example.
The recommended workflow is to run Rollup in one terminal:
yarn start # or yarn startThis builds to /es and runs the project in watch mode so any edits you save inside src causes a rebuild to /es.
Then run either Storybook or the example playground:
Run inside another terminal:
yarn storybookThis loads the stories from ./stories.
NOTE: Stories should reference the components as if using the library, similar to the example playground. This means importing from the root project directory. This has been aliased in the tsconfig and the storybook webpack config as a helper.
Then run the example inside another:
cd example
yarn install # to install dependencies
yarn start # or yarn startThe default example imports and live reloads whatever is in /es, so if you are seeing an out of date component, make sure Rollup is running in watch mode like we recommend above. No symlinking required, we use aliasing.
To do a one-off build, use yarn build.
To run tests, use yarn test.
Code quality is set up for you with prettier, husky, and lint-staged. Adjust the respective fields in package.json accordingly.
Jest tests are set up to run with yarn test.
Calculates the real cost of your library using size-limit with npm run size and visulize it with npm run analyze.
This is the folder structure we set up for you:
/example
index.html
index.tsx # test your component here in a demo app
package.json
tsconfig.json
/src
index.ts # EDIT THIS
/test
blah.test.tsx # EDIT THIS
/stories
Thing.stories.tsx # EDIT THIS
/.storybook
main.js
preview.js
.gitignore
package.json
README.md # EDIT THIS
tsconfig.jsonWe do not set up react-testing-library for you yet, we welcome contributions and documentation on this.
We use Rollup as a bundler and generates multiple rollup configs for various module formats and build settings.
tsconfig.json is set up to interpret dom and esnext types, as well as react for jsx. Adjust according to your needs.
Two actions are added by default:
mainwhich installs deps w/ cache, lints, tests, and builds on all pushes against a Node and OS matrixsizewhich comments cost comparison of your library on every pull request using size-limit
ESModule format is supported.
The appropriate paths are configured in package.json and es/index.js accordingly. Please report if any issues are found.
The Playground is just a simple CRA app, you can deploy it anywhere you would normally deploy that.
Per Palmer Group guidelines, always use named exports. Code split inside your React app instead of your React library.
There are many ways to ship styles, including with CSS-in-JS. We have no opinion on this, configure how you like.
For vanilla CSS, you can include it at the root directory and add it to the files section in your package.json, so that it can be imported separately by your users and run through their bundler's loader.
When creating a new package with Rollup within a project set up with Lerna, you might encounter a Cannot resolve dependency error when trying to run the example project. To fix that you will need to make changes to the package.json file inside the example directory.
The problem is that due to the nature of how dependencies are installed in Lerna projects, the aliases in the example project's package.json might not point to the right place, as those dependencies might have been installed in the root of your Lerna project.
Change the alias to point to where those packages are actually installed. This depends on the directory structure of your Lerna project, so the actual path might be different from the diff below.
"alias": {
- "react": "../node_modules/react",
- "react-dom": "../node_modules/react-dom"
+ "react": "../../../node_modules/react",
+ "react-dom": "../../../node_modules/react-dom"
},An alternative to fixing this problem would be to remove aliases altogether and define the dependencies referenced as aliases as dev dependencies instead. However, that might cause other problems.