vaaski
commented
4 months ago Update: I ran into the next similar issue with biome.
bun add --dev --exact @biomejs/biomebun pm trust @biomejs/biomebunx @biomejs/biome init
output
``` ❯ bunx @biomejs/biome init node:internal/modules/cjs/loader:1189 throw err; ^ Error: Cannot find module '@biomejs/cli-darwin-x64/biome' Require stack: - /Users/user/projects/project/node_modules/@biomejs/biome/bin/biome at Module._resolveFilename (node:internal/modules/cjs/loader:1186:15) at Function.resolve (node:internal/modules/helpers:133:19) at Object.Works when including the --bun flag.
sal-jim
What version of Bun is running?
1.1.10+5102a9443
What platform is your computer?
Darwin 23.4.0 arm64 arm
What steps can reproduce the bug?
bun x create-vite repro -t vue-tscd reprobun ibun devWhat is the expected behavior?
It should run the vite server
What do you see instead?
`bun dev` output
``` ~/projects/repro ❯ bun dev $ vite /Users/user/projects/repro/node_modules/rollup/dist/native.js:59 throw new Error( ^ Error: Cannot find module @rollup/rollup-darwin-x64. npm has a bug related to optional dependencies (https://github.com/npm/cli/issues/4828). Please try `npm i` again after removing both package-lock.json and node_modules directory. at requireWithFriendlyError (/Users/user/projects/repro/node_modules/rollup/dist/native.js:59:9) at Object.Additional information
When reproducing this I also ran into an issue with the install command.
`bun i` output
``` ~/projects/repro ❯ bun i bun install v1.1.10 (5102a944) ⚙️ esbuild [1/1] [esbuild] Failed to find package "@esbuild/darwin-x64" on the file system This can happen if you use the "--no-optional" flag. The "optionalDependencies" package.json feature is used by esbuild to install the correct binary executable for your current platform. This install script will now attempt to work around this. If that fails, you need to remove the "--no-optional" flag to use esbuild. [esbuild] Trying to install package "@esbuild/darwin-x64" using npm node:internal/errors:983 const err = new Error(message); ^ Error: Command failed: /Users/user/projects/repro/node_modules/esbuild/bin/esbuild --version at genericNodeError (node:internal/errors:983:15) at wrappedFn (node:internal/errors:537:14) at checkExecSyncError (node:child_process:889:11) at Object.execFileSync (node:child_process:925:15) at validateBinaryVersion (/Users/user/projects/repro/node_modules/esbuild/install.js:99:28) at /Users/user/projects/repro/node_modules/esbuild/install.js:286:5 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) { status: null, signal: 'SIGKILL', output: [ null, Buffer(0) [Uint8Array] [], Buffer(0) [Uint8Array] [] ], pid: 19692, stdout: Buffer(0) [Uint8Array] [], stderr: Buffer(0) [Uint8Array] [] } Node.js v22.2.0 error: postinstall script from "esbuild" exited with 1 ```Running
bun iagain does not show any errors. Interestingly,bun --bun devdoes start the vite server as expected. But I feel like having to include the bun flag should not be the default.I've tried the proposed CLI flags in #9876 but they unfortunately do not help.