Rollup isn't focused on node, if it was commonJS support would be bundled into the code. It's got a small and focused core that aims for esm (I regard the othe

Rollup isn't focused on node, if it was commonJS support would be bundled into the code. It's got a small and focused core that aims for esm (I regard the other output formats supported as esm -> that format). You do need to plug stuff in rather than having a batteries included experience. But that is a strength imo where you want to worry only about what you need. I do recommend adapting an existing config when using it in a new project, or creating your own templates/"create-x-app" wrapper. I use it for my home projects, and several work ones. It's "lower level" than Babel or parcel but that means I can set it up to compile both a lean, modern esm build, and a legacy IE11 compatible polyfilled systemJS bundle much easier than I can in webpack with its proprietary bundle format or parcels zero config. I will admit that node resolve and commonJs rollup plugins are pretty much a required part to work within the npm ecosystem right now, so it is a bit more boilerplate-y than I'd like.