60ad8affd7
This PR addresses an issue where the `dev` script in `package.json` was not correctly updated to use the `--turbo` option when specified. The changes ensure that the `dev` script is set to `next dev --turbo` if the `turbo` option is enabled. ### Changes: 1. **Function Modification**: - Updated the `modifyPackageJson` function to include a check for the `turbo` parameter. - If `turbo` is true, the `dev` script in `package.json` is set to `next dev --turbo`. - If `turbo` is false, the `dev` script remains `next dev`. 2. **Integration in App Creation**: - Integrated the `modifyPackageJson` function into the app creation process to ensure the `dev` script is correctly set based on the `turbo` parameter. ### Testing: - Verified that the `dev` script in `package.json` is correctly updated to `next dev --turbo` when the `turbo` option is enabled. - Ensured that the `dev` script remains `next dev` when the `turbo` option is not enabled. ### Related Issues: - Fixes #65924 ### Notes: - This change ensures that developers opting to use Turbopack for development will have the correct script set up automatically. --------- Signed-off-by: Arindam Majumder <arindammajumder2020@gmail.com> Co-authored-by: Lee Robinson <me@leerob.io> Co-authored-by: devjiwonchoi <devjiwonchoi@gmail.com> Co-authored-by: Jiachi Liu <inbox@huozhi.im> Co-authored-by: Sam Ko <sam@vercel.com> |
||
|---|---|---|
| .. | ||
| 01-installation.mdx | ||
| 02-project-structure.mdx | ||
| index.mdx | ||