Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency chokidar to v4 #84

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 16, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
chokidar 3.5.3 -> 4.0.3 age adoption passing confidence

Release Notes

paulmillr/chokidar (chokidar)

v4.0.3

Compare Source

v4.0.2

Compare Source

What's Changed

New Contributors

Full Changelog: paulmillr/chokidar@4.0.1...4.0.2

v4.0.1

Compare Source

  • Various fixes and improvements of typescript types

New Contributors

Full Changelog: paulmillr/chokidar@4.0.0...4.0.1

v4.0.0

Compare Source

  • Remove glob support
  • Remove bundled fsevents
  • Decrease dependency count from 13 to 1
  • Rewrite in typescript. Makes emitted types more precise
  • The package became hybrid common.js / ESM
  • Bump minimum node.js requirement to v14+

Special thanks to @​43081j for improvements and help.

Full Changelog: paulmillr/chokidar@3.6.0...4.0.0

v3.6.0

Compare Source

What's Changed

New Contributors

Full Changelog: paulmillr/chokidar@3.5.3...3.6.0


Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), Automerge - At any time (no schedule defined).

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

Rebasing: Whenever PR is behind base branch, 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.

Copy link
Contributor Author

renovate bot commented Dec 16, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @swc/[email protected]
npm error Found: [email protected]
npm error node_modules/chokidar
npm error   dev chokidar@"4.0.3" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional chokidar@"^3.5.1" from @swc/[email protected]
npm error node_modules/@swc/cli
npm error   dev @swc/cli@"0.1.63" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/chokidar
npm error   peerOptional chokidar@"^3.5.1" from @swc/[email protected]
npm error   node_modules/@swc/cli
npm error     dev @swc/cli@"0.1.63" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-12-18T23_11_13_620Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-12-18T23_11_13_620Z-debug-0.log

@renovate renovate bot force-pushed the renovate/chokidar-4.x branch from 65dc951 to bd6d1c3 Compare December 16, 2024 23:25
@renovate renovate bot force-pushed the renovate/chokidar-4.x branch from bd6d1c3 to 3d7db3b Compare December 18, 2024 23:11
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