
I have run yarn under C:UsersDGB.vscode-insidersextensionsoctref.vetur-0.11.3client
@dbaeumer is this a regression for https://github.com/Microsoft/vscode/issues/33951?
I'm using 3.5.0.
Have same problem here but on linux platform. And yeah, seems that vetur is run in debug mode. After monkeypatching in client/out/vueMain.js and setting const debugServerModule = serverModule vetur server started normally.
@Cherrionella BTW are you using Insiders or Stable version? Did you upgrade Vetur and it stopped working, or is it a Insider upgrade made it stop working?
For me it's the newest update in Insider that breaks it.
@dbaeumer The distributed version with Vetur is 3.4.2, but I guess it doesn't matter since it seems to be a change in Code that makes LS always run in debug mode.
@octref Yes. 1.19.0-insiders. I'll check later but it seems to be working with stable one
This is likely https://github.com/Microsoft/vscode/commit/d9a16d31d3bda6e5d0076fc3da02f285975fb772 which causes the extension host to run with --inspect=<port> in all cases. We can (temporarily) undo that change but this is an issue with Vetur as customers are free to run the extension host in debug mode, see the --inspect-extensions and --inspect-brk-extensions flags
@jrieken. Thanks
Decided to always point to the server in /server. Mainly for ease of development -- no installServerIntoExtension, no npm link.
@HerringtonDarkholme FYI and I'll make sure to release VLS each time I do a release.
im experiencing this issue after i upgraded my code insiders to latest version....
any fix for this?
@codeitlikemiley I had the similar issue and my solution was:
and it works!
Most helpful comment
This is likely https://github.com/Microsoft/vscode/commit/d9a16d31d3bda6e5d0076fc3da02f285975fb772 which causes the extension host to run with
--inspect=<port>in all cases. We can (temporarily) undo that change but this is an issue with Vetur as customers are free to run the extension host in debug mode, see the--inspect-extensionsand--inspect-brk-extensionsflags