Jake Bailey

> Sorry, I commented on a couple of other old issues before I read some comments about trying to group things by at least versions (in my defense, there's a...

`--extendedDiagnostics` should show memory usage, or you could artificially lower the max memory with Node's `max-old-space-size`. That or provide a repro.

It seems like we are still somehow concurrency unsafe through `HandleNoEmitOnError`. Incremental is still not doing the expected locking.

We only support pull diagnostics (`textDocument/diagnostic`, https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_pullDiagnostics). Push diagnostics are currently only used for config file errors. Does eglot not support this? (It's a significant architectural change to use push...

Like tsserver before it, the new language server only shows diagnostics in opened files. #2169 covers diags for unopened files.

I don't think that's accurate; package managers gracefully handle installing multiple versions of the same libraries all the time, so they must be able to handle multiple sets of transitive...

> Why? This is because npm actually did not figure out what you want. When it saw @microsoft/fast-foundation-v3's package.json says it has a dependency of @microsoft/fast-element, it just fetches the...

TS 5.0 is well out of support, no? (See also, https://github.com/DefinitelyTyped/DefinitelyTyped?tab=readme-ov-file#support-window, which is as conservative as we get)

That import only worked due to defaulting to an older resolution mode in 5.9, which are deprecated in 6.0 and removed in 7.0. If you use a newer resolution mode,...

I'm not entirely convinced it's a good idea to port these functions now, when they aren't be used or tested, and may not actually be useful for future code.