fix(non-monorepo): correct devDependency from 'turb' to 'turbo' #10526
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-monorepo
template to use the correctturbo
package as a devDependency instead of the incorrectturb
.Changes
template/package.json
in thenon-monorepo
example to use"turbo"
as adevDependency
.Context
Previously, running
npx create-turbo@latest -e non-monorepo
would generate a project withturb
listed 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!