-
Notifications
You must be signed in to change notification settings - Fork 3.4k
feat: added init-private option #8246
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
base: latest
Are you sure you want to change the base?
Conversation
647f13b
to
eb99fca
Compare
eb99fca
to
f12422b
Compare
f12422b
to
9a26950
Compare
npm/cli#8246 This pull request introduces support for an `init-private` configuration option, allowing users to specify whether a package should be private by default. It includes changes to the initialization logic and corresponding test cases to ensure the feature works as expected.
9a26950
to
e531f17
Compare
e531f17
to
d06004b
Compare
d06004b
to
160413e
Compare
this is waiting on npm/init-package-json#327 |
160413e
to
fae36f2
Compare
Landed npm/init-package-json#327 and amended the |
This is gonna take more work than what's in here, the code path that's failing is when no args are present, it goes directly to
|
Closes npm/statusboard#509
This pull request introduces a new
--init-private
flag to thenpm init
command, allowing users to set theprivate
field in thepackage.json
file by default.