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

chore(deps): update dependency component-emitter to v2 #648

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 18, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
component-emitter 1.3.1 -> 2.0.0 age adoption passing confidence

Release Notes

sindresorhus/component-emitter (component-emitter)

v2.0.0

Compare Source

Breaking
  • Require Node.js 18 and modern browsers a56d239
  • Removed support for component (now defunct project)
  • Listeners are now internally stored in a Map. This only affects you if you used the private property emitter._callbacks 7298216
Improvements

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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 Nov 18, 2023

⚠ 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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/component-emitter
npm ERR!   dev component-emitter@"2.0.0" from the root project
npm ERR!   peer component-emitter@"^1.3.0 || ^2.0.0" from [email protected]
npm ERR!   node_modules/vis-graph3d
npm ERR!     dev vis-graph3d@"6.0.6" from the root project
npm ERR!   1 more (vis-util)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer component-emitter@"^1.3.0" from [email protected]
npm ERR! node_modules/vis-network
npm ERR!   dev vis-network@"9.1.9" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/component-emitter
npm ERR!   peer component-emitter@"^1.3.0" from [email protected]
npm ERR!   node_modules/vis-network
npm ERR!     dev vis-network@"9.1.9" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-04-11T22_22_00_152Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-04-11T22_22_00_152Z-debug-0.log

@renovate renovate bot force-pushed the renovate/component-emitter-2.x branch 3 times, most recently from 723d49f to ef76b58 Compare November 25, 2023 00:49
@renovate renovate bot force-pushed the renovate/component-emitter-2.x branch 2 times, most recently from 4b2b737 to 894b57a Compare December 6, 2023 00:28
@renovate renovate bot force-pushed the renovate/component-emitter-2.x branch 3 times, most recently from 5a4e292 to 7a2a66e Compare January 3, 2024 01:32
@renovate renovate bot force-pushed the renovate/component-emitter-2.x branch from 7a2a66e to 6cfd38c Compare January 17, 2024 00:45
@renovate renovate bot force-pushed the renovate/component-emitter-2.x branch from 6cfd38c to 4423574 Compare January 24, 2024 21:39
@renovate renovate bot force-pushed the renovate/component-emitter-2.x branch from 4423574 to 5bfb68a Compare February 8, 2024 19:31
@renovate renovate bot force-pushed the renovate/component-emitter-2.x branch from 5bfb68a to 83a7d12 Compare March 1, 2024 21:26
@renovate renovate bot force-pushed the renovate/component-emitter-2.x branch 2 times, most recently from 8f45f76 to 2f16330 Compare March 26, 2024 21:53
@renovate renovate bot force-pushed the renovate/component-emitter-2.x branch from 2f16330 to 95c069b Compare April 4, 2024 03:42
@renovate renovate bot force-pushed the renovate/component-emitter-2.x branch from 95c069b to ef73d90 Compare April 11, 2024 22:22
@renovate renovate bot force-pushed the renovate/component-emitter-2.x branch from ef73d90 to feb5429 Compare June 24, 2024 22:45
Copy link
Contributor Author

renovate bot commented Jun 24, 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: [email protected]
npm error Found: [email protected]
npm error node_modules/component-emitter
npm error   dev component-emitter@"2.0.0" from the root project
npm error   peer component-emitter@"^1.3.0 || ^2.0.0" from [email protected]
npm error   node_modules/vis-graph3d
npm error     dev vis-graph3d@"6.0.6" from the root project
npm error   1 more (vis-util)
npm error
npm error Could not resolve dependency:
npm error peer component-emitter@"^1.3.0" from [email protected]
npm error node_modules/vis-network
npm error   dev vis-network@"9.1.9" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/component-emitter
npm error   peer component-emitter@"^1.3.0" from [email protected]
npm error   node_modules/vis-network
npm error     dev vis-network@"9.1.9" 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-10-30T00_02_36_231Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-10-30T00_02_36_231Z-debug-0.log

@renovate renovate bot force-pushed the renovate/component-emitter-2.x branch 2 times, most recently from 1b33ab3 to ce2fdf8 Compare June 26, 2024 21:40
@renovate renovate bot force-pushed the renovate/component-emitter-2.x branch from ce2fdf8 to 0d52628 Compare July 2, 2024 19:29
@renovate renovate bot force-pushed the renovate/component-emitter-2.x branch from 0d52628 to d4d4e68 Compare July 20, 2024 23:18
@renovate renovate bot force-pushed the renovate/component-emitter-2.x branch from d4d4e68 to 82534af Compare August 9, 2024 12:11
@renovate renovate bot force-pushed the renovate/component-emitter-2.x branch from 82534af to 5627750 Compare October 30, 2024 00:02
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