When you publish a package, it must have my-org as the scope.

The package-name can be whatever you want.

ForĮxample, a package in GitLab becomes for npm. This requirement and translates uppercase in the GitLab to lowercase for npm. Problematic because the npm public registry does not allow uppercase letters. Before GitLab 13.10, had to be a case-sensitive match of the GitLab project’s root namespace.

However, the GitLab package registry allows for uppercase.

The is the root namespace of the GitLab project.

When you use the instance-level endpoint, only the packages with names in the format of are available. Npm config set always-auth true Package naming convention # Force npm to always require authentication when accessing the registry, even for GET requests. To use the project-level npm endpoint, set your npm configuration: To authenticate with the Package Registry, you need a personal access token or deploy token.

Your npm package name must be in the format of must match exactly, including the case.Īuthenticate with a personal access token or deploy token.

You must use a personal access token with OAuth headers. Standard OAuth tokens cannot authenticate to the GitLab npm Registry.

It’s not recommended, but you can use OAuth tokens.

A deploy token, with the scope set to read_package_registry, write_package_registry, or both.

(required for two-factor authentication (2FA)), with the scope set to api. To authenticate, use one of the following: Public projects do not require authentication. You must authenticate with the Package Registry when the project Some features such as publishing a package is only available on the project-level endpoint. Be sure to comply with the package naming convention.

Instance-level: Use when you have many npm packages in different.

When you use a scope, the registry URL is updated only for that scope. Instead, you should use a scope for your package. The package naming convention is not enforced at this level.

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

To use the GitLab endpoint for npm packages, choose an option: Project or group where the registry exists. The naming convention and is scoped to the

Supported CLI commands npm packages in the Package Registry.

npm publish returns npm ERR! 500 Internal Server Error - PUT.

Package name does not meet the naming convention.

npm publish returns npm ERR! 400 Bad Request.

npm install returns npm ERR! 403 Forbidden.

npm install returns Error: Failed to replace env in config: $.

npm publish targets default npm registry ( ).

Error running Yarn with the Package Registry for npm registry.

Install npm packages from other organizations.

Publishing packages with the same name or version.Configure the GitLab npm registry with Yarn 2.Use variables to avoid hard-coding auth token values.Authenticate with a personal access token or deploy token.Use the GitLab endpoint for npm packages.

Npm install package with version syntax