-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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(turborepo): support Bun #5934
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
9 Ignored Deployments
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Orca Security Scan Summary
Status | Check | Issues by priority | |
---|---|---|---|
Passed | Secrets | 0 0 0 0 | View in Orca |
Someone is attempting to deploy a commit to the Vercel Team on Vercel. A member of the Team first needs to authorize it. |
let repo_root_path = AbsoluteSystemPathBuf::try_from(repo_root.path())?; | ||
|
||
let lockfile_path = repo_root.path().join(LOCKFILE); | ||
File::create(lockfile_path)?; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Non-blocking nit: we have .create_with_contents("")
so we don't need to pull in std::fs::File
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall looks good to me. A few questions:
- Are we expecting users to have
print = "yarn"
in their in theirbunfig.toml
in order to get lockfile based info for their repos? If so we should probably have some custom error messaging in the package graph building that suggests adding it when we notice they have abun.lockb
but noyarn.lock
that we can read. - I'm pretty strongly against claiming we offer any sort of
prune
support until we can serialize enough info for some version ofbun install
to work. (Unless I'm reading the docs wrong and users can justbun install --yarn
with only ayarn.lock
and not need abun.lockb
)
45f7cbe
to
7e1e6b6
Compare
Nope,
I've started a thread in Slack on this to get full team input. |
d893629
to
da5e5e0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Orca Security Scan Summary
Status | Check | Issues by priority | |
---|---|---|---|
Passed | Secrets | 0 0 0 0 | View in Orca |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Orca Security Scan Summary
Status | Check | Issues by priority | |
---|---|---|---|
Passed | Secrets | 0 0 0 0 | View in Orca |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Orca Security Scan Summary
Status | Check | Issues by priority | |
---|---|---|---|
Passed | Secrets | 0 0 0 0 | View in Orca |
This reverts commit 26ec64c.
2ffa3c2
to
ed3f4ff
Compare
same here look like corepack issue nodejs/corepack#307 |
@juliusmarminge Thanks for the quick feedback!
Aside, the opener for the |
Enable using
bun
as both a package manager and a runtime.Closes #4762
Closes TURBO-1324