Last year, we had announced how excited and proud we that trivago was joining our family of supporters on Open Collective.
Throughout this year, we’ve checked in periodically with the trivago engineering team to ensure that their $120,000 investment was paying off.
We spoke with Patrick Gotthardt, who oversees all front-end engineering work at trivago, and asked him to summarize their experience sponsoring webpack this year.
“Being a data-driven company we of course also tried to collect some insights into how the sponsoring is affecting us as a company. There’s no discussion about the technical value of webpack within trivago. The work you all have done truly speaks for itself and is absolutely amazing. I can’t wait to get my hands on some of the features in Legato and to see how they’ll impact the productivity and happiness of my colleagues and how they might help us to deliver a better product for our users. …
If you have been following the Google Summer of Code projects, you’ll notice that this year webpack is among the list of organizations participating this year!
Today we’re happy to announce that webpack 4 (Legato) is available today! You can get it via yarn or npm using:
$> yarn add webpack webpack-cli --dev
$> npm i webpack webpack-cli --save-dev
We wanted to start a new tradition by giving each of our major releases a codename! Therefore, we decided to give this privilege to our largest OpenCollective sponsor: trivago!
So we reached out and here was their response:
[At trivago] we usually give our projects a name with a musical theme. For example, our old JS Framework was called “Harmony”, our new framework is “Melody”. …
From all of us at webpack: 🎆🎉 Happy New Year! 🎉🎆
The Contributors Guide to webpack is a multi-part publication series outlining the many ways that you can learn about, and contribute to the webpack open source project. You can read the first article in the series here!
In Part 1 of this series we learned about the packages that reside within both the webpack and webpack-contrib GitHub organizations! In Part 2, we discovered
Tapable , learned that it is a ~230 line library similar to NodeJs’s
EventEmitter , and found that it powers the entire [webpack] plugin system.
In addition to this, we learned how webpack creates tapable instances (Classes that
extend Tapable ) and how [webpack] plugins register to them and execute their functionality. Finally, we learned about each tapable instance that exists in webpack and what their purpose is. …
With webpack becoming the tool of choice for many companies across the world, its success and that of the companies that rely on it are intertwined. Ensuring the future of webpack is a no brainer for everyone who benefits from it.
Over the past two years we have collaborated with engineers at trivago as webpack is vital to their technology stack. Today we are thrilled to announce trivago as the newest sponsor to the webpack open source project.
trivago’s business mission is clear: be the traveler’s first and independent source of information for finding the ideal hotel at the lowest rate. …
One of the signature features of webpack is its use of the “dependency graph” to manage and bundle assets.
At webpack, we would like to shift our focus to supporting more module types. One of these module types we would like to treat as a first-class citizen is WebAssembly. …
A few weeks ago I announced that I was leaving my job to go work at Microsoft. I soon realized that I would leaving behind a lot of work for my team at Mutual of Omaha.
As a maintainer of webpack, I knew had really pushed the build tool to its limits. Through advanced webpack techniques, our team was able to re-architect MutualOfOmaha.com into a multipage app that was at the same time a Progressive Web App.
But who was going to take this over this complex implementation when I was gone? I had handled a majority of our webpack setup and configuration. …
This post is dedicated to my wife Mallory. Without her patience and support to allow me to pursue my endeavors, I would not be where I am today. ❤
Today, with a ginormous lump in my throat, I gave my current employer my 2 weeks notice, and informed them that I would be leaving Nebraska, to join Microsoft in Seattle, Washington. 😍
I will be joining the EdgeHTML team as a Program Manager for F12 DevTools. (tl;dr I’m gunning to be the Paul Irish of Microsoft 😂)
I’d be lying if I said it felt like the odds were not stacked against Microsoft, the Edge Platform, and its DevTools. But I accepted this position for a reason: Developers come first. …