Use a less greedy file watcher for lower dev CPU usage #2293
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This proposes using a less greedy file watcher for our default yarn start setup
It also removes the max header size because we now use session sharing rather than huge url sizes
The less greedy file watcher helps reduce CPU usage considerably from ~6% CPU (what i see pretty much constantly while
yarn start
is idling, similar to the ~7% reported in the issue) to nothing (in issue it is reported as ~0.2%)microsoft/TypeScript#31048
e.g. this is pretty much what my computer looks like 100% of the time developing jbrowse

The reason why this PR is in question is that Typescript decided not to make it their default at the time being due to some rare caveats but IMO it is rare enough that we could make it default
Laptop temp cooler===happy