NPM registry naming convention is impractical for Monorepos

Problem to solve

The Naming convention that is enforced is highly impractical

Target audience

Further details

Same problem existed for the docker registry, and was solved thankfully by enabling several layers of naming

Proposal

What does success look like, and how can we measure that?

What is the type of buyer?

(Which leads to: in which enterprise tier should this feature go see https://about.gitlab.com/handbook/product/pricing/#four-tiers )

Links / references

https://airtable.com/tblEC5647tCeSOWMy/viwWJaP3qazoPlDUL/recTUEBU2WRQpqf14?blocks=hide

Edited Jan 15, 2020 by Vincent Lecrubier
Assignee Loading
Time tracking Loading