web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Engage with the Community
Unanswered

SPFx 1.22.x (Heft Toolchain) Live Reload Not Working Inside Docker Container

(0) ShareShare
ReportReport
Posted on by 12
I am facing an issue with SPFx 1.22.x (Heft-based toolchain) running inside a Docker container.
The web part is created successfully inside the container workspace using:

yo @microsoft/sharepoint

I selected a React-based web part, and the project builds successfully without any errors.

However, the live reload / file watching is not working.

What happens:

  • When I modify any web part file, the terminal does not detect file changes

  • The SharePoint Workbench does not reload or reflect updates

  • Live reload never triggers

What works correctly:

  • The web part builds successfully

  • The debug manifest loads correctly

  • I can access the manifest here:

https://localhost:4321/temp/build/manifests.js

The web part also loads in the SharePoint Workbench using:

https://<tenant>.sharepoint.com/_layouts/15/workbench.aspx?debugManifestsFile=https://localhost:4321/temp/build/manifests.js&debug=true&noredir=true

But file changes are not detected, so live reload never happens.

Configuration change I tried

I updated config/serve.json:

{
  "hostname": "0.0.0.0",
  "port": 4321,
  "https": true
}

But this did not resolve the issue.

Important comparison

If I use SPFx 1.21 (Gulp-based toolchain) with spfx-fast-serve, everything works perfectly:

  • File changes are detected

  • Live reload works

  • Updates appear immediately in the Workbench

But with SPFx 1.22.x (Heft-based toolchain) inside Docker:

  • File watch does not work

  • Live reload does not work

Environment

  • SPFx Version: 1.22.x

  • Toolchain: Heft

  • Running inside: Docker container

  • Docker Desktop installed

  • Web part created using Yeoman generator

  • React-based web part

Question

Has anyone successfully configured SPFx 1.22.x (Heft) live reload inside a Docker container?

Is there any known issue with:

  • file watching inside Docker

  • Heft build-watch --serve

  • container volume mounting

  • or LiveReload with SPFx 1.22?

Any guidance or working configuration would be greatly appreciated. I have been trying to resolve this for the past week but have not been able to get live reload working inside Docker.

please make sure you comment first try in docker with setup spfx 1.22 then you realized what i stuck! (no direct ask to chatgpt first try then if you resolved this then comment here)

 

I have the same question (0)
  • IS-11032257-0 Profile Picture
    4 Microsoft Employee on at
    I have a similar but slightly different experience.
    It all worked yesterday, but overnight my computer rebooted (having installed some windows update?) and now the project I worked on yesterday does not load.
     
    The manifests.js load only if I use workbench. if I use the ?debugManifestsFile querystring it does not even appear to try to load it (no request sent to webpack). dev console does not show rejected attempts to hit localhost.
    In workbench it loads only the manifest - does not load the source code and changes are not seen.
    Also curious that sharepoint stopped the popup asking me if I want to load debug scripts when it opens the debug window.
     
    I tried different browsers, rebooting my environment and different tenants and different computers - all have the same issue.
     
    My guess is that microsoft did a server patch and stuffed up sharepoint last night
     
     
  • LUIZCOSTA.DEV Profile Picture
    3 on at
    Estou com o mesmo problema, mas na versão 1.21.1, e começou a acontecer hoje às 18h (horário do Brasil).
    Só consigo ver as alterações nos web parts que estão sendo executados no Workbench (e atualizando a página manualmente).

    A recarga automática parou de funcionar e o parâmetro debugManifestsFile na URL não avisa mais sobre a necessidade de autorizar scripts ou que o manifesto não foi encontrado.
    Não há requisições sendo feitas para localhost; simplesmente parou de funcionar.

    Testei em mais de 5 tenants diferentes, em 2 computadores diferentes.
    O certificado está OK, o manifesto no localhost também está OK.
    Estou procurando soluções há mais de 3 horas e não encontrei nada.

    Presumo que a Microsoft tenha feito algum tipo de atualização.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Leaderboard > Engage with the Community

#1
ManoVerse Profile Picture

ManoVerse 10

#1
wolenberg_ Profile Picture

wolenberg_ 10 Super User 2026 Season 1

#3
J-D-M Profile Picture

J-D-M 5

Last 30 days Overall leaderboard