Polymer Summit 2017: NPM time
Polymer 3 is coming and it’s finally time for ES6 Modules and NPM (Yarn to be more specific) passing through SSR of Web Components, bye bye Bower and 2010 trends.
The new home of Polymer: NPM.
To be more specific, the new real home for Polymer is Yarn. That’s because only Yarn could achieve what Bower and NPM can realize together.
This is an extremely good news. Here’re some reasons:
- (As we all know) Bower is going to be deprecated.
- HTML imports won’t be developed by other browsers except Chrome.
Furthermore this is the right choice to start being a real React-like libraries competitor, pursuing the Web Components road and avoiding the Virtual Dom.
That’s not all: in the coming months we will be able to remove polyfills at all. Well, maybe not in all the browsers, but we can see that the interest in implementing such beautiful and useful specs is high. I’m talking about Custom Elements, Shadow DOM and of course JS Modules.
Browsers’ developers and companies are trying to go in the same direction, and it seems that we can finally achieve more consistency between all major browsers pursuing this road (IE11 IS NOT included in major browsers).
A brand new templating system.
And the day of Webpack is here. We are finally able to use Webpack as “normal people” importing Polymer and its .js files forgetting about the old .html implementation.
The new lit-html templating system developed by the Polymer team will be the real “plugin” able to bring Polymer to the next level, really close to the React developer experience.
But lit-html is not built-in within the Polymer core, indeed, the core exposes the possibility to use a static getter on the template().
What’s next? Interoperability between components library.
To be more specific interoperability between Custom Elements and every library on the JS marketplace.
Rob Dodson and some other awesome guys gave us a new and fresh vision, comprehensive of a test suite, about (for now) the four main libraries on the field: Angular, React, Preact and Vue. I think the results are pretty nice, and, as Rob said, the problems can be easily fixed.
Checkout the custom-elements-everywhere website to learn more about it.
Waiting for this shared compatibility to be achieved, the current vision of what concern the future of Web Components is shining gold, and this aspect wasn’t so clear before this regenerating Polymer Summit 2017.
SSR (SEO problems) and Rendertron.
Among the topics of the second day, there are two that caught our attention as were almost considered as an utopia during the last few years of Web Components spreading. We are talking about Server Side Rendering Web Components and how to solve the SEO problems that are killing the PWAs around the web making them not crawlable by all the search engine’s (and not) bots.
The biggest problem of SSR for Web Components is the Shadow DOM. The beautiful standard that solved our problems of scoping CSS is actually a problem on the Server Side.
Check out Sam Li’s keynote to learn more: Solving SEO with Headless Chrome.
A beautiful place: Copenhagen.
And after the first day “After party” we couldn’t miss to visit the beautiful city of Copenhagen.
It is a really peaceful place where to spend time even in August, with a perfect climate. Well at least, until now, the Polymer guys have never been wrong choosing the Summit city!