Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

vlt package manager is not recognized by turborepo #9425

Closed
1 task done
hamlim opened this issue Nov 12, 2024 · 5 comments
Closed
1 task done

vlt package manager is not recognized by turborepo #9425

hamlim opened this issue Nov 12, 2024 · 5 comments

Comments

@hamlim
Copy link

hamlim commented Nov 12, 2024

Verify canary release

  • I verified that the issue exists in the latest Turborepo 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?

npm
vlt

What operating system are you using?

Mac

Which canary version will you have in your reproduction?

2.2.3

Describe the Bug

The new vlt package manager doesn't seem to be recognized yet.

Expected Behavior

The vlt package manager should be recognized by turborepo

To Reproduce

  • Clone the reproduction repo: https://github.com/hamlim/vlt-monorepo
  • Run vlt install (install vlt via something like bun add -g vlt@latest or npm install -g vlt@latest, etc)
  • Run vlt run dev and see turborepo error

Additional context

No response

@hamlim hamlim added kind: bug Something isn't working needs: triage New issues get this label. Remove it after triage labels Nov 12, 2024
@hamlim
Copy link
Author

hamlim commented Nov 12, 2024

Note - the issue template also only allows me to select a set list of package managers that doesn't list vlt yet either

@anthonyshew anthonyshew added needs: champion and removed kind: bug Something isn't working needs: triage New issues get this label. Remove it after triage labels Nov 13, 2024
@anthonyshew
Copy link
Contributor

anthonyshew commented Nov 13, 2024

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.

@hamlim
Copy link
Author

hamlim commented Nov 13, 2024

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?

@anthonyshew
Copy link
Contributor

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.

@anthonyshew
Copy link
Contributor

Going to move this do a Discussion as that's where we handle our feature requests.

@vercel vercel locked and limited conversation to collaborators Nov 14, 2024
@anthonyshew anthonyshew converted this issue into discussion #9436 Nov 14, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Projects
None yet
Development

No branches or pull requests

2 participants