Origami Newsletter, March 2019
TL;DR:
This issue features the new Origami website with a new design and new documentation, a highlight of the improved service that the Polyfill Service provides, and an explanation of how ECMAScript Modules broke our components.
Top three things
These are some of the bigger things we’ve worked on or released over the last month.
Origami Website Launch
This month we’ve successfully launched the new Origami website. It is officially out of beta, and implements all of the new features of o-layout, which has unified the design across our documentation and our registry.
In addition to the visual changes, this launch is packed full of new documentation and a more digestible specification. You can find more detailed information about the launch in this blog post
As always, we welcome any feedback or questions you might have about the new website’s content and UI.
Polyfills served
Three years ago, the Polyfill Service served 400 million polyfills per month. Today, it serves 800 million every day 💪.
ECMAScript Modules vs CommonJS
We attempted to replace CommonJS with ECMAScript Modules across some of our components to align them more closely to the standard of JavaScript that is used in web browsers (ECMAScript Modules). The intention was to get to a place where teams would not need to compile Origami components’ JavaScript in order to use it.
This shift caused a breaking change as it brought about client-side JavaScript errors for some projects and users. We have since reverted those changes and are working on a different approach.
If there is anything that we might have missed or any questions you might have, please get in touch with the team.
Special thanks
Special thanks to Rhys Evans for implementing the most recent version of o-layout so quickly after its release, and flagging small bugs for us 🙌.
Broader update
A digest list of other things that have happened over the last month.
*[TL;DR]: too long; didn’t read
