-
-
Notifications
You must be signed in to change notification settings - Fork 596
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
Maximum call stack size exceeded. On vscode1.15.1 #390
Comments
Can you provide a repro? |
https://github.com/Moerj/monkey-pc-coupon |
Hi, |
Yes.I lose Emmet after update too. |
@eric-burel |
@Moerj Much thanks, VS Code devs seems to be fond of changing obscure config names so that each new version breaks everything... |
Remove all settings in @Moerj Your project doesn't crash for me though. Are you still using symlinks? |
@octref No. I do npm install all dependencies. |
@octref |
I try to reinstall node_modules and Vetur. Will still crash. 😰 |
node@8.3.0 |
@octref When I do npm run build. The vue-cli will build the project and create dist/ files. In the dist folder. vendor.**.js . There is such a code: forEachChild. So. Need a jsconfig.json to exclude dist folder ? |
I mean. If I create a jsconfig.json like this https://vuejs.github.io/vetur/setup.html |
If you just exclude |
Remove your |
Yes! already removed. |
So with jsconfig.json, you are not getting crashes? |
Yeah. Not crashes with jsconfig.json. |
Hi @Moerj , I think this issue has been solved. So let's close this issue first. Feel free to reopen it if you still have problems. |
@HerringtonDarkholme js.config can not completely solve this problem. |
@Moerj Would you mind give me more explanation? Note, You need to configure jsconfig.json's
Could you try this out? |
Sorry, I just note issue closed by other person cannot be reopened by OP. Reopen. |
I think this should be fixed by microsoft/TypeScript#18246 |
We should upgrade to TS 2.5.3 as microsoft/TypeScript#18246 seems to be included in it. |
Today Vetur was good before I updated vscode.
But when I upgreade vscode from 1.15 to 1.15.1. Vetur has a problem.
vscode @1.15.1
vetur @0.9.3
The text was updated successfully, but these errors were encountered: