Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for scoped packages #26

Open
2 of 3 tasks
glenjamin opened this issue May 2, 2015 · 3 comments
Open
2 of 3 tasks

Support for scoped packages #26

glenjamin opened this issue May 2, 2015 · 3 comments

Comments

@glenjamin
Copy link
Collaborator

The public registry now supports scopes: http://blog.npmjs.org/post/116936804365/solving-npms-hard-problem-naming-packages

There's also some neat stuff in the client to support pointing scopes at different registries: https://docs.npmjs.com/misc/scope

Here's a suggested featurelist in rough order of importance:

  • proxing & caching of scoped packages
  • publishing scoped packages locally
  • configurable whitelist for scopes which can be published to (eg. only local publish to @companyname)

I'm going to take a stab at the first two for now.

@afbobak
Copy link
Owner

afbobak commented May 2, 2015

+1

@afbobak
Copy link
Owner

afbobak commented May 4, 2015

What exactly do you mean by whitelisting scopes? Publishing to local, or even passing it through to the parent registry?

@glenjamin
Copy link
Collaborator Author

I was thinking that local would only accept publishes for the named scopes.

Could proxy other publishes, or just reject.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants