Skip to main content
Keep iteration fast by knowing which changes apply instantly and which require a restart. Extension.js chooses the lightest safe update mode per file change.

Update modes

Common examples

What to do when you need to restart

One change still needs a restart by you: an edit to extension.config.*. The session keeps the config that it read at startup and prints a warning. Stop the session and run extension dev again. A dev session restarts its compiler by itself for a manifest entry change, for a change to the script or style entries of an HTML entrypoint, for an .env change, and for a file added under pages/ or scripts/. From the release after 4.1.41, it also does so for a file deleted or renamed there.

Practical guidance

  • Prefer editing existing modules/assets during active dev sessions for fastest feedback.
  • Batch structural manifest changes (entrypoint list edits) so the session restarts once.
  • Treat restart required diagnostics as authoritative; continuing without restart can leave your runtime in a stale state.

Next steps