On the other hand you can just have Webpack target Node, which sort of results in the same thing with a Webpack bootstrap around it. With exactly the same downsides, but convenient if you're already using Webpack for your clientside code.
I've recently set up a project with server and browser JS (and some shared things), having both bundled by Webpack and just NPM scripts to glue everything together. It's nice to have a single powerful tool that can handle pretty much all of your bundling and transpiling needs, the mental overhead gets smaller that way.
On the other hand you can just have Webpack target Node, which sort of results in the same thing with a Webpack bootstrap around it. With exactly the same downsides, but convenient if you're already using Webpack for your clientside code.
I've recently set up a project with server and browser JS (and some shared things), having both bundled by Webpack and just NPM scripts to glue everything together. It's nice to have a single powerful tool that can handle pretty much all of your bundling and transpiling needs, the mental overhead gets smaller that way.