chore(deps): replace rollup with @rollup/plugin-babel 5.0.0

renovate[bot] commented 1 year ago

This PR contains the following updates:

Package	Type	Update	Change
rollup-plugin-babel	devDependencies	replacement	`4.4.0` -> `5.0.0`
rollup-plugin-node-resolve	devDependencies	replacement	`5.2.0` -> `6.0.0`
rollup-plugin-terser	devDependencies	replacement	`7.0.2` -> `0.1.0`

This is a special PR that replaces rollup-plugin-babel with the community suggested minimal stable replacement version.

This is a special PR that replaces rollup-plugin-node-resolve with the community suggested minimal stable replacement version.

This is a special PR that replaces rollup-plugin-terser with the community suggested minimal stable replacement version.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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 these updates 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[bot] commented 1 year ago

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.

Branch has one or more failed status checks

renovate[bot] commented 1 year ago

⚠ 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 unable to resolve dependency tree
npm error
npm error While resolving: vue-socket.io-extended@0.0.0-semantically-released
npm error Found: rollup@2.79.1
npm error node_modules/rollup
npm error   dev rollup@"2.79.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peer rollup@"^1.20.0" from @rollup/plugin-node-resolve@6.0.0
npm error node_modules/@rollup/plugin-node-resolve
npm error   dev @rollup/plugin-node-resolve@"6.0.0" 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-05-04T08_01_41_838Z-eresolve-report.txt

npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-04T08_01_41_838Z-debug-0.log

renovate[bot] commented 3 months ago

⚠️ 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 unable to resolve dependency tree
npm error
npm error While resolving: vue-socket.io-extended@0.0.0-semantically-released
npm error Found: rollup@2.79.1
npm error node_modules/rollup
npm error   dev rollup@"2.79.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peer rollup@"^1.20.0" from @rollup/plugin-node-resolve@6.0.0
npm error node_modules/@rollup/plugin-node-resolve
npm error   dev @rollup/plugin-node-resolve@"6.0.0" 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-08-28T08_41_15_511Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-08-28T08_41_15_511Z-debug-0.log

probil / vue-socket.io-extended