You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The dev-server does not update the build upon file change in Windows 11 WSL 2 (v 1.2.0.0).
The initial page is built ok, but upon file changes, it still serves the files, that were built upon running the npm start command. Even manual refresh of the page doesn't help.
I have read the documentation, set the --watch flag and the rootDir and basePath paths, but neither of those worked.
Tested on a clean SPA project scaffolded with npm init @open-wc.
The text was updated successfully, but these errors were encountered:
One of my coworkers had this same issue. It turned out that he had cloned his repo into a "mounted" location (/mnt/c which is how you access the Windows C: drive in WSL). We fixed by cloning his repo into a subdirectory under home (~/workspace for example) instead.
Not sure if your issue is caused by a similar location issue, but I figured it was worth mentioning!
The
dev-server
does not update the build upon file change in Windows 11 WSL 2 (v 1.2.0.0).The initial page is built ok, but upon file changes, it still serves the files, that were built upon running the
npm start
command. Even manual refresh of the page doesn't help.I have read the documentation, set the
--watch
flag and therootDir
andbasePath
paths, but neither of those worked.Tested on a clean SPA project scaffolded with
npm init @open-wc
.The text was updated successfully, but these errors were encountered: