|Project Name||Stars||Downloads||Repos Using This||Packages Using This||Most Recent Commit||Total Releases||Latest Release||Open Issues||License||Language|
|Ink||20,253||4,188||784||5 days ago||67||October 07, 2021||65||mit||TypeScript|
|🌈 React for interactive command-line apps|
|Upterm||19,482||4 years ago||1||September 06, 2015||220||mit||TypeScript|
|A terminal emulator for the 21st century.|
|Nx||16,974||126||264||19 hours ago||846||September 23, 2022||700||mit||TypeScript|
|Smart, Fast and Extensible Build System|
|Ignite||15,032||1||1||a day ago||37||December 27, 2016||43||mit||TypeScript|
|Infinite Red's battle-tested React Native project boilerplate, along with a CLI, component/model generators, and more!|
|An online IDE for rapid web development|
|Infisical||5,152||2 days ago||113||other||TypeScript|
|♾ Infisical is an open-source, end-to-end encrypted platform to sync secrets and configs across your team and infrastructure.|
|CLI for creating reusable react libraries.|
|A react renderer for blessed.|
This tool is no longer actively maintained. I suggest using either tsup, tsdx, or microbundle.
Here's an article I wrote in April 2022 which should help you decide between these different tools.
CLI for creating reusable, modern React libraries using Rollup and create-react-app.
This package requires
node >= 10.
npm install -g create-react-library
(npx comes with npm 5.2+ and higher, see instructions for older npm versions)
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.
npm 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.
# (in another tab) cd example npm start # runs create-react-app dev server
Now, anytime you make a change to your library in
src/ or to the example app's
create-react-app will live-reload your local dev server so you can iterate on your component in real-time.
es versions of your module to
dist/ and then publishes your module to
Make sure that any npm modules you want as peer dependencies are properly marked as
package.json. The rollup config will automatically recognize them as peers and not try to bundle them in your module.
npm 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,
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
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.
MIT Travis Fischer
Support my OSS work by following me on twitter