Andrey Sitnik

Oops. I forget to remove another trick. It help me adding `import: '{ escape }',` to checks.

I am working on a better solution

@ludofischer webpack 5 started to remove any exports from bundles if we do not pass `import` option. Any idea how to disable it for non-`import` cases?

@ludofischer I added `shakable-webpack-5` with a test for this case

> In my case all .cjs files' sizes were increased approximately by 140-150 bytes. @yumauri we already subtract wrapper size from the bundle size. In my case, I got 20-30...

@ludofischer we can add some optional like `importAll: true` or `import: "*"` and use [`import`-option code](https://github.com/ai/size-limit/blob/main/packages/webpack/get-config.js#L12-L24) to generate file like: ```js import * as all from '../entry.js' console.log(all) ```

> For my own libraries, I would prefer to use the path option to point to example code that uses the library instead of the library entry point. The problem...

> What about outputting best/worst case numbers by default (so both the current configuration and using the console.log(all) trick)? That way people do not need to bother with extra options....

> Which limit would make CI fail though? Should the limit in the size-limit config now mean 'worst case limit'? My idea is to use `import * as all from...

I can only wait a reply from `estimo` maintainer