bca6ff77f9
### What? As [discussed](https://vercel.slack.com/archives/C04DUD7EB1B/p1692183798097169), we should follow the ecosystem standard separation of dependencies and dev dependencies. ### Why? This is a common issue/misunderstanding that we always have to explain separately, while there is no real benefit. One counter-argument was that install times would be increased when we had to run install for `dependencies` and `devDependencies` separately, but that's easy to work around as explained below. ### How? Instead of passing the `dependencies` array to the package manager in the CLI, we write these to the `package.json` file and then run the package manager's install command without the dependency arguments. This will also reduce the number of writes to the `package.json` file from two to just one. Ref: https://github.com/vercel/next.js/pull/42218, https://github.com/vercel/next.js/pull/48076, https://github.com/vercel/next.js/issues/54105, https://github.com/vercel/next.js/pull/42012, and more [Slack thread](https://vercel.slack.com/archives/C04DUD7EB1B/p1692183798097169) Co-authored-by: Steven <229881+styfle@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| copy.ts | ||
| examples.ts | ||
| get-pkg-manager.ts | ||
| git.ts | ||
| install.ts | ||
| is-folder-empty.ts | ||
| is-online.ts | ||
| is-writeable.ts | ||
| make-dir.ts | ||
| validate-pkg.ts | ||