In TS <= 4.8, fixedPollingInterval is the default watcher configuration. Starting in TS 4.9, they changed the default to useFsEvents. This is generally a good thing! It means that users get more efficient, more effective FS watching.
For us, though, in the Actions runner, this causes instability in our tests. Some days it's totally fine, but others it can cause any of our tests that rely on FS events triggering behavior in glint --watch (or glint --build --watch) to fail at random.
This PR sets up any test projects generated with the glint-monorepo-test-utilsProject class to continue using the fixedPollingInterval strategy. There shouldn't be any reason end users need to switch; this is just about FS watcher stability in the Actions runners.
In TS <= 4.8,
fixedPollingIntervalis the default watcher configuration. Starting in TS 4.9, they changed the default touseFsEvents. This is generally a good thing! It means that users get more efficient, more effective FS watching.For us, though, in the Actions runner, this causes instability in our tests. Some days it's totally fine, but others it can cause any of our tests that rely on FS events triggering behavior in
glint --watch(orglint --build --watch) to fail at random.This PR sets up any test projects generated with the
glint-monorepo-test-utilsProjectclass to continue using thefixedPollingIntervalstrategy. There shouldn't be any reason end users need to switch; this is just about FS watcher stability in the Actions runners.EDIT: Still a bit to do here