[GH-ISSUE #169] bug: Vinext init ignores existing package manager and defaults to npm #39

New issue

Closed

opened 2026-05-06 12:36:44 +02:00 by BreizhHardware · 2 comments

BreizhHardware commented

2026-05-06 12:36:44 +02:00

Owner

Originally created by @Zaid-maker on GitHub (Feb 27, 2026).
Original GitHub issue: https://github.com/cloudflare/vinext/issues/169

When migrating an existing Next.js project to Vinext using vinext init, the CLI does not auto-detect the package manager being used in the project.

For example, I use Bun for better performance, and I run vinext init inside a Bun-based project. However, after the compatibility check, Vinext installs dependencies using npm under the hood instead of the project’s existing package manager.

This causes significantly slower dependency installation and breaks the expected workflow. Vinext should automatically detect the package manager based on:

The lockfile present (bun.lockb, pnpm-lock.yaml, yarn.lock, package-lock.json)
Or the runtime used to execute the command (e.g., bunx vinext init)
Or the packageManager field in package.json

Expected behavior:
Vinext should respect and use the project's existing package manager (e.g., Bun) instead of defaulting to npm.

Originally created by @Zaid-maker on GitHub (Feb 27, 2026). Original GitHub issue: https://github.com/cloudflare/vinext/issues/169 When migrating an existing Next.js project to Vinext using `vinext init`, the CLI does not auto-detect the package manager being used in the project. For example, I use **Bun** for better performance, and I run `vinext init` inside a Bun-based project. However, after the compatibility check, Vinext installs dependencies using **npm** under the hood instead of the project’s existing package manager. This causes significantly slower dependency installation and breaks the expected workflow. Vinext should automatically detect the package manager based on: * The lockfile present (`bun.lockb`, `pnpm-lock.yaml`, `yarn.lock`, `package-lock.json`) * Or the runtime used to execute the command (e.g., `bunx vinext init`) * Or the `packageManager` field in `package.json` **Expected behavior:** Vinext should respect and use the project's existing package manager (e.g., Bun) instead of defaulting to npm.

BreizhHardware closed this issue

2026-05-06 12:36:44 +02:00

BreizhHardware commented

2026-05-06 12:36:45 +02:00

Author

Owner

@threepointone commented on GitHub (Feb 27, 2026):

this is fixed in main, should go out in the next release, thanks for flagging

@threepointone commented on GitHub (Feb 27, 2026): this is fixed in main, should go out in the next release, thanks for flagging

BreizhHardware commented

2026-05-06 12:36:45 +02:00

Author

Owner

@Zaid-maker commented on GitHub (Feb 28, 2026):

this is fixed in main, should go out in the next release, thanks for flagging

Thank you so much!

@Zaid-maker commented on GitHub (Feb 28, 2026): > this is fixed in main, should go out in the next release, thanks for flagging Thank you so much!

BreizhHardware referenced this issue

2026-05-06 12:38:49 +02:00

[PR #39] [MERGED] fix: link to Vite RSC plugin in README #260