Suggest an editImprove this articleRefine the answer for “What is "no-bundle development"?”. Your changes go to moderation before they’re published.Approval requiredContentWhat you’re changing🇺🇸EN🇺🇦UAPreviewTitle (EN)Short answer (EN)**"No-bundle development"** is an approach where the application in dev mode is **not bundled before startup**, and the browser receives the source modules directly, loading dependencies itself via ES modules (`import`). **Key point:** no-bundle development is a mode where the build is not performed in advance and code is served module by module, "as is", which makes development significantly faster.Shown above the full answer for quick recall.Answer (EN)Image**"No-bundle development"** is an approach where the application in dev mode is **not bundled before startup**. Instead of one large file, as in Webpack, the browser receives the source modules directly and loads dependencies itself via ES modules (`import`). --- ### **The main ideas of "no-bundle":** 1. **No preliminary build of the whole project.** The server starts instantly, because there is no need to build a bundle before startup. 2. **The browser itself plays the role of the "dependency graph".** It loads files via `import`, while Vite only intercepts requests and prepares individual modules as needed. 3. **HMR updates only the changed module.** There is no rebuilding of chains, as in Webpack. --- ### **What it is used for** | Task | How it helps | |---|---| | Speeding up project startup | no initial bundling | | Speeding up code updates | only the needed module changes | | Making development more responsive | fewer delays with HMR | --- ### **Key takeaway** **No-bundle development is a mode in which the build is not performed in advance. Code is served module by module, "as is", using the browser's native ES modules.** As a result, development becomes significantly faster, especially on large projects.For the reviewerNote to the moderator (optional)Visible only to the moderator. Helps review go faster.