Stuck on an issue?

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.

Doesn't detect change in nested files (on Linux)

See original GitHub issue

Hey, Luke 👋🏻

So I was trying snowpack out, and the docs brought me here. Their doc highly recommends servor. 😉 I’ve watched you in YT on pushing the web forward on a bundle-less future. I’m excited that it’s becoming more mainstream.

So I’m using this in Ubuntu via WSL / Windows 10; while it reloads fine when I change the index.html, it doesn’t reload if I change the JS file.

Here’s a screencast I made to document the error.

Issue Analytics

State:
Created 4 years ago
Reactions:3
Comments:23 (9 by maintainers)

Top GitHub Comments

1reaction

thisguychriscommented, Feb 1, 2020

@nakleiderer I actually agree with you on size being less important, since this is a dev dependency.

If the file size is the problem, then I would argue that this is a dev dependency and file size is not that going to a big deal especially it’s only 2.6kb

But the author seems he wanted this to be fixed at the main library level without dependency. Let’s wait. The main thing here is we can’t rely on Node’s Native fs.watch. It’s a buggy implementation. 🙊 That’s the whole reason, chokidar, node-watch, cheap-watch, and other permutations exist.

1reaction

nakleiderercommented, Feb 1, 2020

@thisguychris Fair points all around. I’ve mainly used chokidar in environments where dependency size is largely irrelevant, so I wasn’t familiar with the size. Thanks for the insight!

Is it a goal of this project to be light-weight on dependencies? I see that mentioned as a feature in the docs, but I’m curious if that is intended to be a defining trait of this project or a reflection of its current state. Is it a goal of this project to be used in deployed environments or as a development tool? If it’s a development tool, then dependency weight is less important in this project than it is for Sapper, which is run in deployed environments. I agree that chokidar’s size is disproportionate to the current size of this project, though it appears to be a more mature project than some of the alternatives with a large following. Popularity isn’t everything though.

Obviously, I’m happy with any solution to the problem. I think a clarification on the principles/goals of this project can help the community contribute more effectively. Again, thanks for the reply 😃