-
-
Notifications
You must be signed in to change notification settings - Fork 407
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
vue-tsc not work with typescript 5.7.2 #5018
Comments
I found the issue, Typescript was updated 1 hour ago to version 5.7.2. For me, version 5.6.2 is working. |
I am experiencing the same problem when using vue-tsc version 2.1.10 with TypeScript 5.7.2. The error occurs when running the build script using pnpm /node_modules/.pnpm/[email protected][email protected]/node_modules/vue-tsc/index.js:34
throw err;
^
Search string not found: "/supportedTSExtensions = .*(?=;)/"
Node.js v22.11.0 To resolve this issue temporarily, I had to downgrade:
Here is the updated portion of my package.json after the downgrade: {
"scripts": {
"build": "vue-tsc -b && vite build"
},
"devDependencies": {
"vue-tsc": "2.0.29",
"typescript": "5.6.2",
"vite": "^5.4.10",
"@vitejs/plugin-vue": "^5.1.4"
}
} This downgrade fixed the issue. It appears to be related to an incompatibility between [email protected] and TypeScript 5.7.x. |
The incompatibility appears to be in the Volar repo, specifically where @volar/typescript patches the tsc code, because the tsc code changed with the typescript 5.7 release. I was a little late to the Vue ecosystem and I haven't followed the Volar discussion, so I'm not 100% sure, but I believe Volar is a standalone project now. I'm wondering if this issue may be more appropriately handled over there, since Volar supports other TypeScript-based languages that are impacted by this issue. I searched the issues there, and didn't find anything yet, but it may just be that fresh, since TypeScript 5.7.2 is only about 5 hours old. In the mean time, pinning TypeScript at 5.6.3 and allowing vue-tsc to go to 2.1.10 works for me. |
* Upgrade to Marked 15 * Upgrade to ESLint 9 and typescript-eslint 8 * Stay on TypeScript 5.6 because of an issue with vue-tsc with TS 5.7: vuejs/language-tools#5018 (and also because typescript-eslint doesn't officially support 5.7)
same here |
At language-tools/packages/tsc/index.ts Line 6 in cf70eda
typescript/lib/tsc.js is referenced.
This file is now To work in all typescript versions, it would need to apply the transformations on both It might be worth updating https://github.com/volarjs/volar.js/blob/master/packages/typescript/lib/quickstart/runTsc.ts#L11 to:
|
This has a huge impact. When will the version be released to solve this problem? |
I use this command But it continues falling with the same error on pipeline in gitlab.
|
I was able to fix this issue by changing the lib path which is now different, like above comment described. Why this sudden change I cant figure out |
Same issue with
what i've found so far is that the error is triggered by |
I'm getting the same error. It doesn't seem to matter what older versions of typescript or vue-tsc that I try. So I'm not convinced that typescript is the actual problem.
EDIT: I recreated my project using the latest Vite template and using these dependencies it now builds without the error...
|
I wanted to share that, as a palliative solution, I resolved the issue by using these specific versions in my package.json without the ^ at the beginning: "devDependencies": {
"typescript": "5.6.2",
"vue-tsc": "2.0.29"
} After making this change, the problem stopped occurring for me. |
Since vue-tsc does not (yet) work with newer typescript versions, the typescript version was pinned to '5.6.3' for now. For more information see vuejs/language-tools#5018 RISDEV-0000
Vue - Official extension or vue-tsc version
2.1.10
VSCode version
none
Vue version
3.5.13
TypeScript version
5.7.2
System Info
package.json dependencies
Steps to reproduce
update typescript to 5.7.2
What is expected?
no error
What is actually happening?
throw error:
Link to minimal reproduction
No response
Any additional comments?
No response
The text was updated successfully, but these errors were encountered: