search

npm / npme-installer

npm Enterprise installer
https://www.npmjs.com/enterprise
Other
35 stars 21 forks source link

Shouldn't Scoped modules be tagged as "Private"? #117

Open marcellodesales opened 8 years ago

marcellodesales commented 8 years ago

What does the "Public" tag mean in the NPM UI? For instance, PM2 is a public module as we know...

screen shot 2016-01-12 at 5 37 41 pm

Considering that "Public" means retrieved from the public NPM Registry, then what would mean to have the same tag for a shared module published into NPMO? For instance, the following library deployed internally.

screen shot 2016-01-12 at 5 16 33 pm
kevinSuttle commented 8 years ago

Good question. Clarification in the npm docs would be good.

kevinSuttle commented 8 years ago

Got it here. https://github.com/npm/npmo-docs/issues/6 @bcoe I mentioned to @nexdrew that it would seem to make sense to require scoping. https://github.com/npm/npmo-docs/issues/6#issuecomment-213122575

kevinSuttle commented 8 years ago

@marcellodesales Apparently marking packages as private prevents publishing at all. https://docs.npmjs.com/misc/registry#i-dont-want-my-package-published-in-the-official-registry-its-private

marcellodesales commented 8 years ago

@kevinSuttle That's why I don't think this feature is related to the "private" setup in the package.json... It might have to do with the concept of "public" or "private" in terms of the use of Scopes...