Killing `pnpm dev` results in a defunct `esbuild` process

I've created a fresh solid start project with the default template. I noticed that pressing Ctrl+C causes a esbuild process to linger around in the defunct state.
11169 pts/1 Z 0:00 [esbuild] <defunct>
11169 pts/1 Z 0:00 [esbuild] <defunct>
So every time I start and stop the process another defunct esbuild process is created. I guess this really is a vinxi or vite issue. I just wanted to ask here if anyone else ran into this issue and knows a fix.
1 Reply
Michael P. Jung
Michael P. JungOP7d ago
I "fixed" it for the time being by wrapping the vinxi dev with tini -s. So my package.json looks like that now:
- "dev": "vinxi dev",
+ "dev": "tini -s -- vinxi dev",
- "dev": "vinxi dev",
+ "dev": "tini -s -- vinxi dev",
Now the zombie processes get reaped. It's not ideal but solves my biggest pain point of an ever growing process list. Mmmh... well... that didn't really solve the issue it seams. The more I dig into that issue it seams to be more related to an issue with vscode,dev containers and docker than anything else. Yeah... definitely a dev container issue. I even end up with some defunct git processes... O_o

Did you find this page helpful?