-
Notifications
You must be signed in to change notification settings - Fork 137
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
Extension should recognize other package managers than npm #3854
Comments
Which package managers would you like to see supported? You're correct in that we only support npm at the moment. Others we could support would be yarn or pnpm. |
Yarn and pnpm is a really solid base, if the hype continues, bun could be also a good candidate. In terms of priority (against my personal preferences, in which I would prefer seeing Yarn 3 first), I think it is:
|
Ok, thanks for the info. |
This feature request is now a candidate for our backlog. The community has 240 days to upvote the issue. If it receives 5 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation. Happy Coding! |
Which one are you currently using? Yarn 3? |
@alexweininger Yes, v3 at the moment. Note that versions 2/3/4 will be all pretty much the same when implementing support - same commands, same lockfiles, same configuration files etc. |
Existence of any other package manager (recognized by
packageManager
inpackage.json
, presence of a certain lockfile) is simply ignored and the extension still tries to configure everything, particularlytasks.json
, using npm. This leads to creating setups that may simply not work.The text was updated successfully, but these errors were encountered: