Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

file watcher is very CPU hungry in ^8.3.4 #1283

Open
holic opened this issue Jan 31, 2025 · 0 comments
Open

file watcher is very CPU hungry in ^8.3.4 #1283

holic opened this issue Jan 31, 2025 · 0 comments

Comments

@holic
Copy link

holic commented Jan 31, 2025

We use tsup with turbo in our monorepo to build ~30 packages. I'm on node 20.18.2, but this issue seems present in node 18 as well.

I recently upgraded from tsup 6.7.0 to 8.3.6 and noticed our local build/watch step (tsup --watch) started consuming significantly more CPU (70-100% per process rather than 1-2%), seemingly due to the file watcher. I downgraded back to 6.7.0 and slowly upgraded through each major version, then minor/patch versions, to find out where the issues started.

8.3.0 is the last version where tsup is ~the same CPU usage. Once I bump past 8.3.0, CPU per process spikes and stays high until killed.

Some notes:

  • I first tried using pnpm.overrides to downgrade esbuild and rollup to specific prior versions, but didn't see any effect.
  • 8.1.1 just doesn't work and all builds exit with Cannot find module '@swc/core' (fixed in 8.1.2)
  • 8.3.1 and 8.3.3 don't appear to be installable from npm, despite it being in releases (No matching version found for [email protected])

Happy to provide more info and continue debugging if helpful!

@holic holic changed the title file watcher is very CPU hungry in ^8.3.0 file watcher is very CPU hungry in ^8.3.4 Jan 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant