Skip to content

feat(init): add new config to npm init for setting private value (ie. --init-private) #509

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

Open
darcyclarke opened this issue May 16, 2022 · 4 comments · May be fixed by npm/cli#8246
Open
Assignees
Labels
Milestone

Comments

@darcyclarke
Copy link
Contributor

No description provided.

@darcyclarke darcyclarke mentioned this issue May 16, 2022
32 tasks
@darcyclarke darcyclarke changed the title BREAKING CHANGE(init): default to <code class="notranslate">--init-private=true` BREAKING CHANGE(init): default to --init-private=true May 16, 2022
@wraithgar
Copy link
Member

npm init does not currently have a config item that alters the private flag.

@ljharb
Copy link

ljharb commented Sep 1, 2022

When this was filed, the intention was to ship in npm 8 a config item for this that defaulted to false.

@lukekarrys lukekarrys added this to the v9.0.0 milestone Sep 2, 2022
@lukekarrys
Copy link
Contributor

I have the same recollection as @ljharb and think this should be changed to add a config option for this. Obviously that makes it no longer a breaking change.

@ljharb
Copy link

ljharb commented Sep 2, 2022

Is it too late to semver minor it into v8?

@darcyclarke darcyclarke changed the title BREAKING CHANGE(init): default to --init-private=true feat(init): add new config to npm init for setting private value (ie. --init-private) Oct 5, 2022
@owlstronaut owlstronaut linked a pull request Apr 21, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants