5 ms·
Typescript in watch mode in a background process (with compilation output on or off) is the default recommendation here. (and what I do, alongside prettier form
by Normal_gaussian 4y ago
Typescript in watch mode in a background process (with compilation output on or off) is the default recommendation here. (and what I do, alongside prettier formats and some macros).
That is effectively what happens in VSCode, via the lsp, so I'm guessing something is being lazy and its a bug with the integration.
- WorldMaker 4y agoMy understanding is that VSCode's use of the LSP does a lot of "horizon shortening" to keep things performant in a large workspace. If the workspace is small enough it does seem to check every file all the time, as the workspace grows it starts to prioritize open editors and gets lazier about checking other files, and I've even seen situations where it prioritizes the current editors (visible tabs/splits) entirely over even the rest of open editors. I don't think it's necessarily "a bug", but it's certainly seems an intentional laziness to prioritize the editing experience over the compile experience. Which is a long winded thing to say that it's still often useful in VS Code to keep a full tsc --watch process around even if you think the LSP's horizon is wide enough to catch everything because tsc --watch will always have different performance priorities to VSCode's editing experience.
- johnfn 4y agoWow, can't believe I never thought to try this before. That's a huge improvement, thanks!