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
This changed when we updated all typescript and eslint related packages. We replaced @vue/eslint-config-typescript v12.0.0 with typescript-eslint v8.17.0, since the first package caused problems in mono repos.
⏯ Playground Link
No response
💻 Code
// Changing this:consthello=()=>{returntrue;};hello();// To this:consthello=(value: string)=>{returntrue;};hello();
🙁 Actual behavior
Takes over 5 seconds to show an error about the missing parameter. This happens only in .vue files and in .test.ts files which use Vue components. If I remove all imported components from the component template the type check time becomes almost instant. Regular .ts files show the error instantly.
🙂 Expected behavior
It should show the error almost instantly.
Additional information about the issue
This all started when we updated our eslint and typescript packages and eslint configuration. Our configuration is based on this comment: vuejs/eslint-config-typescript#76 (comment)
If I set the "strictNullChecks" to false in tsconfig, everything works instantly. I am running out of ideas how I can fix this, maybe someone who knows these things inside out can instantly point out what is wrong with our tsconfig or eslint configuration?
tsconfig.json:
{// This tsconfig extends these files:// https://github.com/vuejs/tsconfig/blob/main/tsconfig.json (this is extended by below dom.json)// https://github.com/vuejs/tsconfig/blob/main/tsconfig.dom.json// https://github.com/vuejs/tsconfig/blob/main/tsconfig.lib.json"extends": ["@vue/tsconfig/tsconfig.dom.json","@vue/tsconfig/tsconfig.lib.json"],"compilerOptions": {"paths": {"@/*": ["./src/*"]},// Fix building Vue components"moduleResolution": "node","outDir": "dist",// Fix importing translations"allowSyntheticDefaultImports": true,"types": ["vitest/globals","@vitest/browser/providers/playwright","vitest-browser-vue"]},"include": ["src/**/*.ts","src/**/*.d.ts","src/**/*.tsx","src/**/*.vue"],"references": [{"path": "./tsconfig.node.json"}],"exclude": ["src/App.vue","src/main.ts"]}
🔎 Search Terms
"strictNullChecks slow", "ts-plugin slow"
🕗 Version & Regression Information
This changed when we updated all typescript and eslint related packages. We replaced @vue/eslint-config-typescript v12.0.0 with typescript-eslint v8.17.0, since the first package caused problems in mono repos.
⏯ Playground Link
No response
💻 Code
🙁 Actual behavior
Takes over 5 seconds to show an error about the missing parameter. This happens only in .vue files and in .test.ts files which use Vue components. If I remove all imported components from the component template the type check time becomes almost instant. Regular .ts files show the error instantly.
🙂 Expected behavior
It should show the error almost instantly.
Additional information about the issue
This all started when we updated our eslint and typescript packages and eslint configuration. Our configuration is based on this comment: vuejs/eslint-config-typescript#76 (comment)
If I set the "strictNullChecks" to false in tsconfig, everything works instantly. I am running out of ideas how I can fix this, maybe someone who knows these things inside out can instantly point out what is wrong with our tsconfig or eslint configuration?
tsconfig.json
:tsconfig.node.json
:eslint.config.js
:Installed versions:
The text was updated successfully, but these errors were encountered: