Andy Brenneke

Yeah `harbor-meta/src/betterer.ts` was the file I had open in VS Code, I know exactly where the errors should have been appearing

Nah still no good :( ``` [Info - 8:22:53 PM] Validator: Sending 12 diagnostics to "file:///Users/andy.brenneke/code/work/ironclad/harbor/packages/harbor-meta/src/worser.ts". ```

This seems specific to `eslint-plugin-eslint-comments`! I disabled those rules in a file that wasn't working and suddenly problems showed up.

yeah I was looking at the code for svelte-language-server as a reference, looks like it's a whole lot of boilerplate to get a server process being reused.

It seems like svelte has its own language server that then wraps `tsserver` et al. Looks like * The extension boots up the svelte server: https://github.com/sveltejs/language-tools/blob/master/packages/svelte-vscode/src/extension.ts#L57-L145 * The svelte server...

Yeah that makes sense, babel doesn't even try to compile it so 🤷 - swc does compile it so I was surprised when a call simply didn't work at all,...

> I.e. this whole thing probably starts with vue-loader using a false assumption that loaderContext.resourcePath is safely changeable. I've been investigating this for the past 4 days or so, and...

> Remove the intermediate representation altogether. It's literally a useless internal implementation detail. At best it should be behind a verbose debugging switch that is off by default. The problem...

[Yeah I was the one that noticed they didn't work any more with a recent change](https://github.com/sveltejs/language-tools/issues/678#issuecomment-814524420). Forgot to add that step into this issue description.

You can try the above code, it leaks for me. Error.stackTraceLimit = 10, the default