I find webpack to be slow and complicated to understand whenever changes are required. So I decided to see how much work it would take to completely replace our frontend-build (wrapper around webpack + babel + etc.) with a more modern approach - specifically using Vite . I picked a small MFE, the pr…

If we can find reasonable drop-in replacements for the webpack plugins/loaders we use, and (top of mind for me) a module federation implementation that functions well, we can probably simplify and speed up our builds by switching to another bundler. And if it makes the Typescript migration easier, …

Hot take: I like that the diff is small. I like that it allows us to deprecate a dependency (frontend-build). I like that it’s all faster. Hot questions: will it work with frontend-plugin-framework? Will it work with module federation (a.k.a The New OEP-65 )?

[image] arbrandes: Hot questions: will it work with frontend-plugin-framework? That one I can answer quickly: Yes :slight_smile: feat: A leaner example app that is built using Vite by bradenmacdonald · Pull Request #54 · openedx/frontend-plugin-framework · GitHub [image] djoy: Is Vite t…

But personally I wonder if we could use Vite/Jest in such a standard way that the required per-MFE config is so minimal that there is no need for frontend-build at all. I like the spirit of this idea, but am admittedly skeptical. My hot take is that even if we are able to get our configuration f…

I’ll try to look into how this works with module federation and also if the vite functionality can just be pushed into frontend-build as a toggleable option, making the per-MFE changes even smaller.

[image] braden: The Vite production build uses half as much memory TAKE MY MONEY!

Vite was one of several options identified in Discovery: Faster build tool · Issue #126 · openedx/wg-frontend · GitHub . We ultimately closed that issue about a year ago because Vite and Turbopack had recently been released, seemed more promising than the other options we had identified, but weren’…

I have a new demo, that builds on my previous demo of the Vite-based profile MFE. This one shows a “shell” MFE that provides the header and footer, and dynamically loads the profile MFE as needed within the shell. It only loads a single copy of React, Paragon, etc. [image] GitHub - open-cr…

Just wanted to chime in with some additional appetite for Vite-based MFE builds vs. Webpack in support of future transitions to React Router 7 (Open edX currently runs React Router 6). With React Router 7, apps may use either Declarative/Data modes (like we do today), or Framework mode which brings…

Experiment: build an MFE with Vite instead of frontend-build/webpack

Working Groups Frontend

regis (Régis Behmo ) April 5, 2024, 9:06am 7

TAKE MY MONEY!

Topic		Replies	Views
OEP-65: Frontend composability next steps and a bit of visionin' Architecture	9	443	September 24, 2025
Microfrontends: a retrospective Development	19	3302	February 15, 2022
OEP-65 adjacent: A frontend architecture vision Architecture	15	545	June 27, 2024
Deploying microfrontends (MFEs) in a single container Build-Test-Release devops , mfe	15	4268	October 5, 2021
A proposal for the evolution of frontend plugins/modules Architecture plugins , frontend	6	216	November 14, 2024

Experiment: build an MFE with Vite instead of frontend-build/webpack

Related topics