Proposal - use rollup instead of esbuild

[just-boris]

There is a known and not yet fixed issue with rollup: evanw/esbuild#3899

Because of this issue, libraries cannot create reusable aliases for env vars. This is unfortunate, because it reports size increase which can be avoided

[ai]

Is it possible to manage CSS and other edge cases? I remember that Rollup was a low-level tool.

[ai]

Technically we can just create a rollup plugin for Size Limit so team can choose.

But I need some bigger motivation to start supporting another plugin. Can you provide any real-world example where Rollup will give a big difference?

[just-boris]

Here is an example: https://github.com/just-boris/size-challenge

In our project we have a reusable isDevelopment constant: https://github.com/search?q=repo%3Acloudscape-design%2Fcomponents%20isDevelopment&type=code

Because of that esbuild bug, the dead code elimination does not work.

In the example project there is 8% size improvement by using esbuild without rollup and any code changes.

(btw, vite in library mode uses rollup too, achieving the same result)

[ai]

Sure, please send PR with a new plugin.