Error checking package import bundle size for node packages with size-limit-preset-node-lib about size-limit HOT 6 OPEN

After investigation I have figured out that whole node-fetch package was replace with some small esbuild global.fetch polyfill

It is expected behavior. Why it doesn’t work for you?

from size-limit.

After investigation I have figured out that whole node-fetch package was replace with some small esbuild global.fetch polyfill

It is expected behavior. Why it doesn’t work for you?

Because the package I'm checking bundle size is developed to be used in node projects only, and I'm interested in what the actual bundle size for node project not supporting fetch

from size-limit.

In my world, there is no such thing as bundle size for Node.js project since you do not need bundlers for Node.js.

What do you mean for “bundle” in Node.js and why do you care about it’s size?

from size-limit.

Our backend is build on top of AWS lambda, which have size limit of 50mb.
So there is cold start problem when it comes to lamdas https://khalilstemmler.com/blogs/serverless/5-ways-to-manage-lambda-cold-starts/#Understanding-the-Cold-Start-Problem
While bundle size is not primary first problem with cold starts, we are still care about reusable packages bundle size to make it each lambda as small as possible, to ensure smaller cold starts

from size-limit.

I was able to fix this by replacing size-limit-preset-node-lib with undocumented modifyEsbuildConfig option and setting esbuild platform to node.

from size-limit.

Interesting problem :-/

Seems like you need to set custom esbuild config with a target to Node.js https://esbuild.github.io/api/#target

It will disable auto-polyfills.

Try to use config option in Size Limi config.

from size-limit.