Testing
Module Federation was originally a Webpack 5 feature, but @originjs/vite-plugin-federation brought it to the Vite ecosystem. Testing Vite-based federated modules requires a different setup than Webpack — Vitest is the natural testing tool, and the module resolution strategy for federated imports needs specific configuration. This guide covers
Testing
Micro-frontends enable independent deployment — teams can release new versions of their micro-frontend without coordinating with other teams. But this independence creates CI/CD testing challenges: how do you test a remote in isolation, how do you verify the composition still works after a remote deploys, and how do
Testing
Micro-frontends communicate through defined interfaces: federated module exports, custom events, shared state, and props passed from shell to remote. When one team changes their interface without notifying consumers, the entire application breaks — and in production. Contract testing formalizes these interfaces so both sides can verify compatibility independently, without deploying
Testing
Single-SPA is a framework for orchestrating multiple micro-frontend applications on a single page. Each micro-frontend registers as an application with its own lifecycle hooks — bootstrap, mount, and unmount — and Single-SPA activates them based on URL patterns. Testing Single-SPA applications requires testing at three levels: individual
Testing
Module Federation in Webpack 5 enables true micro-frontend architecture — separate teams building, deploying, and updating independent JavaScript bundles that compose into a single application at runtime. The testing challenges this introduces are real: federated modules can fail to load, version contracts can break silently, and the shell app'