Zombie esbuild processes

[mhanberg]

I can't seem to run the esbuild with the --serve functionality without leaving a zombie esbuild process when I stop it.

I have tried using the CLI and using the JS API, both seem to leave a zombie process.

This is what I've tried with the JS API so far.

const baseConfig = {
  entryPoints: ['./js/app.js', './css/app.css'],
  target: "es2015",
  bundle: true,
  outdir: "../priv/static",
  plugins: [PostCSSPlugin] // plugin defined earlier in the script
};

function onRequest({ path }) {
  console.log(`building ${path}`);
}

esbuild.serve({ onRequest }, baseConfig)
  .then(server => {
    console.log("Server running for esbuild");

    process.on("exit", code => {
      console.log(`stopping the server with exit code ${code}`);

      server.stop();
    });
  })
  .catch(() => {
    console.log("Crashing esbuild");

    return process.exit(1)
  });

Any ideas?

[evanw]

I can't reproduce this. What platform are you on? And how are you stopping it? Does it happen without the plugin?

[mhanberg]

• This is on macOS.
• started as a "watcher" with the Phoenix web framework (elixir).
• I ctrl-c out of the phoenix dev server. it starts the esbuild process via an erlang port, not sure exactly how that get's shut down
• I do see it without the plugin

My priorities have shifted and I don't have the time to see this through. I'll close this and circle back if I find some time.

Thanks for your response 🙇.

[evanw]

Well I think I finally got it. I came across it due to some other work. It was a stray ! of all things.

[mhanberg]

I'll update and see if it's fixed on my end. Thanks for your work on this!

[mhanberg]

Looks good 👍