VUE Language Server crashed 5 times in the last 3 minutes
See original GitHub issue- I have searched through existing issues
- I have read through docs
- I have read FAQ
- I have tried restarting VS Code or running
Vetur: Restart VLS
Info
- Platform: Windows_NT x64 10.0.19043
- Vetur version: 0.36.0
- VS Code version: 1.71.0, Electron: 19.0.12, Chromium: 102.0.5005.167
- Node.js: 16.14.2
Problem
The errror occurs on some .vue files, not on all. I have no idea what the reason is, i tried almost everything: i reduced step by step the code of such a failed .vue file, but the vls server restart takes a long time, which makes the error investigation very heavy ! I checked the folder structure, e.g. same file name like folder name (maybe this creates end endless loop), i renamed, copied files and so on - nothing helped !! Vetur is a very important tool for me, and I and other developer need it really for developing stable software. Maybe is “VOLAR” the right plugin, but my program exists since 3 years (VUE2 with about 100 files), and i don’t want to change it like VOLAR spec. I reinstalled also VETUR, no success
Vetur initialized [INFO ] Loaded bundled typescript@4.4.4. [INFO ] Loaded bundled prettier. [INFO ] Loaded bundled @starptech/prettyhtml. [INFO ] Loaded bundled prettier-eslint. [INFO ] Loaded bundled prettier-tslint. [INFO ] Loaded bundled stylus-supremacy. [INFO ] Loaded bundled @prettier/plugin-pug. [Error - 06:47:41] Request textDocument/semanticTokens/range failed. Message: Request textDocument/semanticTokens/range failed with message: Maximum call stack size exceeded Code: -32603 c:\Users\Wolfgang.vscode\extensions\octref.vetur-0.36.0\server\node_modules\typescript\lib\typescript.js:60473 function getObjectTypeInstantiation(type, mapper, aliasSymbol, aliasTypeArguments) { ^
RangeError: Maximum call stack size exceeded at getObjectTypeInstantiation (c:\Users\Wolfgang.vscode\extensions\octref.vetur-0.36.0\server\node_modules\typescript\lib\typescript.js:60473:44) at instantiateTypeWorker (c:\Users\Wolfgang.vscode\extensions\octref.vetur-0.36.0\server\node_modules\typescript\lib\typescript.js:60736:28) at instantiateTypeWithAlias (c:\Users\Wolfgang.vscode\extensions\octref.vetur-0.36.0\server\node_modules\typescript\lib\typescript.js:60716:26) at instantiateType (c:\Users\Wolfgang.vscode\extensions\octref.vetur-0.36.0\server\node_modules\typescript\lib\typescript.js:60699:37) at instantiateList (c:\Users\Wolfgang.vscode\extensions\octref.vetur-0.36.0\server\node_modules\typescript\lib\typescript.js:60323:34)
Reproducible Case
Not Reproducable
My Package.json
{
"name": "xxx",
"version": "1.0.0",
"private": true,
"scripts": {
"serve": "vue-cli-service serve ",
"dev": "vue-cli-service build --mode development",
"netcup": "vue-cli-service build --mode netcup",
"xampp": "vue-cli-service build --mode xampp",
"lint": "vue-cli-service lint --no-fix"
},
"devDependencies": {
"@types/crypto-js": "4.1.1",
"@types/d3": "^7.1.0",
"@types/lodash": "^4.14.178",
"@types/vue2-datepicker": "^3.3.1",
"@types/vuelidate": "^0.7.15",
"@typescript-eslint/eslint-plugin": "^5.33.1",
"@typescript-eslint/parser": "^5.33.1",
"@vue/eslint-config-typescript": "^11.0.0",
"axios": "^0.21.1",
"bootstrap": "^4.6.0",
"cross-env": "^7.0.3",
"eslint": "^8.22.0",
"eslint-plugin-vue": "^9.3.0",
"jquery": "^3.6.0",
"lodash": "^4.17.21",
"popper.js": "^1.12",
"resolve-url-loader": "^3.1.2",
"sass": "^1.32.8",
"sass-loader": "^10.1.1",
"typescript": "~4.1.5",
"vue": "^2.6.12",
"vue-template-compiler": "^2.6.12"
},
"dependencies": {
"@fortawesome/fontawesome-svg-core": "^6.1.1",
"@fortawesome/free-brands-svg-icons": "^6.1.1",
"@fortawesome/free-regular-svg-icons": "^6.1.1",
"@fortawesome/free-solid-svg-icons": "^6.1.1",
"@fortawesome/vue-fontawesome": "^2.0.6",
"@fullcalendar/bootstrap": "^5.6.0",
"@fullcalendar/core": "^5.6.0",
"@fullcalendar/daygrid": "^5.6.0",
"@fullcalendar/google-calendar": "^5.6.0",
"@fullcalendar/interaction": "^5.6.0",
"@fullcalendar/list": "^5.6.0",
"@fullcalendar/resource-common": "^5.6.0",
"@fullcalendar/resource-daygrid": "^5.6.0",
"@fullcalendar/resource-timeline": "^5.6.0",
"@fullcalendar/rrule": "^5.6.0",
"@fullcalendar/timegrid": "^5.6.0",
"@fullcalendar/timeline": "^5.6.0",
"@fullcalendar/vue": "^5.6.0",
"@vue/cli-plugin-eslint": "^5.0.8",
"@vue/cli-plugin-typescript": "^5.0.4",
"@vue/cli-service": "^5.0.4",
"bootstrap-vue": "^2.21.2",
"crypto-js": "^4.1.1",
"d3": "^6.6.2",
"rrule": "^2.6.8",
"vue-axios": "^3.2.4",
"vue-bootstrap-typeahead": "^0.2.6",
"vue-context": "^6.0.0",
"vue-i18n": "^8.26.7",
"vue-moment": "^4.1.0",
"vue-router": "^3.5.1",
"vue-swatches": "^2.1.1",
"vue-unique-id": "^3.2.0",
"vue2-datepicker": "^3.9.0",
"vuelidate": "^0.7.6",
"vuex": "^3.6.2"
}
}
Issue Analytics
- State:
- Created a year ago
- Comments:9 (1 by maintainers)
Top GitHub Comments
Hi Cyclodex, thanks for your helping!
tsconfig.json:
“Select Typescript Version”:
I tried to use the workspace Version - the problem still exists
Hey @susanne99 I have almost exactly the same issue as you do, after a lengthy investigation found that if I removed
“@types/vuelidate”: “^0.7.15”, the range error maximum callstack size exceeded no longer happens.
I got declaration missing and other expected validation errors in components where vuelidate is present, which is in the dozens of places for me , but the build does not fail. it will take some time to make the update but hopefully thats is it.
Suggestion:
Try updating vuelidate to @vuelidate/core v2.0.0
https://vuelidate-next.netlify.app/ after that update vue-template-compiler to 2.7.14