So here is a block diagram for a very simple e-Commerce [https://github.com/jherr/wp5-full-site-federation] site that is made up of three applications: We have the applications at the top, Home, Search and Checkout, and they connect to some React components shared using NPM (AddToCart and Frame). And they
Micro-Frontends and Module Federation creates an interesting challenge for state management. Because you may not know the data requirements of the frontend. A naive implementation using useState or useContext could result in a system where the entire page is re-rendered on even the most minor state change, with most components
To prove if using Federated Modules for a dashboard would be a good thing I think you'd have to prove three technical capabilities: * Load dashboard widget code dynamically at runtime (no requirement to rebuild to add new widgets) * The host page shouldn't need to be based
NextJS 9.3 brings Static Site Generation to the NextJS platform. Which is really exciting because NextJS now supports three different rendering modes. * Client Side Rendering (CSR) * Server Side Rendering (SSR) * Static Site Generation (SSG) This article explains these three modes and when to use them. If you like video
I'm seeing a lot of comments about hiring on my Twitter feed that read like this: The answer is no, and in the context of an interview, it's a bad question. So how can you and I fix this? How do we, as developers, get companies
Move backwards in time in your code, make changes and watch your tests pass.