|Date Created||June 24, 2019|
|Date Ended||February 20, 2020|
|Slack||#wg_webpack (only accessible from within the company)|
|Google Doc||Webpack Working Group Agenda (only accessible from within the company)|
|Epic||Webpack Working Group|
GitLab has been using webpack to bundle its frontend assets for three years now, and it has enabled us to do some great things, but at the same time we are not taking full advantage of its strengths (e.g. code splitting and performance improvements) and we are letting it get in the way of developer productivity (high resource consumption, crashes, broken debug tooling, etc) by not adequately addressing issues as we scale. This working group aims to both fix the most glaring issues with our frontend build tooling and to re-align the frontend development guidelines to promote best practices for performance and maintainability using webpack's underutilized features.
Increase engineer productivity by fixing and improving our frontend build tooling, and put both guidelines and automated processes in place to ensure best practices are followed for performance and maintainability.
<script type="module">respectively) with only the code transformations and polyfills needed by each target.
|Working Group Role||Person||Title|
|Frontend Lead||Mike Greiling||Senior Frontend Engineer|
|Facilitator||Lukas 'Eipi' Eipert||Senior Frontend Engineer|
|Member||Jake Burden||Frontend Engineer|
|Member||Tristan Read||Senior Frontend Engineer|
|Member||David 'DJ' Mountney||Senior Distribution Engineer|
|Executive Stakeholder||Christopher Lefelhocz||VP of Development|