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.

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

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

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

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?

What is "it"? I don't think TS actually reads this out at all

When you enable the file watcher setting, TS Server says > Falling back to legacy node.js based file watching because of user settings

tsserver says that? Or is it the VS Code extension? (I don't remember that message)