Update chokidar 2.1.8 → 3.6.0 (major)

[depfu]

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ chokidar (2.1.8 → 3.6.0) · Repo · Changelog

Release Notes

3.6.0

What's Changed

• fix readyCount logic by @JLHwung in #1288
• handle MustScanSubDirs by @MarcCelani-at in #1197
• update fs.FSWatcher types to satisfy nodejs versions >= 16; fixes #1299 by @ben-polinsky in #1300

New Contributors

• @Mutahhar made their first contribution in #1226
• @zqianem made their first contribution in #1242
• @JLHwung made their first contribution in #1288
• @MarcCelani-at made their first contribution in #1197
• @ben-polinsky made their first contribution in #1300

Full Changelog: 3.5.3...3.6.0

3.5.2

"Update" glob-parent dependency from ~5.1.0 to ~5.1.2 to silence "vulnerability" warnings

3.5.0

• Support for ARM Macs with Apple Silicon.
• Fixed missing removal of symlinks when the target path was deleted (#1042)

3.2.1

Improve Linux RAM usage by 50%. Stability optimizations. Race condition fixes. Windows glob fixes.

3.1.1

Fixes "Expected pattern to be a non-empty string" (#871)

3.1.0

Emit dotfiles by default. You can filter them out by using ignored option.

Improves Linux performance by 50%.

3.0.2

• Brings bigint support to stat outputs on windows.
• Fixes ready event emission for symlink directories.

3.0.1

• Fixes "Assertion failed" errors when a watcher is closed
• General optimizations

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 22 commits:

• Release 3.6.0.
• Add github ci autopublish
• Merge pull request #1300 from ben-polinsky/fix-fswatcher-types-1299
• fix formatting
• update fs.FSWatcher types to satisfy node versions >= 16; fixes #1299
• Merge pull request #1197 from MarcCelani-at/handleMustScanSubDirs
• Merge pull request #1288 from JLHwung/fix-ready-count
• ready call # is unfortunately platform specific
• fix readyCount logic
• Adjust funding field in pkg
• Enable GitHub Sponsors
• Merge pull request #1242 from zqianem/fix/tests
• Fix test case using unsupported option for Node 8
• Fix `close` tests
• Merge pull request #1226 from Mutahhar/patch-1
• Update README.md
• Merge pull request #1198 from XhmikosR/rm-unused-deps
• Merge pull request #1199 from XhmikosR/patch-1
• Update CI config
• Remove unused devDependencies
• move to constants
• handle MustScanSubDirs

✳️ duti (0.15.2 → 0.15.3) · Repo · Changelog

Release Notes

0.15.3 (from changelog)

• Update all mentions of futil-js to futil

Does any of this look wrong? Please let us know.

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)