not able to overwrite compilerOptions
See original GitHub issueEnvironment
mac os
Reproduction
adding the following values into tsconfig.json
"compilerOptions": {
"lib": [
"es2020", "esnext"
],
"module": "commonjs",
"target": "es2020"
}
Does not override the .nuxt/tsconfig.json file and keeps target as ESNext
Describe the bug
I need to overwrite the compilerOptions because during the “nuxi run dev” I am unable to load a package that requires a different target. When using the following code for the main tsconfig.json file at the root of the project, it does not overwrite the changes and resulting target is always as its set initially by nuxi.
{
// https://v3.nuxtjs.org/concepts/typescript
"extends": "./.nuxt/tsconfig.json",
"compilerOptions": {
"lib": [
"es2020", "esnext"
],
"module": "commonjs",
"target": "es2020"
}
}
There needs to be a way to overwrite this. If I build the project, the imported module does not give errors. During the development, I am getting compilation errors for
Big integer literals are not available in the configured target environment ("chrome87", "edge88", "es2020", "firefox78", "safari13" + 2 overrides)
which should be corrected by changing the target during the compilation.
Additional context
No response
Logs
No response
Issue Analytics
- State:
- Created a year ago
- Comments:7 (3 by maintainers)
Top GitHub Comments
@Redemption198 To fix the dev server you can exclude wasm-vips from pre-bundling and set the required COOP and COEP headers, for example:
The production build is (unfortunately) currently broken, as you noticed. This is due to issue https://github.com/vitejs/vite/issues/7015, which causes an infinite loop when it tries to transform/bundle
lib/vips-es6.worker.js
.Closing this to track the feature request in https://github.com/nuxt/framework/issues/7471. The remaining issue here appears to be an upstream vite bug and is not the one described in the issue.