Gathering detailed insights and metrics for create-react-library
Gathering detailed insights and metrics for create-react-library
Gathering detailed insights and metrics for create-react-library
Gathering detailed insights and metrics for create-react-library
npm install create-react-library
Typescript
Module System
Min. Node Version
JavaScript (68.98%)
HTML (19.51%)
CSS (6.43%)
TypeScript (5.08%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
4,779 Stars
265 Commits
300 Forks
31 Watchers
6 Branches
26 Contributors
Updated on Jul 12, 2025
Latest Version
3.1.1
Package Id
create-react-library@3.1.1
Unpacked Size
216.09 kB
Size
66.23 kB
File Count
75
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
CLI for creating reusable, modern React libraries using Rollup and create-react-app.
commonjs
and es
module formatsThis package requires node >= 10
.
1npm install -g create-react-library
1npx create-react-library
(npx comes with npm 5.2+ and higher, see instructions for older npm versions)
1create-react-library
Answer some basic prompts about your module, and then the CLI will perform the following steps:
At this point, your new module should resemble this screenshot and is all setup for local development.
Local development is broken into two parts (ideally using two tabs).
First, run rollup to watch your src/
module and automatically recompile it into dist/
whenever you make changes.
1npm start # runs rollup with watch flag
The second part will be running the example/
create-react-app that's linked to the local version of your module.
1# (in another tab) 2cd example 3npm start # runs create-react-app dev server
Now, anytime you make a change to your library in src/
or to the example app's example/src
, create-react-app
will live-reload your local dev server so you can iterate on your component in real-time.
1npm publish
This builds commonjs
and es
versions of your module to dist/
and then publishes your module to npm
.
Make sure that any npm modules you want as peer dependencies are properly marked as peerDependencies
in package.json
. The rollup config will automatically recognize them as peers and not try to bundle them in your module.
1npm run deploy
This creates a production build of the example create-react-app
that showcases your library and then runs gh-pages
to deploy the resulting bundle.
If you use react-hooks in your project, when you debug your example you may run into an exception Invalid Hook Call Warning. This issue explains the reason, your lib and example use a different instance, one solution is rewrite the react
path in your example's package.json
to 'file:../node_modules/react' or 'link:../node_modules/react'.
Here is a branch which demonstrates how to use multiple named exports. The module in this branch exports two components, Foo
and Bar
, and shows how to use them from the example app.
Here is a branch which demonstrates how to make use of a relatively complicated peer dependency, material-ui. It shows the power of rollup-plugin-peer-deps-external which makes it a breeze to create reusable modules that include complicated material-ui subcomponents without having them bundled as a part of your module.
The CLI is based on this boilerplate, which you can optionally read about here.
Here are some example libraries that have been bootstrapped with create-react-library
.
Want to see a more completed list? Check out Made with CRL
Want to add yours to the list? Submit an PR at the Made with CRL repository.
My open source efforts are now focused on Saasify, and I am not able to invest a significant amount of time into maintaining CRL anymore. I am looking for volunteers who would like to become active maintainers on the project. If you are interested, please shoot me a note.
MIT © Travis Fischer
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
Found 7/18 approved changesets -- score normalized to 3
Reason
project is archived
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
license file not detected
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
30 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More