Development server and HMR in Svelte - Performance & Optimization

Performance: Development server and HMR

MEDIUM IMPACT

This affects the speed of code updates during development and how quickly changes appear in the browser without full reloads.

Updating UI components during development

Svelte

Use a development server with Hot Module Replacement (HMR) enabled to update only changed components.

HMR updates only the changed parts without full reload, preserving state and speeding updates.

📈 Performance GainReduces reload time to under 100 ms, improving developer productivity.

Updating UI components during development

Svelte

Run a development server without HMR, requiring full page reload on every code change.

Full reloads cause the entire page to reload, losing state and slowing feedback.

📉 Performance CostBlocks rendering for 500+ ms per change, causing slow developer feedback loops.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Full page reload on change	All DOM nodes recreated	Multiple reflows	High paint cost	[X] Bad
HMR updates changed modules only	Minimal DOM updates	Single reflow	Low paint cost	[OK] Good

Rendering Pipeline

When a file changes, the development server recompiles only the affected modules. HMR injects updated code into the running app, triggering minimal re-rendering.

→Compile

→JavaScript Execution

→Paint

⚠️ BottleneckFull page reload triggers complete recompile and re-render, which is slow.

Optimization Tips

1Use HMR to update only changed modules during development.

2Avoid full page reloads to keep app state and speed feedback.

3Check DevTools Performance panel to confirm efficient updates.

Performance Quiz - 3 Questions

What is the main performance benefit of using HMR during development?

A It improves SEO by pre-rendering pages

B Only changed modules reload, speeding up updates

C It reduces the final bundle size for production

D It caches all assets to avoid network requests

DevTools: Performance

How to check: Record a session while saving a file. Observe if the page reloads fully or only patches update.

What to look for: Look for long 'Reload' events indicating full reload vs short 'Script Evaluation' for HMR.

Practice

1. What is the main purpose of the development server in a Svelte project?

easy

A. To compile the app into a production build

B. To minify the app's JavaScript files

C. To deploy the app to a web server

D. To show your app live and update it as you code

Solution

1. Step 1: Understand the role of the development server

   The development server runs your app locally and shows live updates as you make changes.

2. Step 2: Differentiate from production tasks

   Compiling for production, deploying, and minifying are separate steps done after development.

3. Final Answer:

   To show your app live and update it as you code -> Option D

4. Quick Check:

   Development server = live updates [OK]

Hint: Development server = live preview while coding [OK]

Common Mistakes:

• Confusing development server with production build
• Thinking it deploys the app
• Assuming it minifies code automatically

2. Which command starts the Svelte development server with Hot Module Replacement (HMR)?

easy

A. npm run build

B. npm run dev

C. npm start

D. npm run serve

Solution

1. Step 1: Identify the standard Svelte dev command

   In Svelte projects, npm run dev starts the development server with HMR enabled.

2. Step 2: Understand other commands

   npm run build creates production files; npm start and npm run serve are not standard for Svelte dev server.

3. Final Answer:

   npm run dev -> Option B

4. Quick Check:

   Start dev server = npm run dev [OK]

Hint: Use npm run dev to start Svelte dev server with HMR [OK]

Common Mistakes:

• Using npm run build instead of dev
• Confusing npm start with npm run dev
• Trying npm run serve which is not default

3. Given this Svelte component running with HMR, what happens when you change the text inside the <p> tag and save the file?

medium

A. Nothing happens until you manually refresh the browser

B. The entire page reloads and the app state resets

C. Only the changed text updates instantly without full reload

D. The app crashes due to hot reload errors

Solution

1. Step 1: Understand Hot Module Replacement (HMR) behavior

   HMR updates only the changed parts of the app instantly without reloading the whole page.

2. Step 2: Apply to text change in <p> tag

   Changing text inside the paragraph triggers HMR to update that text immediately, preserving app state.

3. Final Answer:

   Only the changed text updates instantly without full reload -> Option C

4. Quick Check:

   HMR updates changed parts instantly [OK]

Hint: HMR updates only changed parts, no full reload [OK]

Common Mistakes:

• Thinking full page reload happens on every change
• Believing manual refresh is needed
• Assuming app crashes on text change

4. You run npm run dev but the browser does not update when you change your Svelte files. What is the most likely cause?

medium

A. The development server is not running or crashed

B. You forgot to save the file after editing

C. You used npm run build instead of npm run dev

D. Your browser cache is disabled

Solution

1. Step 1: Check if development server is active

   If the dev server is not running or crashed, no updates or HMR can happen.

2. Step 2: Evaluate other options

   Not saving files prevents changes but usually obvious; using build command doesn't start dev server; browser cache disabled does not stop updates.

3. Final Answer:

   The development server is not running or crashed -> Option A

4. Quick Check:

   Dev server running = updates work [OK]

Hint: Check if dev server is running when no updates appear [OK]

Common Mistakes:

• Assuming browser cache blocks updates
• Not saving files before expecting changes
• Confusing build command with dev server

5. You want to keep your app state while updating styles during development. Which feature of the Svelte development server helps you achieve this?

hard

A. Hot Module Replacement (HMR)

B. Full page reload on every change

C. Production build optimization

D. Manual browser refresh

Solution

1. Step 1: Understand state preservation during updates

   HMR updates only changed modules without reloading the whole page, preserving app state like variables and UI state.

2. Step 2: Contrast with other options

   Full reload resets state; production build is unrelated to live updates; manual refresh loses state.

3. Final Answer:

   Hot Module Replacement (HMR) -> Option A

4. Quick Check:

   Keep state during updates = HMR [OK]

Hint: HMR preserves app state during live updates [OK]

Common Mistakes:

• Thinking full reload keeps state
• Confusing production build with dev features
• Relying on manual refresh to keep state