Code splitting is creating many small unnecessary chunks about esbuild HOT 1 OPEN

The pink chunks are what we talking about:

The general chunk structure is pretty nice. But the more import('...') entries you create, the more of these pink <2kb chunks appear

For us these micro chunks are created by:

1. Redux actions that are used at 2+ places. These chunks look like

import{Mb as e}from"./chunk-OMCORABT.js";var t=e("[Product] Clicked");export{t as a};

2. Or assets from { loader: { ".webp": "file" } that are used at 2+ places. These chunks look like:

var l="./media/image-FZ7VCKMX.webp";export{l as a};

Would be awesome if esbuild could inline the file loader string or via a minChunkSize pull into the largest parent chunk.

Gzip and less http requests would make this more efficient. And you reduce the chance of running into the maximum allowed requests limit.

from esbuild.