chore: Re-enable turbo flag in dev script #6836
Merged
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.
Description
Next 14.2.4 is released now with the expected fix backported from canary.
next dev --turbo
works now but ran into a different issue with shiki (vercel/next.js#64525, vercel/next.js#63318) and added the suggested temp workaround(vercel/next.js#63318 (comment)) while the fix(vercel/next.js#64918) is being worked on.Validation
npm run serve
works as expected.Related Issues
Fixes #6808
Check List
npm run format
to ensure the code follows the style guide.npm run test
to check if all tests are passing.npx turbo build
to check if the website builds without errors.