Suggest an editImprove this articleRefine the answer for “What does "lazy compilation" mean?”. Your changes go to moderation before they’re published.Approval requiredContentWhat you’re changing🇺🇸EN🇺🇦UAPreviewTitle (EN)Short answer (EN)**Lazy compilation** is an approach where modules are not compiled in advance, but are processed only at the moment they are actually requested by the browser or the application. **Key point:** lazy compilation is a lazy compilation mechanism where modules are processed not in advance but only when they are actually used, which speeds up startup and updates during development.Shown above the full answer for quick recall.Answer (EN)Image**Lazy compilation** is an approach where modules are **not compiled in advance**, but are processed **only at the moment they are actually requested by the browser or the application**. In other words, instead of building the entire project all at once, compilation is performed "lazily", on demand. --- ### The essence of the mechanism - when the dev server starts, compilation is not performed for all files - a module is compiled only when a real import or request reaches it - unused modules remain "untouched", saving time --- ### What this gives you | Result | Why | |---|---| | **fast dev server startup** | nothing extra is compiled in advance | | **instant project opening in the browser** | only the startup modules are processed | | **faster HMR** | only the changed fragment is compiled | --- ### An important distinction Lazy compilation is part of the broader "no-bundle"/"on-demand" development trend, where the tool serves code *as needed*, rather than "just in case". --- **Summary:** *Lazy compilation is a lazy compilation mechanism where modules are processed not in advance, but only at the moment they are actually used. This speeds up startup and updates during development.*For the reviewerNote to the moderator (optional)Visible only to the moderator. Helps review go faster.