vetur: Maximum call stack size exceeded. On vscode1.15.1
Today Vetur was good before I updated vscode. But when I upgreade vscode from 1.15 to 1.15.1. Vetur has a problem.
vetur initialized
/Users/apple/.vscode/extensions/octref.vetur-0.9.3/client/node_modules/typescript/lib/typescript.js:15973
function forEachChild(node, cbNode, cbNodeArray) {
^
RangeError: Maximum call stack size exceeded
at Object.forEachChild (/Users/apple/.vscode/extensions/octref.vetur-0.9.3/client/node_modules/typescript/lib/typescript.js:15973:26)
at bindEachChild (/Users/apple/.vscode/extensions/octref.vetur-0.9.3/client/node_modules/typescript/lib/typescript.js:23091:16)
at bindBinaryExpressionFlow (/Users/apple/.vscode/extensions/octref.vetur-0.9.3/client/node_modules/typescript/lib/typescript.js:23748:17)
at bindChildrenWorker (/Users/apple/.vscode/extensions/octref.vetur-0.9.3/client/node_modules/typescript/lib/typescript.js:23162:21)
at bindChildren (/Users/apple/.vscode/extensions/octref.vetur-0.9.3/client/node_modules/typescript/lib/typescript.js:23066:17)
at bind (/Users/apple/.vscode/extensions/octref.vetur-0.9.3/client/node_modules/typescript/lib/typescript.js:24319:21)
at visitNode (/Users/apple/.vscode/extensions/octref.vetur-0.9.3/client/node_modules/typescript/lib/typescript.js:15944:20)
at Object.forEachChild (/Users/apple/.vscode/extensions/octref.vetur-0.9.3/client/node_modules/typescript/lib/typescript.js:16114:24)
at bindEachChild (/Users/apple/.vscode/extensions/octref.vetur-0.9.3/client/node_modules/typescript/lib/typescript.js:23091:16)
at bindBinaryExpressionFlow (/Users/apple/.vscode/extensions/octref.vetur-0.9.3/client/node_modules/typescript/lib/typescript.js:23748:17)
[Info - 7:48:31 PM] Connection to server got closed. Server will restart.
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 25 (10 by maintainers)
Commits related to this issue
- Upgrade ts. Fix #390 — committed to vuejs/vetur by octref 7 years ago
@eric-burel see https://code.visualstudio.com/blogs/2017/08/07/emmet-2.0#_other-changes Use emmet.includeLanguages instead of emmet.syntaxProfiles setting. Now emmet is work.