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

Why is there inconsistency in the behavior of npm, yarn, and pnpm when using the @ parameter placeholder? #124

Closed
mishengqiang opened this issue Nov 30, 2023 · 2 comments

Comments

@mishengqiang
Copy link

In the create-vue project, the @ placeholder is used, but there is inconsistency in behavior between npm, yarn, and pnpm. See details at vuejs/create-vue#394 (comment).

@bcomnes
Copy link
Owner

bcomnes commented Nov 30, 2023

I don't have an exact answer off hand, but the 3 package managers vary quite a bit in annoying and subtle ways when it comes to package.json script running, argument passing etc. It's an unfortunate set of circumstances.

npm-run-all{2} doesn't attempt to normalize these differences. Generally my order of priorities here is: make it work perfectly with npm, then best effort on pnpm and then yarn.

Could you clarify what you think npm-run-all2 is doing incorrectly here, and how you think it should work?

@bcomnes
Copy link
Owner

bcomnes commented Dec 18, 2023

Closing due to lack of specifics here. Happy to reopen when we can clarify these issues. I don't have time at the moment to investigate on my own.

@bcomnes bcomnes closed this as completed Dec 18, 2023
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

2 participants