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

[Feat/Bug] pnpm init does not respect init.* options as flags like npm init --init-* #8090

Closed
1 task done
josh-hemphill opened this issue May 16, 2024 · 3 comments
Closed
1 task done

Comments

@josh-hemphill
Copy link

Contribution

Describe the user story

I often have multiple folders to init, and when the defaults are specific there's no way to set them all other than manually, but I'd like to be able to set defaults on the cli so I can easily create a bunch of package.json files by just modifying a cli one-liner, or write some automation to iterate with the option flags.

In fact, npm has actually deprecated using the config options instead of the cli flags as introduced in pnpm with #4422

Describe the solution you'd like

I'd actually like it if pnpm allowed more of the default values to be set with flags, since that would add even more convenience.

Describe the drawbacks of your solution

Nothing I can think of.

Describe alternatives you've considered

Using npm

@btea
Copy link
Contributor

btea commented May 16, 2024

It seems to be a duplicate of #7711.

@josh-hemphill
Copy link
Author

Ah, didn't manage to find that one (not much searchable text/keywords on it 😅). Should I close this or link them?

@btea
Copy link
Contributor

btea commented May 16, 2024

My comment above has been linked there, maybe you can close this issue directly. You can keep it active by adding your comments there. 😀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants