fix(non-monorepo): correct devDependency from 'turb' to 'turbo'#10526
Merged
anthonyshew merged 4 commits intoJun 13, 2025
Conversation
ghost
added
Contributor
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Contributor
|
@DiegoDev2 is attempting to deploy a commit to the Vercel Team on Vercel. A member of the Team first needs to authorize it. |
dimitropoulos
approved these changes
Jun 4, 2025
anthonyshew
approved these changes
Jun 9, 2025
Contributor
anthonyshew
left a comment
anthonyshew
left a comment
There was a problem hiding this comment.
Oops! Thank you for fixing. I also updated to latest.
Contributor
Author
|
I apologize for not updating to the latest version. Thanks! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #10523
This PR updates the
non-monorepotemplate to use the correctturbopackage as a devDependency instead of the incorrectturb.Changes
template/package.jsonin thenon-monorepoexample to use"turbo"as adevDependency.Context
Previously, running
npx create-turbo@latest -e non-monorepowould generate a project withturblisted indevDependencies, causing confusion and requiring users to manually installturbo.This fix ensures new projects created from this template have the correct dependency out of the box.
Let me know if there’s anything else I should adjust!