or does it still need to be enabled manually with the --turbo flag

i believe you still have to --turbo, but its stable in sense they trust it more

as most of us add the --turbo to the package.json script we dont need to remember and enable

ok yes i just tried creating a blank next 15 project and it's still a flag

good then i can migrate to next 15

yay

nevermind, bunch of errors for peer dependencies

btw you can usually force your way to install because often they will work, but peer deps shouldnt just be all without testing https://canary.discord.com/channels/752553802359505017/1298228956834828330/1298231945368436776

Slightly aside from your Turbopack question, but what peer dep issues did you face?
I've hit the following when trying to upgrade today, I believe is an issue with @next/third-parties package, maybe I need to manually upgrade that first before running the code mod

While resolving: my-new-app@1.0.0
Found: react@19.0.0-rc-65a56d0e-20241020
node_modules/react
react@"19.0.0-rc-65a56d0e-20241020" from the root project
peer react@"^18.2.0 19.0.0-rc-65a56d0e-20241020" from next@15.0.0
node_modules/next
next@"15.0.0" from the root project
peer next@"^13.0.0 ^14.0.0 ^15.0.0" from @next/third-parties@15.0.0
node_modules/@next/third-parties
@next/third-parties@"15.0.0" from the root project
peer react@"19.0.0-rc-65a56d0e-20241020" from react-dom@19.0.0-rc-65a56d0e-20241020
node_modules/react-dom
react-dom@"19.0.0-rc-65a56d0e-20241020" from the root project
peer react-dom@"^18.2.0 19.0.0-rc-65a56d0e-20241020" from next@15.0.0
node_modules/next
next@"15.0.0" from the root project
peer next@"^13.0.0 ^14.0.0 ^15.0.0" from @next/third-parties@15.0.0
node_modules/@next/third-parties
@next/third-parties@"15.0.0" from the root project

Could not resolve dependency:
peer react@"^18.2.0 || 19.0.0-rc-cd22717c-20241013" from @next/third-parties@15.0.0
node_modules/@next/third-parties
@next/third-parties@"15.0.0" from the root project

Fix the upstream dependency conflict, or retry
this command with --force or --legacy-peer-deps
to accept an incorrect (and potentially broken) dependency resolution.

Main issue I had was next having errors when starting, it automatically tried to install @types/react even though they were already installed, and that lead to startup errors because of peer deps etc, I'll just wait for react 19 to come out officially and then migrate in a month or so