Closed schl3ck closed 6 months ago
Thanks for the bug report. I'll try to reproduce the issue this weekend.
I can reproduce the issue if I create a directory junction and open a file through that junction. For example:
mklink /j p:\quick-lint-js-sandbox p:\quick-lint-js\sandbox
code p:\quick-lint-js-sandbox\hello.js
I could not reproduce this issue when using subst or a network drive.
@schl3ck Are you using a junction/symlink?
Yes, I'm editing the files through a junction.
Fixed in Git commit 748b775a60ae558c8d717d2be1e6e58f80b0cae5. This fix will be included in quick-lint-js version 3.2.
Fix released in version 3.2.0.
When the extension is activated the extension host immediately crashes. It doesn't matter what .js file I've open.
The only clue I found was in the developer tools of VSCode. All other output views did not provide any useful information. In the console of the developer tools it logged:
Please let me know if there is any other information I can provide.