deprecated

Fixing the API for chokidar since it was calling FSEvents as a constructor

deprecated

We have upgraded to N-API. For that reason we have also dropped support for node < 6.

For that reason, we have made this a major version bump so dependents have to opt in. The actual API remains entirely the same, so if you are depending on fsevents, it should be as simple as changing the version number in your package.json.

v1.2.3

• Added node v10 for pre-built binaries
• C++ tuning to fix potential SIGILL and cyclic dependency (#204)

v1.2.2

Fixed node-pre-gyp bundling issue

v1.2.1

[unpublished because of errors during publish process]

v1.2.0

• BREAKING: End support for Node v0.12. If you are using Node v0.12 please pin your fsevents dependencies to v1.1.3. Not bumping semver major for this release was a compromise solution discussed in #199 and #201.
  • Node v0.10 should continue to work with local compilation for now, but hosted pre-built binaries will no longer be provided. If this is a constraint for you, please pin to an earlier version.
• Fixed security vulnerability warnings by updating node-pre-gyp to ^0.9.0
• Compatibility updates for nan v2.9.0

v1.1.3

• Added node v9 for pre-built binaries
• Fixed bug related to using --no-bin-links option on install
• Updated node-pre-gyp to latest version (0.6.39)

v1.1.2

• Added Node.js v8 to the prebuild binary assets.
• Stopped prebuilding for io.js (can still be built locally)
• Updated node-pre-gyp to latest version (0.6.36)

v1.1.1

Back to specifying compatibility with darwin platform only because some use cases rely upon it.

v1.1.0

No longer specifies itself as compatible with darwin platform only to resolve longstanding issues with npm and optional/platform-specific dependencies. Will now install seamlessly on all platforms, but will throw an error if loaded on an incompatible system.

As was already the case, require('fsevents') should be wrapped in a try statement when needing to ensure cross-compatibility.