Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
next-upgrade: do not add
--turbopack
flag when --turbo
exists in …
…`next dev` (#71730) ### Why? 1. When `next dev --turbo` existed, it added `--turbopack` since it was looking for existing `--turbopack` only. 2. When there's no `"dev"` script found in package.json, inform the user we weren't able to enable Turbopack for them. - https://github.com/vercel/next.js/releases/tag/v15.0.1-canary.3 ## Test Plan ### Suggest Turbopack ``` pnpm test:upgrade-fixture bin/__testfixtures__/suggest-turbopack ``` ```diff "scripts": { - "dev": "next dev" + "dev": "next dev --turbopack" }, ``` ### Change `--turbo` to `--turbopack` ``` pnpm test:upgrade-fixture bin/__testfixtures__/change-turbo-to-turbopack ``` CLI output includes: ``` ✔ Replaced "--turbo" with "--turbopack" in your dev script. ``` ```diff "scripts": { - "dev": "next dev --turbo" + "dev": "next dev --turbopack" }, ```
- Loading branch information