Working on a big Angular/Typescript monorepo lately I got one VSCode Helper process constantly staying at 100% CPU usage. Watching the Process Explorer (Help > Open Process Explorer) identified it as a fileWatcher process.

Excluding the node_modules directory from file watching by adding **/node_modules/** to the files.watcherExclude key in the VSCode Settings put it down to 0% most of the time.

Reason for that is a bug in the @parcel/watcher module VSCode uses. See https://github.com/microsoft/vscode/issues/226050 for details.

(I’m using VSCodium btw which is VSCode without Microsoft telemetry.)