Publish package to npm registry

The package is hosted in a private npm registry In order to authorize on the npm registry you need to create a Personal Access Token with api scope. Further you have to authorize npm to use company's registry using the following command.

npm login --scope @chillirepo --registry https://nexus.betinvest.work/repository/npm/

Execute npm command and select a new version, patch, minor, major

npm run publish --registry https://nexus.betinvest.work/repository/npm/

For the prompts use your gitlab information:

• username: Gitlab username
• password: Personal Access Token created above
• email: Email used on GitLab

The command above will create/update the .npmrc file from your home directory to enable npm to resolve packages under @chillirepo to our npm registry.

Only packages under the scope @chillirepo will be published/installed from the aforementioned registry

Installing the package

Once authorized and with the registry set for @chillirepo, one can simply install the package using the standard npm i command.

npm i --save @chillirepo/backend-eslint-plugin

Development

This package is hosted on company's private npm registry located at https://nexus.betinvest.work/repository/npm/. The user management on that registry is done through GitLab, thus having Developer access to a project on GitLab means you are able to publish and install this package.

Typical development flow:

• Create a branch from master.
• Make your changes.
• Commit them.
• Open a merge request to master for review.
• Once the merge request was approved and merged, a 'patch'(x.y.z+1) version will be created.
• • Before release, the pipeline 'publish_minor' must be run from gitlab ui, which will publish a minor version (x.y+1.0) will be created and the new version will be published

package url

https://gitlab.favorit/casino/backend/chillirepo.git