NPM PUBLISH REACT TEMPLATE

This project is just a template to create isolated components or modules with react, and publish it to npm.

Production

Props (Sockets)

  title: PropTypes.oneOfType([PropTypes.element, PropTypes.string]),

  title: null,

Component loaded in title section.

  box1: PropTypes.oneOfType([PropTypes.element, PropTypes.string]),

  // default
  box1: null,

Component loaded in box1 section.

  box2: PropTypes.oneOfType([PropTypes.element, PropTypes.string]),

  // default
  box2: null,

Component loaded in box2 section.

  box3: PropTypes.oneOfType([PropTypes.element, PropTypes.string]),

  // default
  box3: null,

Component loaded in box3 section.

Development

Folder structure

- build
- config
- node_modules
- src
.babelrc
.eslintignore
.eslintrc
.gitignore
.npmignore
package.json
README.md

Folders

• build: is the transpiled code in ES5.
• config: is where the webpack configuration is defined.
• src: is where our component / modules are developed.

Files

• .babelrc: here is defined the babel configuration about how transpile our code
• .eslintrc / .eslintignore: here are defined the eslint configuration and ignored files
• .npmignore / .gitignore: here are defined the files and foldes that we want to ignore for and npm

How to use

You must create your component or module inside src/ folder. To test your component you must have another project to load it, but before you need to link it locally with npm.

1. Link your component from your component project:

npm link

2. Run webpack to compile your component and keep it in watch mode:

npm start

3. In the second project, where you want to load your component, create a reference to it:

npm link component-name

4. Import it and use into your project.

This simulates locally the node_modules and npm behavior.

Publish your component

Remeber to add to peerDependencies in package.json the dependencies that will used by it's parent from our component in production.

You need to login using your npm account, and then run:

npm publish

Using the prepublishOnly script, each time that you want to publish your component, webpack generates a new fresh build.

Remember to unlink your component after publish:

In your component folder:

npm unlink

In your local project to test:

npm unlink component-name

Webpack Configuration

Eslint configuration