How can we prevent elm-live from monitoring `node_modules/`? about elm-live

[tomek-he-him]

Hey, thanks for opening 🙂 Can you please post more info about the version of elm-live and the OS you’re running?

Also, please read through #97 for more context about picking up changes from node_modules. (TLDR: This is not intended and we’re still trying to put together the short, self-contained, compilable example. Your help would be appreciated.)

I’m keeping this issue open though, because #97 seems to involve two cross-cutting concerns – and picking up node_modules is only one of them.

[Natim]

After investigation it seems that the problem is coming from chokidar.
paulmillr/chokidar#544

[Natim]

Refs #90

[Natim]

I have no idea how to write such a test. I am bit puzzle because you seem to be using **/*.{html,css,js} and **/*.elm so I don't see why this command are monitored to be honest.

I guess a way to reproduce the test is to run elm-live in a thread and touching some files in a fake node_module/.bin repository in the meantime and see that elm-live doesn't rebuild when we do.

[Natim]

Any help on fixing this, it is really a pain while using Elm-live on a daily basis

[tomek-he-him]

Fixed in v2.7.5. Really sorry for the long wait on this, it was a crazy couple of months for me! All getting slightly better now though 😄