Performance - what's the reason behind reinitialising watcher on every restart?

[koniferous22]

Issue description

I've been dealing with ts-node-dev restart on file change that takes about 25sec (larger codebase). Note that compiled directory in /tmp filesystem, should be initialized, so at this point minimum transpilation should take place. In such case the limiting factor seem to be emitted events, from patched require.

After debugging transpiled code from node_modules with snippet above (transpiled hook.ts - section where callback is fired)
ts-node-dev on each restart fires in my case about 2500 {required: "filename.ts"} events. However the sole purpose of the events seems to just initialize watcher, that also gets destroyed before each restart.

ts-node-dev/src/index.ts

Lines 251 to 252 in f0c3e7e

	watcher.close()
	watcher = initWatcher()

Tried removing it from the restart function, worked fine on my workstation & worked with TS errors. So just wanted to double check if there's something.

Context

OS version (is it docker or host?), ts-node-dev version
Host - Apple M1 macOS Monterey, 1.18

Did you try to run with ts-node?
Yes

Did you try to run with --files option enabled?
Yes

Did you try to run with --debug option enabled?
Yes

Do you have a repro example (git repo) with simple steps to reproduce your problem?
No

[vantaboard]

That is the ugliest font I have ever seen.