🧁 vanilla-extract: what's all the fuss about? (#58)
I hope you all had a great weekend! I know I did -- I love a crisp September morning!
At work, we've been using the library for about a month now, and I have to be honest, it's totally living up to the hype.
It dovetails nicely with the way I model design tokens conceptually in my mind, and its opinionated approach can lower the barrier to entry for early design systems teams.
How does it solve common design tokens challenges?
1. Better performance
2. Prevents breakage when tokens are edited or deleted
I've seen teams accidentally delete or rename a design token and cause breaking changes in consuming applications.
vanilla-extract provides type-safety via CSSType. If someone accidentally deletes, renames, or misspells a token, it will trigger a TypeScript error describing exactly what went wrong.
3. Opinionated approach to theming
One of my favorite aspects of vanilla-extract is its opinionated approach to theming. Tokens and theming can be complicated to implement the first time around, and there are many potential approaches.
Early-stage design systems teams push forward more confidently by leveraging the experience of the design systems team over at Seek.
Have you used vanilla-extract? What did you think? Reply to this email and let me know.
If you like this newsletter it would really help me if you shared it with your friends. Tweet about it, post on LinkedIn, and share in slack channels. Building this community can lead all of us to more job opportunities, guest posts, and connections.
Do you want design systems tips and tricks sent to your inbox?