Replies: 5 comments
-
|
Converting to a Discussion as that's where we handle our feature requests. |
Beta Was this translation helpful? Give feedback.
-
|
We parse lockfiles to get knowledge about the package and task graph, letting us create all the optimizations that we do. Since every package manager has a different lockfile format, we have to write fresh code for every one. |
Beta Was this translation helpful? Give feedback.
-
|
Is there documentation on why there's a strict allowlist of package managers that turborepo works with as opposed to being agnostic of the package manager? |
Beta Was this translation helpful? Give feedback.
-
|
HI, we're not looking to support any new package managers right now. Maybe in the future! Will leave this open for posterity and anyone who wants to add their interest can add a 👍 to the top-level. |
Beta Was this translation helpful? Give feedback.
-
|
Note - the issue template also only allows me to select a set list of package managers that doesn't list |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Verify canary release
Link to code that reproduces this issue
https://github.com/hamlim/vlt-monorepo
What package manager are you using / does the bug impact?
npmvlt
What operating system are you using?
Mac
Which canary version will you have in your reproduction?
2.2.3
Describe the Bug
The new
vltpackage manager doesn't seem to be recognized yet.Expected Behavior
The
vltpackage manager should be recognized by turborepoTo Reproduce
vlt install(installvltvia something likebun add -g vlt@latestornpm install -g vlt@latest, etc)vlt run devand see turborepo errorAdditional context
No response
Beta Was this translation helpful? Give feedback.
All reactions