Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Watch not working following tutorial on Windows 10 WSL Nix #2778

Open
CodingFlow opened this issue Nov 29, 2024 · 1 comment
Open

Watch not working following tutorial on Windows 10 WSL Nix #2778

CodingFlow opened this issue Nov 29, 2024 · 1 comment
Labels
upstream The issue is with an upstream dependency.

Comments

@CodingFlow
Copy link

CodingFlow commented Nov 29, 2024

I'm following the tutorial and when I run deno task start, the server starts successfully after what feels like ~ 10 seconds (seems slow). As per the tutorial, I make a change to routes/index.tsx in VS Code in Windows, but I do not see the changes reflected in the browser even after refreshing the page. The terminal does not produce any updates to indicate that watch has detected the change: terminal continues to display:

/> deno task start
Task start deno run -A --watch=static/,routes/ dev.ts
Watcher Process started.
The manifest has been generated for 5 routes and 1 islands.

🍋 Fresh ready
Local: http://localhost:8000/

I'm using:

  • Deno: 2.0.6 in Nix via Devbox shell
  • Fresh: 1.7.3
  • Windows 10 / WSL2

Edit:

Watch works fine if deno task start is run from Windows. It also runs a lot faster.

@CodingFlow
Copy link
Author

This appears to be a known WSL 2 issue. Stack Overflow answer. For my use case, I was able to setup the code in the Linux filesystem instead of Windows mounted directories. It also solved the slowness I was experiencing.

There is a Deno issue open, but it hasn't seen any activity for over a year.

@marvinhagemeister marvinhagemeister added the upstream The issue is with an upstream dependency. label Dec 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
upstream The issue is with an upstream dependency.
Projects
None yet
Development

No branches or pull requests

2 participants