Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 8, 2026

This PR contains the following updates:

Package Change Age Confidence
fsevents@1 ^2.0.0^2.3.3 age confidence

Release Notes

fsevents/fsevents (fsevents@1)

v2.3.3

Compare Source

Released to npm as v2.3.3

v2.3.2

Compare Source

Released to npm as v2.3.2

v2.3.1

Compare Source

Released to npm as v2.3.1

Release contains universal binary for x86 & amd64 (m1) chips

v2.3.0

Compare Source

v2.2.2

Compare Source

Released to npm as v2.2.2

Universal Binary Support x86-64 & amd64(m1)

v2.2.1

Compare Source

v2.2.0

Compare Source

Electron Enabled (no static functions/variables)

v2.1.3: Release v1.2.3

Compare Source

v2.1.2

Compare Source

v2.1.1

Compare Source

v2.1.0

Compare Source

Latest stable release

v2.0.7

Compare Source

v2.0.6: Release NAPI v2.0.6

Compare Source

Include essential files only.

v2.0.5: Release NAPI v2.0.5

Compare Source

v2.0.4: Release NAPI v2.0.4

Compare Source

v2.0.3: Release NAPI v2.0.3

Compare Source

Moved NAPI version out of experimental.

v2.0.1: deprecated

Compare Source

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


Configuration

📅 Schedule: Branch creation - Between 09:00 PM and 09:59 PM, only on Thursday ( * 21 * * 4 ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/fsevents1-2.x branch from e30a0ce to 07a1fd1 Compare January 19, 2026 19:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants