Commit e9997645 authored by Achilleas Pipinellis's avatar Achilleas Pipinellis

Merge branch '55344-npm-package-requests-forwarding-docs' into 'master'

Document npm package requests forwarding

See merge request gitlab-org/gitlab!26888
parents 0b5d06d9 f3e7c8d4
...@@ -191,3 +191,16 @@ To set required pipeline configuration: ...@@ -191,3 +191,16 @@ To set required pipeline configuration:
1. Click **Save changes**. 1. Click **Save changes**.
![Required pipeline](img/admin_required_pipeline.png) ![Required pipeline](img/admin_required_pipeline.png)
## Package Registry configuration **(PREMIUM ONLY)**
GitLab administrators can disable the forwarding of NPM requests to [npmjs.com](https://www.npmjs.com/).
To disable it:
1. Go to **Admin Area > Settings > CI/CD**.
1. Expand the **Package Registry** section.
1. Uncheck **Enable forwarding of NPM package requests to npmjs.org**.
1. Click **Save changes**.
![NPM package requests forwarding](img/admin_package_registry_npm_package_requests_forward.png)
...@@ -269,6 +269,14 @@ Or if you're using Yarn: ...@@ -269,6 +269,14 @@ Or if you're using Yarn:
yarn add @my-project-scope/my-package yarn add @my-project-scope/my-package
``` ```
### Forwarding requests to npmjs.org
> [Introduced](https://gitlab.com/gitlab-org/gitlab/issues/55344) in [GitLab Premium](https://about.gitlab.com/pricing/) 12.9.
By default, when an NPM package is not found in the GitLab NPM Registry, the request will be forwarded to [npmjs.com](https://www.npmjs.com/).
Administrators can disable this behavior in the [Continuous Integration settings](../../admin_area/settings/continuous_integration.md).
## Removing a package ## Removing a package
In the packages view of your project page, you can delete packages by clicking In the packages view of your project page, you can delete packages by clicking
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment