Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Nitro Watcher Needs Polling Config
See original GitHub issueEnvironment
Docker, Windows, WSL
Reproduction
Run the most minimal Nuxt3 boilerplate setup via the docs in a simple docker container.
Describe the bug
For all typical/known Docker+WSL file watcher issues:
Vite polling works with usePolling: true.
Webpack works with chokidar or polling config options set.
Nitro has no (documented) support for the equivalent.
Polling option needs to be added, or if it’s already supported, the docs need to be much clearer on how to enable polling.
(And development should have better testing for Docker+WSL.)
Additional context
No response
Logs
No response
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@pi0 Ugh… I SINCERELY appreciate the “rubber-ducking” for exactly that reason of missing that in the doc; I don’t know HOW i just glanced over that!!
It fixes nitro AND its not needed in vite config anymore either – way more elegant soution (as it IS env specific problem…)
Thank you SO much for taking another look!
PR Welcome @peteromano you need to update here.
BTW I always developed within WSL2 environment with no issues. Maybe we need to enable polling for specific environments known to watching issues?