Managing a growing component library can be quite a puzzle. The more it expands, the heavier it gets with larger bundle sizes, dependencies multiplying, and the overall complexity going through the roof. And let's face it, it's a headache when every project using the library ends up dragging the entire package, even when they just need a single component 🤦.

But worry not! That's where tree-shaking steps in to save the day!

In this talk, I will spill the beans on my experience fine-tuning a React component library that boasts over 40 components and serves various projects. We'll roll up our sleeves and dig into the world of tree shaking, talk about what you need to get it up and running smoothly and untangle some tricky terms like commonJS vs. ES modules, peer dependencies, and the whole multi-bundle exports thing.

Get ready for some down-to-earth, practical insights that can save you a refactor or two.