CLI for creating reusable, modern Inferno libraries using Rollup and create-inferno-app.
This is a fork of create-react-library.
At the moment, it doesn't offer a Typescript option like create-react-library, but if you'd like to have it,
let me know, or send up a pull request :)
- Easy-to-use CLI
- Handles all modern JS features
- Bundles
cjsandesmodule formats - create-inferno-app for example usage and local dev
- Rollup for bundling
- Babel for transpiling
- Jest for testing
- Supports complicated peer-dependencies
- Supports CSS modules
- Optional support for TypeScript
- Sourcemap creation
- Hundreds of public modules created
- Thorough documentation 😍
This package requires node >= 4, but we recommend node >= 8.
yarn global add create-inferno-library
# OR npm install -g create-inferno-librarynpx create-inferno-library(npx comes with npm 5.2+ and higher, see instructions for older npm versions)
create-inferno-libraryAnswer some basic prompts about your module, and then the CLI will perform the following steps:
- copy over the template
- install dependencies via yarn or npm
- link packages together for local development
- initialize local git repo
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.
yarn start
# OR npm start
# runs rollup with watch flagThe second part will be running the example/ create-inferno-app that's linked to the local version of your module.
# (in another shell)
cd example
yarn start
# OR npm start
# runs create-inferno-app dev serverNow, anytime you make a change to your library in src/ or to the example app's example/src, create-inferno-app will live-reload your local dev server so you can iterate on your component in real-time.
npm publishThis builds cjs 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.
yarn deploy
# OR npm run deployThis creates a production build of the example create-inferno-app that showcases your library and then runs gh-pages to deploy the resulting bundle.
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-inferno-library.
Want to add yours to the list? Submit an issue.
MIT © Tom Golden
Thanks to Travis Fischer for making create-react-library.