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.

Sign up for GitHub

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

Jump to bottom

Better verbage around why Blacklist / Whitelist are important #124

Open

indexzero opened this issue Feb 4, 2014 · 1 comment

Member

indexzero commented Feb 4, 2014

Right now we just describe what the features are, not why they are so valuable to teams using npm.

Member Author

indexzero commented Feb 4, 2014

Here is the TL;DR:

Whitelisting is really important if you want to ensure that only certain modules are available to your team.
Blacklisting is more common, if you want to "fork" a package from the public npm, you simply blacklist it and then publish your version of the module which will go to your private npm.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment