You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using @parcel/watcher for skott and the library is nice, thank you!
As it was reported by a skott's user it seems that using negated entries in the ignore option is causing a weird behavior where the watcher does not detect any change. Another issue (#166) was opened by @arciisine close to that topic but the issue is just mentioning a lack of support (that is being able to not ignore some of the entries) and in my case it is causing the watcher to not detect changes at all.
I would either expect:
negated entries to be ignored by the watcher (as it's currently not supposed to be supported)
I created a repo to reproduce the issue with .vscode entries initially coming from .gitignore, provided down to the ignore of @parcel/watcher#subscribe method. You can find all information in the README.md to reproduce the problem.
The text was updated successfully, but these errors were encountered:
antoine-coulon
changed the title
Negated entries from the "ignore" option are making the watcher not detecting any changes
Negated entries provided to "ignore" option are making the watcher not detecting any changes
May 27, 2024
Hello,
I'm using @parcel/watcher for skott and the library is nice, thank you!
As it was reported by a skott's user it seems that using negated entries in the
ignore
option is causing a weird behavior where the watcher does not detect any change. Another issue (#166) was opened by @arciisine close to that topic but the issue is just mentioning a lack of support (that is being able to not ignore some of the entries) and in my case it is causing the watcher to not detect changes at all.I would either expect:
I created a repo to reproduce the issue with
.vscode
entries initially coming from.gitignore
, provided down to theignore
of@parcel/watcher#subscribe
method. You can find all information in the README.md to reproduce the problem.The text was updated successfully, but these errors were encountered: