Post

@jakebailey.dev Hey there, I was wondering if you had any insight into github.com/microsoft/Ty... and what the best practice is nowawadays. > Falling back to legacy node.js based file watching When testing new native it **feels** slower than using the node based one with excludes.

github.comTypeScript slow project load times for large projects on MacOS · Issue #60832 · microsoft/TypeScriptDoes this issue occur when all extensions are disabled?: Yes VS Code Version: v1.96.2 OS Version: MacOS TypeScript: v5.7.2 (workspace version) Node.JS: v20.18.0 Steps to Reproduce: Add the followin...

14/2/25, 7:22 pm0 reposts2 likes

Jake Bailey

@jakebailey.dev

14 Feb 2025

I don't have any more information than what's on github Every time we change file watching, it helps some people, and hurts others, to the point where I can only right now suggest futzing with settings to find what works best for your system

Stanzilla

@stanzilla.dev

14 Feb 2025

Hah okay, thank you. I was mostly curious to know if there is a way to ignore directories with the new native mode or if it has some smarts included that ignore node_modules etc

Jake Bailey

@jakebailey.dev

14 Feb 2025

The new watch goes through VS Code, so all of their settings take effect, and they have watcher exclusions as settings.

Stanzilla

@stanzilla.dev

14 Feb 2025

That's what I was confused about, setting "files.watcherExclude": { "**/node_modules": true }, makes it fall back to the node.js based one. Is there a different setting?