- Notifications
You must be signed in to change notification settings - Fork 3.9k
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
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
|
fae36f2 to 6e40573 Compare | Will depend on npm/init-package-json#330 |
6e40573 to 5ce90bd Compare 5ce90bd to a4a3b5c Compare
Closes npm/statusboard#509
This pull request introduces a new
--init-privateflag to thenpm initcommand, allowing users to set theprivatefield in thepackage.jsonfile by default.