Request: Add “Delete Service Worker” button in Firebase Studio preview (HMR workaround)

Previews
,
1

Hello

I’m running into an issue where stale service workers interfere with Hot Module Replacement (HMR) in the preview pane. In Chrome DevTools, it’s easy to go to Application » Service Workers and click “Unregister” to clear the old worker. That lets HMR work again.

However, Firebase Studio’s built-in preview lacks this capability — there’s no option to unregister or disable the service worker. The result?

  • Changes don’t update live in the preview.
  • I need to open an external browser tab, manually unregister the SW, then refresh Firebase Studio preview.
  • This breaks my workflow and disrupts the dev feedback loop.

Request:
Please add a “Clear / Unregister Service Worker” option (similar to Chrome DevTools) in the preview toolbar or via right-click/context menu.

This would:

  • Restore HMR functionality without leaving the IDE.
  • Avoid stale cache issues and preview inconsistencies.
  • Improve the overall dev experience in Firebase Studio.

Anyone else running into this? Or is there a workaround I’ve missed? Appreciate any advice or ETA on this feature. :folded_hands:

Thanks!

1 Like
2

May I ask for an example of such a change that’s not getting updated in the preview?

3

Yes — for example, after making a significant change to a .tsx file (like modifying the component structure or imports), the preview inside Firebase Studio throws an HMR error and stops reflecting updates.

If I open the preview in a separate browser tab (using the “pop out” feature), I can use Chrome DevTools → Application → Service Worker → Unregister to clear the service worker. After that, the app reloads correctly and HMR works again in that tab.

But this doesn’t fix the error in the inline preview inside Firebase Studio, which remains stuck. That’s why I’m asking for a way to unregister or reset the service worker directly within the Studio preview, to recover from HMR issues without leaving the development environment.

4

Sometimes I click “Restart App” instead of “Reload App” to force a restart. But your suggestion makes senes. Your request has been shared with the team.

5

I’m having this issue right now.

It was a silent problem, that took me hours to realize it was occurring.

I added a version footer to my app and noticed it was not updating.

This is after a full pnpm purge, node modules and next purge as well.

After restarting the dev server, it is still not updating.

However, if I do what Pollarit mentioned and use the pop out feature, it’s up to date.

Issues like this need to be tracked and fixed and made into known issues.

Restarting a VM is a valid workaround, but only if the user notices the silent problem.

But, I tested that and even still my app preview is out of date, code view and prototyper.

I’m at a loss right now, I cannot use the in app web previews for development anymore.

I would greatly appreciate a workaround to remove this blocker.