Warning: Our component library doubled in size after one Figma plugin change

I manage a design system for a team of 15 at a mid-sized agency in Denver. Six months ago we let a junior dev install a plugin that auto-generated variants for every button state, and suddenly our file went from 300 components to over 600. Nobody noticed until the load times hit 45 seconds and our production builds started failing. Has anyone else dealt with a tool update that quietly bloated your system before you caught it?

2 comments

2 Comments

finley_walker5712d ago

Huh, believe it or not I was just reading about this exact thing in a design systems newsletter. They talked about how a lot of these plugin updates don't warn you about the actual impact on file size and performance. 45 seconds for load times is brutal though, that's basically unusable for any real workflow. I've heard some teams now run a diff report every time a plugin touches the component tree, just to catch this kind of bloat before it hits production.

reeseanderson12d ago

45 seconds is barely even noticeable if you're working on something complex though. Isn't that the whole point of having a beefy machine and dedicated workflow tools?