Packages

fsevents

2.3.3 · 21 Aug 2023MIT38.9M / weekRepositorynpmAtom feed

Your version

68 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.

  1. 2.x · latest line
  2. 2.3.3

    21 Aug 2023

    Released to npm as v2.3.3

  3. 2.3.2

    5 Feb 2021

    Released to npm as v2.3.2

  4. 2.3.1

    5 Jan 2021

    Released to npm as v2.3.1

  5. 2.3.0

    5 Jan 2021
  6. 2.2.2

    5 Jan 2021

    Released to npm as v2.2.2

  7. 2.2.1

    5 Nov 2020
  8. 2.2.0

    3 Nov 2020

    Electron Enabled (no static functions/variables)

  9. 2.1.1 – 2.1.33 releases without a noteShow each
  10. 2.1.0

    1 Oct 2019

    Latest stable release

  11. 2.0.7

    16 May 2019
  12. 2.0.6

    16 Apr 2019

    Include essential files only.

  13. 2.0.4 – 2.0.52 releases without a noteShow each
  14. 2.0.3

    1 Apr 2019

    Moved NAPI version out of experimental.

  15. 2.0.1

    10 Nov 2018

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

  16. 2.0.0

    10 Nov 2018

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

  17. 1.x
  18. 1.2.13

    5 May 2020

    Only build on Mac-OSX

  19. 1.2.12

    19 Mar 2020
  20. 1.2.11

    14 Dec 2019

    Removing node-pre-gyp so that building fsevents becomes easier and enabled without the download of binaries.

  21. 1.2.4 – 1.2.106 releases without a noteShow each
  22. 1.2.3

    27 Apr 2018
    • Added node v10 for pre-built binaries

    • C++ tuning to fix potential SIGILL and cyclic dependency

  23. 1.2.2

    23 Apr 2018

    Fixed node-pre-gyp bundling issue

  24. 1.2.1

    23 Apr 2018

    [unpublished because of errors during publish process]

  25. 1.2.0

    20 Apr 2018
    • 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.

    • Security

      Fixed security vulnerability warnings by updating node-pre-gyp to ^0.9.0

    • Compatibility updates for nan v2.9.0

  26. 1.1.3

    10 Nov 2017
    • 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)

  27. 1.1.2

    13 Jun 2017
    • 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)

  28. 1.1.1

    20 Feb 2017

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

  29. 1.1.0

    19 Feb 2017

    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.

  30. 1.0.17

    4 Jan 2017

    Updated bundled dependencies

  31. 1.0.16

    4 Jan 2017

    < unpublished >

  32. 1.0.15

    2 Nov 2016

    Updated bundled dependencies

  33. 1.0.14

    18 Jul 2016
  34. 1.0.13

    13 Jul 2016

    < unpublished >

  35. 1.0.12

    29 Apr 2016
    • Fixed compatibility issue with Node v6

    • Bumped nan to ^2.3.0

  36. 1.0.11

    31 Mar 2016
  37. 1.0.10

    31 Mar 2016

    Republish with ansi-styles@2.2.1 (since 2.2.0 was unpublished from npm)

  38. 1.0.9

    23 Mar 2016
  39. 1.0.8

    23 Feb 2016

    Updated node-pre-gyp to 0.6.21

  40. 1.0.7

    3 Feb 2016

    Updated node-pre-gyp to 0.6.19

  41. 1.0.6

    10 Dec 2015

    Updated node-pre-gyp to 0.6.17

  42. 1.0.5

    5 Nov 2015

    Re-added the bundled dependency flattening after having resolved the npm shrinkwrap issues in the deps

  43. 1.0.4

    4 Nov 2015
    • Reverted the bundled dependency flattening because of downstream dep version conflicts, leading to problems with npm shrinkwrap

  44. 1.0.3

    3 Nov 2015
    • Node v5 compatibility

    • Bundled dependencies are flattened

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.