Run & review this pull request in StackBlitz Codeflow.

✅ Deploy Preview for fastidious-cascaron-4ded94 canceled.

@AriPerkkio what do you think?

Why not just process.title = 'vitest'? Many process list parsing tools can match that out of the box, but can likely not match node (vitest). Also, put a try-catch around it for unsupporting runtimes.

Why not just process.title = 'vitest'? Many process list parsing tools can match that out of the box, but can likely not match node (vitest). Also, put a try-catch around it for unsupporting runtimes.

Because people look for the "node" process usually. This is why I asked @AriPerkkio opinion here (this change was discussed in a team meeting)

Why not just process.title = 'vitest'?

If your tests spawn external processes you won't see those if you look for vitest. Minimal repro below:

process.title = "vitest";
setTimeout(() => {}, 5000);

$ node repro.mjs

$ pgrep node
> no results

This works:

process.title = "node (vitest)";
setTimeout(() => {}, 5000);

$ node repro.mjs

$ pgrep node
76662       # <--- Yes this is good

$ pgrep vitest
76662          # <-- also here

$ ps $(pgrep node)
  PID   TT  STAT      TIME COMMAND
76662 s008  S+     0:00.04 node (vitest) 

I prefer pidof over pgrep because it's a exact match it won't find it with the current name:

$ node -e 'process.title = "node (vitest)"; setTimeout(() => {}, 60000);'

$ pidof vitest # fails

$ node -e 'process.title = "vitest"; setTimeout(() => {}, 60000);'

$ pidof vitest # works

Also, what if vitest is run in another runtime like bun or deno? It's wrong to identify as node in such cases.

Also, what if vitest is run in another runtime like bun or deno? It's wrong to identify as node in such cases.

This should not be a problem because:

1. bun doesn't support process renaming
2. Deno doesn't support running vitest

bun doesn't support process renaming

It will eventually and then you'll have to needlessly change the process name again.

I still think vitest is the ideal process name but if you persist on this silly name, use at least path.basename(process.argv[0]) to make it agnostic to the runtime.