Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/zxol/react-component-publish
A starter for publishing your own react components.
https://github.com/zxol/react-component-publish
babel boilerplate component npm publish react template webpack
Last synced: 25 days ago
JSON representation
A starter for publishing your own react components.
- Host: GitHub
- URL: https://github.com/zxol/react-component-publish
- Owner: zxol
- Created: 2019-01-27T03:03:31.000Z (almost 6 years ago)
- Default Branch: master
- Last Pushed: 2023-01-03T16:11:26.000Z (almost 2 years ago)
- Last Synced: 2024-09-29T06:22:42.205Z (about 1 month ago)
- Topics: babel, boilerplate, component, npm, publish, react, template, webpack
- Language: JavaScript
- Homepage:
- Size: 1.03 MB
- Stars: 9
- Watchers: 1
- Forks: 4
- Open Issues: 22
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# react-component-publish
A barebones boilerplate to quickly publish react components.
Features Webpack 4 and Babel 7.
It will compile down to commonjs, and will require a peer dependancy of react, meaning it will use whatever version of react the host project is using. Hopefully this will minimize compatibility issues.
[Based on this tutorial](https://medium.com/quick-code/publish-your-own-react-component-as-npm-package-under-5-minutes-8a47f0cb92b9) by [codewithbernard](https://github.com/codewithbernard)
## To start
```
npm i
npm start
```
Edit `src/index.js` (your component)
## To view your component in isolation with a basic webpack dev server:
type:
```
npm run dev
```
Edit `/srctest/app.js` to change the parent environment, pass in props, etc.
## To test your component in another project (locally), before publishing to npm:
Build this project:
```
npm run build
```
In this project's root directory, type:
```
npm link
```
And then, in the project (root dir) you would like to use your component:
```
npm link my-awesome-component
```
For this example I've used the package name `my-awesome-component`.
This creates a symlink of your package in your project's node_modules/ dir.
Now, you may import the component in your test project, as if it was a normally installed dependancy:
```
import MyAwesomeComponent from 'my-awesome-component'
```
If you're using a hot-reload system, you should be able to observe any changes you make to your component (as long as you build them)
## To publish your component to npm
Update the package.json with correct information.
Important things to set:
```json
{
"name": "cool-beans",
"version": "4.2.0",
"description": "My wizzbang gizmo",
"author": "stevejobs",
"license": "ISC"
}
```
If you have a git repo for the project, include the details:
```json
"repository": {
"type" : "git",
"url" : "https://github.com/zxol/react-component-publish"
},
```
Then, in the root directory, type:
```
npm publish
```
[npm docs on publishing packages](https://docs.npmjs.com/packages-and-modules/contributing-packages-to-the-registry)
## A note on webpack configs and the dev server:
There are two webpack configs.
- One for building the published component `webpack.publish.js`
- One for viewing the component in the dev server. `webpack.testServer.js`
Note that they are separate, so any additions you make will have to be mirrored in both files, if you want to use the dev server. If anyone knows a better way to do this, please let me know.