NPM Registry - allow custom scopes
Problem to solve
Currently, the organization scope of an NPM package is determined by convention: the name of the top-level project. This is detailed in the NPM package naming convention.
This can be a problem for corporate development organizations where the project might be the company name and cannot be changed, while the NPM organization might be something else, like an acronym of the company name.
In our case, we are migrating a lot of (hundreds) of projects to Gitlab, where all imports of our NPM packages reference the organization scope we have used until now. The top-level project in Gitlab however, is set to our official company name and cannot be changed to what we were using as our NPM organization scope. Right now I only see solution: changing the thousands of imports in our code to the new NPM scope automatically set by Gitlab.
- Company name (top-level project): "Acme Corporation"
- Desired NPM organization scope: "acme"
Personas are described at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ -->
Allow defining custom NPM scopes for projects.