Vaadin web components 25.0.0 stable release notes

📢 We've reached an important milestone at @vaadin.com: Vaadin web components 25.0.0 fully based on @lit.dev instead of Polymer are finally released as stable!

github.com/vaadin/web-c...

What it takes to build a set of Vaadin components | Vaadin An inside look at eight years of building and refining Vaadin components: what went well, what we changed, and how we keep shipping better major releases.

Vaadin 25 is almost here!
To mark the milestone, Senior Software Engineer Serhii Kulykov looks back at 8 years of Vaadin components: the key decisions behind versions 10, 14, 22 and 25, and what we’ve learned about stability, accessibility, and simplicity along the way. vaadin.com/blog/what-it...

What it takes to build a set of Vaadin components | Vaadin An inside look at eight years of building and refining Vaadin components: what went well, what we changed, and how we keep shipping better major releases.

Published a blog post about 8 years of building Web Components at @vaadin.com and the lessons learned along the way. It's been a great journey so far! And by the way, today we have reached Vaadin 25 release candidate.

vaadin.com/blog/what-it...

Most of the logic we added on top of Lit was actually needed to reuse mixins extracted from our Polymer based components. Over time we'll improve the code to use Lit lifecycle callbacks, e.g. updated() for property observers.

Using Lit provides a lot of benefits related to not having to write boilerplate code for reactive properties, attributes etc. We do have a few vanilla custom elements used internally though.

10 years of building Web Components: the story of <vaadin-combo-box> A story about building Vaadin web components

10 years of building Web Components at @vaadin.com: celebrating the "anniversary" of <vaadin-combo-box>!

Check out this blog post to learn about our journey and how we finally migrated to @lit.dev:

dev.to/webpadawan/1...

Neat, looks like MDN's new frontend is built with @lit.dev