> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/11867) in GitLab Premium 12.6.
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/11867) in GitLab Premium 12.6.
> - [Moved](https://gitlab.com/gitlab-org/gitlab/-/issues/221259) to GitLab Free in 13.3.
> - [Moved](https://gitlab.com/gitlab-org/gitlab/-/issues/221259) to GitLab Free in 13.3.
> - [Improved](https://gitlab.com/gitlab-org/gitlab/-/issues/330929) in GitLab 14.5.
In GitLab 12.6 and later, packages published to the Package Registry expose the following attributes to the npm client:
The GitLab Package Registry exposes the following attributes to the npm client.
- name
These are similar to the [abbreviated metadata format](https://github.com/npm/registry/blob/9e368cf6aaca608da5b2c378c0d53f475298b916/docs/responses/package-metadata.md#abbreviated-metadata-format):
- version
- dist-tags
-`name`
- dependencies
-`versions`
- dependencies
-`name`
- devDependencies
-`version`
- bundleDependencies
-`deprecated`
- peerDependencies
-`dependencies`
- deprecated
-`devDependencies`
-`bundleDependencies`
-`peerDependencies`
-`bin`
-`directories`
-`dist`
-`engines`
-`_hasShrinkwrap`
## Add npm distribution tags
## Add npm distribution tags
...
@@ -579,6 +590,10 @@ root namespace and therefore cannot be published again using the same name.
...
@@ -579,6 +590,10 @@ root namespace and therefore cannot be published again using the same name.
This is also true even if the prior published package shares the same name,
This is also true even if the prior published package shares the same name,
but not the version.
but not the version.
#### Package JSON file is too large
Make sure that your `package.json` file does not [exceed `20,000` characters](#packagejson-limitations).