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 doesn't detect cascading changes when nospawn is true #510
Comments
any news here? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have noticed a wrong behaviour of watch when
nospawn
istrue
. At least, watch doesn't behave the same as whennospawn
isfalse
.The use case I am considering is a frequent use case where a change to a
source
file triggers a change to adestination
file. This is typically the case when files are compiled (e.g..sass
files into.css
), or copied to a production folder.For the sake of simplification, I have built the following example:
watch is configured to trigger the copy when the
source
file is modified. It also watches thedestination
file. Note thenospawn: true
option:With this configuration, a change of the
source
file should trigger the copy task, which modifies thedestination
file. This change is unfortunately not detected by watch, as shown by the traces:On the other hand, when specifying
nospawn: false
, the modification of thedestination
file is correctly detected:Although using
nospawn: false
is a good workaround, it has much lower performances, hence it would be great if the issue could be fixed.The text was updated successfully, but these errors were encountered: