ConnectKit package size too large

[nikmace]

Hello, is there something being done about this package being too large? The builds become very heavy when importing anything from ConnectKit. Here is a picture of the import cost. Could there be some optimization of this package or its already at its smallest?

[lochie]

@nikmace woah this doesn't seem right at all, thanks for catching this issue

I'll review when I'm back in office, might be an issue from how we recently moved our build process to a pure ES module, but will keep you notified

[nikmace]

Thanks for the reply. The package is great and very useful to us, can't really find a better alternative that works like this out of the box. It was just strange to me why would this package take up so much space.

Just to add to this, wagmi is also a big boy, but I can understand why. Here is a picture of the import cost.

This is the output of our build (nextjs):

The _app.js chunk becomes very large. We've used all kinds of optimizations but the First Load JS is not coming down.

[lochie]

Based on that output I'd say that the calculation for the import cost might actually just be incorrect as it looks to be tree shaking is working correctly (else wise _app.js would be way higher than 452kb).

It's probably worth noting that the ethers package has usually been the culprit to bundle size being high and there aren't many alternatives to this dependency yet.