-
-
Notifications
You must be signed in to change notification settings - Fork 160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
An error during "bun install," how can I resolve it? #247
Comments
Hey, can you check with Node.js? I don't know what the issue is. I just checked on Ubuntu, and it's working fine for me |
Same issue here |
Hey, sorry about the issue. Are you using Bun or npm? |
Using bun. However, after I posted this I used nvm to install node 23, and the problem disappeared. Somehow that fixed it. |
More info for you. This is on Mint 22. Before I used nvm I didn't have any versions of node installed. So mostly vanilla install with no node, running the 'bun install' command failed. Install nvm, install node 23, all problems gone. It seems like some version of node has to be installed for 'bun install' to work. |
OS: Ubuntu 24.04 LTS (GNU/Linux 6.8.0-31-generic x86_64)
(base) root@kafeizha:# bun install
bun install v1.1.34 (5e5e7c60)
$ wxt prepare
WXT 0.19.13 9:05:36 AM
✖ Command failed after 466 ms 9:05:37 AM
ERROR virtualModule.require is not a function. (In 'virtualModule.require(wantedModuleName)', 'virtualModule.require' is undefined) 9:05:37 AM
at (node_modules/vite-plugin-top-level-await/dist/esbuild.js:14:50)
at (node_modules/vite-plugin-top-level-await/dist/esbuild.js:16:56)
at evalModule (node_modules/jiti/dist/jiti.js:1:247312)
at jiti (node_modules/jiti/dist/jiti.js:1:245240)
at (node_modules/vite-plugin-top-level-await/dist/index.js:25:32)
at evalModule (node_modules/jiti/dist/jiti.js:1:247312)
at jiti (node_modules/jiti/dist/jiti.js:1:245240)
at (node_modules/vite-plugin-top-level-await/exports/require.cjs:1:100)
at evalModule (node_modules/jiti/dist/jiti.js:1:247312)
at jiti (node_modules/jiti/dist/jiti.js:1:245240)
at (wxt.config.ts:3:1)
at evalModule (node_modules/jiti/dist/jiti.js:1:247312)
at jiti (node_modules/jiti/dist/jiti.js:1:245240)
at (node_modules/c12/dist/shared/c12.cab0c9da.mjs:345:26)
at resolveConfig (node_modules/c12/dist/shared/c12.cab0c9da.mjs:279:30)
at (node_modules/c12/dist/shared/c12.cab0c9da.mjs:147:29)
at loadConfig (node_modules/c12/dist/shared/c12.cab0c9da.mjs:108:27)
at (node_modules/wxt/dist/core/resolve-config.mjs:17:57)
at resolveConfig (node_modules/wxt/dist/core/resolve-config.mjs:13:37)
at (node_modules/wxt/dist/core/wxt.mjs:11:24)
at registerWxt (node_modules/wxt/dist/core/wxt.mjs:8:35)
at (node_modules/wxt/dist/core/prepare.mjs:5:9)
at prepare (node_modules/wxt/dist/core/prepare.mjs:4:31)
at (node_modules/wxt/dist/cli/commands.mjs:76:11)
at (node_modules/wxt/dist/cli/commands.mjs:75:21)
at (node_modules/wxt/dist/cli/cli-utils.mjs:17:28)
at (node_modules/wxt/dist/cli/cli-utils.mjs:9:10)
at module code (node_modules/wxt/dist/cli/index.mjs:11:11)
at (native)
at processTicksAndRejections (native)
error: postinstall script from "pageassist" exited with 1
The text was updated successfully, but these errors were encountered: