If you plan to install a package through the project level, then you do not have to adhere to the naming convention.

Project-level: Use when you have few npm packages and they are not in the same GitLab group.

Instance-level: Use when you have many npm packages in different GitLab groups or in their own namespace.

You can use one of two API endpoints to install packages: Naming conventionĭepending on how the package is installed, you may need to adhere to the naming convention.

If you are publishing a package via CI/CD pipelines, you must use a CI job token.Ĭreate a token and save it to use later in the process.

If your organization uses two factor authentication (2FA), you must use a personal access token with the scope set to api.

For more information, review the guidance on tokens. There are different tokens available depending on what you’re trying to achieve. Publish to GitLab Package Registry Authentication to the Package Registry Watch a video demo of how to publish npm packages to the GitLab Package Registry. Learn how to build an npm or yarn package.

npm publish returns npm ERR! 500 Internal Server Error - PUT npm packages in the Package Registryįor documentation of the specific API endpoints that the npm package manager client uses, see the npm API documentation.

Package name does not meet the naming convention.

npm publish returns npm ERR! 400 Bad Request.

npm install returns npm ERR! 403 Forbidden.

npm publish targets default npm registry ( ).

404 Not Found errors are happening on npm install or yarn.

Install npm packages from other organizations.

Publishing a package via a CI/CD pipeline.

Publishing a package via the command line.

Npm config set user 0