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

Feature request: handling of private packages? #265

Open
bertrand-caron opened this issue Apr 4, 2023 · 0 comments
Open

Feature request: handling of private packages? #265

bertrand-caron opened this issue Apr 4, 2023 · 0 comments

Comments

@bertrand-caron
Copy link

Hi there,

Thanks for your awesome library :)

I am having issues with privately hosted packages.

As it currently stands, the private option in NPM's package.json is in my opinion quite misleading: it might as well be called canPublish.
The source code seems unambiguous: you cannot publish a package using npm publish with the package: false option (it will throw).

Short of making a massive backwards-incompatible change to npm, package.json, or both, is there a way to specify that a package is private?

Or am I just missing some fundamental knowledge about how private packages are published with npm/yarn publish?

Note that this extends to yarn as it seems to implement the exact same behaviour as NPM.

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

1 participant