react-component-library-test-simibac v1.0.9
Provotum SSI React Component Library
This project uses this template to bootstrap a react component library.
This project skeleton was created to help people get started with creating their own React component library using:
- Rollup
- TypeScript
- Storybook to help you create and show off your components
Building
yarn buildStorybook
Storybook helps to build, document and test your components. To run a live-reload Storybook server on your local machine:
yarn storybookTo export your Storybook as static files:
npm run storybook:exportGenerating New Components
I've included a handy NodeJS util file under util called create-component.js. Instead of copy pasting components to create a new component, you can instead run this command to generate all the files you need to start building out a new component. To use it:
npm run generate YourComponentNameThis will generate:
/src
/YourComponentName
YourComponentName.tsx
YourComponentName.stories.tsx
YourComponentName.test.tsx
YourComponentName.types.ts
YourComponentName.scssThe default templates for each file can be modified under util/templates.
Don't forget to add the component to your index.ts exports if you want the library to export the component!
Installing Component Library Locally
Let's say you have another project (test-app) on your machine that you want to try installing the component library into without having to first publish the component library. In the test-app directory, you can run:
npm i --save ../react-component-librarywhich will install the local component library as a dependency in test-app. It'll then appear as a dependency in package.json like:
...
"dependencies": {
...
"react-component-library": "file:../react-component-library",
...
},
...Your components can then be imported and used in that project.
Publishing
Hosting via NPM
First, make sure you have an NPM account and are logged into NPM using the npm login command.
Then update the name field in package.json to reflect your NPM package name in your private or public NPM registry. Then run:
npm publishThe "prepublishOnly": "npm run build" script in package.json will execute before publish occurs, ensuring the build/ directory and the compiled component library exist.
Hosting via GitHub
I recommend you host the component library using NPM. However, if you don't want to use NPM, you can use GitHub to host it instead.
You'll need to remove build/ from .gitignore, build the component library (npm run build), add, commit and push the contents of build. See this branch for an example.
You can then install your library into other projects by running:
npm i --save git+https://github.com/HarveyD/react-component-library.git#branch-nameOR
npm i --save github:harveyd/react-component-library#branch-nameUsage
Let's say you created a public NPM package called harvey-component-library with the TestComponent component created in this repository.
Usage of the component (after the library installed as a dependency into another project) will be:
import React from "react";
import { TestComponent } from "harvey-component-library";
const App = () => (
<div className="app-container">
<h1>Hello I'm consuming the component library</h1>
<TestComponent theme="primary" />
</div>
);
export default App;Additional Help
CSS Modules
If you want to use CSS Modules, update postcss in rollup-config.js to:
postcss({
modules: true
})Supporting Image Imports
Add the following library to your component library @rollup/plugin-image:
npm i -D @rollup/plugin-imageThen add it to rollup-config.js:
...
plugins:[
...,
image(),
...
]
...You can then import and render images in your components like:
import logo from "./rollup.png";
export const ImageComponent = () => (
<div>
<img src={logo} />
</div>
);