fsevents

Following warning is being thrown on npm install command - npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.1.2 (node_modules\rea ct-scripts\node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@ 1.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"} ) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules\ch okidar\node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@ 1.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32",

I am watching a directory for file system events. Everything seems to work fine with one exception. When I create a file the first time, it spits out that it was created. Then I can remove it and it says it was removed. When I go to create the same file again, I get both a created and removed flag at the same time. I obviously am misunderstanding how the flags are being set when the callback is being called. What is happening here? // // main.c // GoFSEvents // // Created by Kyle Cook on 8/22/13. // Copyright (c) 2013 Kyle Cook. All rights reserved. // #include <CoreServices/CoreServices.h>

I tried running webpack --watch and after editing my JS files, it doesn't trigger an auto-recompilation. I've tried reinstalling webpack using npm uninstall but it's still not working. Any ideas? FYI: it seems OS X can have a folder get corrupted and no longer send fsevents (which watchpack / chokidar /Finder uses) for itself and any child folders. I can't be sure this is what happened to you, but it was very frustrating for me and a colleague. We were able to rename the corrupt parent folder and then watch events immediately came through as expected. See this blog post for more info: http:/