files not included in the globs are still being watched about sane

[amasad]

looking

[jonathanong]

i think the easiest solution is to make sure any file matches one of the globs before being emitted. another solution would be to filiter the files in the recReaddir callbacks, though i think that's more complicated.

[amasad]

wait, where are you getting this list of files from?
I can't repro

[jonathanong]

i'm doing:

console.log(watcher.globs)
console.log(Object.keys(watcher.watched))

[jonathanong]

oaky. you know waht. i can't reproduce anymore either. wtfff.

closing haha.

can you release 0.3.1 please? i think component build -w is done

[jonathanong]

btw this shit is so fast

[amasad]

.watched is internal wouldn't tell you what is really being watched.

publish have been failing with me all day. npm ERR! publish fail Cannot publish over existing version. any idea?

[jonathanong]

meh. just publish another version. lol

[jonathanong]

noticed that on 0.10, events have a 300ms delay and on 0.11, events have a 100ms delay. do you know why that is?

[amasad]

no idea

[amasad]

publish is fucked, can't publish anything, npm is so broken

[jonathanong]

seriously. this is why i like component and using github as a registry :D

[amasad]

alright published

[amasad]

btw if you're interested, this.watched is big, because it watches everything in case at some point something appeared in one of the directories that matches our glob we should be able to emit an event. Maybe optimizations exist but the library needs to understand globs much deeply to do this optimizations.

[jonathanong]

yeah i don't completely understand the code yet. at least it's readable though, unlike other watcher libs i've seen _