You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Most likely 22.13.1, deployed using Vercel CLI 39.3.0 with "Node 22.x" preset
Platform
Most likely Linux, deployed using Vercel CLI 39.3.0 with "Node 22.x" preset
Subsystem
No response
What steps will reproduce the bug?
We are directed to report the stack trace as it might be an error with Node.js.
How often does it reproduce? Is there a required condition?
This error occurs when trying to deploy using Node 22. There is no error when deploying to Node 20.
What is the expected behavior? Why is that the expected behavior?
The project is successfully deployed using Node 22.
What do you see instead?
[08:54:18.399] [info] Building client...
[08:54:18.806] [error] Nuxt Build Error: Unexpected status of a module that is imported again after being required. Status = 0
[08:54:18.806] This is caused by either a bug in Node.js or incorrect usage of Node.js internals.
[08:54:18.806] Please open an issue with this stack trace at https://github.com/nodejs/node/issues
[08:54:18.806]
[08:54:18.806] This is caused by either a bug in Node.js or incorrect usage of Node.js internals.
[08:54:18.806] Please open an issue with this stack trace at https://github.com/nodejs/node/issues
[08:54:18.806]
[08:54:18.806] at Function.fail (node:internal/assert:17:9)
[08:54:18.806] at ModuleJobSync.run (node:internal/modules/esm/module_job:378:12)
[08:54:18.806] at onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:547:42)
[08:54:18.806] at async import (/vercel/path0/node_modules/.pnpm/jiti@2.0.0-beta.3/node_modules/jiti/dist/jiti.cjs:1:195631)
[08:54:18.806] at async unocss.config.ts:1:195
[08:54:18.806] at async Function.import (/vercel/path0/node_modules/.pnpm/jiti@2.0.0-beta.3/node_modules/jiti/dist/jiti.cjs:1:195631)
[08:54:18.806] at async Module.loader (/vercel/path0/node_modules/.pnpm/importx@0.4.4/node_modules/importx/dist/chunks/jiti.mjs:11:15)
[08:54:18.806] at async Module.importx (/vercel/path0/node_modules/.pnpm/importx@0.4.4/node_modules/importx/dist/index.mjs:179:19)
[08:54:18.806] at async /vercel/path0/node_modules/.pnpm/unconfig@0.5.5/node_modules/unconfig/dist/index.mjs:169:21
[08:54:18.806] at async loadConfigFile (/vercel/path0/node_modules/.pnpm/unconfig@0.5.5/node_modules/unconfig/dist/index.mjs:168:18)
[08:54:18.806] at async Object.load (/vercel/path0/node_modules/.pnpm/unconfig@0.5.5/node_modules/unconfig/dist/index.mjs:97:24)
[08:54:18.806] at async loadConfig (/vercel/path0/node_modules/.pnpm/@unocss+config@0.62.3/node_modules/@unocss/config/dist/index.mjs:43:18)
[08:54:18.806] at async /vercel/path0/node_modules/.pnpm/@unocss+config@0.62.3/node_modules/@unocss/config/dist/index.mjs:57:22
[08:54:18.807] at async reloadConfig (/vercel/path0/node_modules/.pnpm/@unocss+vite@0.62.3_rollup@4.18.0_vite@5.3.1_@types+node@20.14.2_terser@5.31.1_/node_modules/@unocss/vite/dist/index.mjs:94:20)
[08:54:18.831] ELIFECYCLE Command failed with exit code 1.
[08:54:18.852] Error: Command "pnpm run build" exited with 1
[08:54:19.358]
Additional information
No response
The text was updated successfully, but these errors were encountered:
Version
Most likely 22.13.1, deployed using Vercel CLI 39.3.0 with "Node 22.x" preset
Platform
Subsystem
No response
What steps will reproduce the bug?
We are directed to report the stack trace as it might be an error with Node.js.
How often does it reproduce? Is there a required condition?
This error occurs when trying to deploy using Node 22. There is no error when deploying to Node 20.
What is the expected behavior? Why is that the expected behavior?
The project is successfully deployed using Node 22.
What do you see instead?
Additional information
No response
The text was updated successfully, but these errors were encountered: