Why?

time px index.js bundle.js real 0m0.015s user 0m0.006s sys 0m0.006s

Your bundler is a tool. It’s supposed to help you, not slow you down.

You know the feeling. You make that tweak, hit ⌘S ⌘Tab ⌘R , and… nothing changes. You get the old version. You beat the bundler. You wait a few seconds, hit ⌘R again, and your changes finally show up. But it’s too late—you’ve lost momentum. It’s exactly the wrong shade of pink. You spelled “menu” with a z. The bug still happens sometimes.

Rinse. Repeat. Ten cycles later, things are looking good. It’s time to git commit . But you spent more time waiting than working. And it’s your bundler’s fault.

Pax is a bundler. But you’ll never beat it. Why?

It’s parallelized. It makes the most of your cores.

It makes the most of your cores. It’s minimal. It isn’t bogged down by features you don’t need.

It isn’t bogged down by features you don’t need. It knows exactly enough about JavaScript to handle dependency resolution. It doesn’t even bother parsing most of your source code.

Don’t waste time waiting for your bundler to do its thing. Use Pax while you’re developing, and iterate to your heart’s content. Use your super-cool, magical, slow-as-molasses bundler for releases, when you don’t care how long it takes to run.