Environment
- Operating System: Linux
- Node Version: v20.6.0
- Nuxt Version: 3.7.1
- CLI Version: 3.7.3
- Nitro Version: 2.6.2
- Package Manager: pnpm@8.7.3
- Builder: -
- User Config: extends, nitro, css, app, imports, modules, fontLoader, mapbox, quasar
- Runtime Modules: nuxt-mapbox@1.4.4, @nuxtjs/device@3.1.0, nuxt-font-loader@2.3.1
- Build Modules: -
Reproduction
After upgrading to node v20.6, you should get Cannot redefine property: __internal__deprecationWarning after trying to run nuxi build or some other commands as well.
Describe the bug
I am fairly certain this is related to this issue. Don't think there is anything that can be done currently but I wanted to open an issue in case others run into the problem. This can be easily worked around by downgrading your node version to something other than v20.6.
Additional context
No response
Logs
> nuxt build
Nuxt 3.7.1 with Nitro 2.6.2 4:48:24 PM
ERROR Cannot redefine property: __internal__deprecationWarning 4:48:24 PM
at Function.defineProperty (<anonymous>)
at Object.<anonymous> (/home/alex/ProperateMono/node_modules/.pnpm/@babel+types@7.22.15/node_modules/@babel/types/lib/index.js:66:8)
at Module._compile (node:internal/modules/cjs/loader:1241:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1295:10)
at Module.load (node:internal/modules/cjs/loader:1091:32)
at Module._load (node:internal/modules/cjs/loader:938:12)
at Module.require (node:internal/modules/cjs/loader:1115:19)
at require (node:internal/modules/helpers:130:18)
at Object.<anonymous> (/home/alex/ProperateMono/node_modules/.pnpm/@babel+types@7.22.15/node_modules/@babel/types/lib/builders/validateNode.js:8:14)
at Module._compile (node:internal/modules/cjs/loader:1241:14)
ERROR Cannot redefine property: __internal__deprecationWarning 4:48:24 PM
ELIFECYCLE Command failed with exit code 1.
Environment
Reproduction
After upgrading to node v20.6, you should get
Cannot redefine property: __internal__deprecationWarningafter trying to runnuxi buildor some other commands as well.Describe the bug
I am fairly certain this is related to this issue. Don't think there is anything that can be done currently but I wanted to open an issue in case others run into the problem. This can be easily worked around by downgrading your node version to something other than v20.6.
Additional context
No response
Logs