chore(deps): bump rollup and vite #2050
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [rollup](https://github.com/rollup/rollup) to 2.79.2 and updates ancestor dependency [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite). These dependencies need to be updated together. Updates `rollup` from 2.79.1 to 2.79.2 - [Release notes](https://github.com/rollup/rollup/releases) - [Changelog](https://github.com/rollup/rollup/blob/master/CHANGELOG.md) - [Commits](rollup/rollup@v2.79.1...v2.79.2) Updates `vite` from 2.9.18 to 5.4.8 - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/v5.4.8/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/v5.4.8/packages/vite) --- updated-dependencies: - dependency-name: rollup dependency-type: indirect - dependency-name: vite dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]>
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Getting the following error in Vercel:
[17:12:32.315] Cloning github.com/tijlleenders/ZinZen (Branch: dependabot/npm_and_yarn/multi-96e66b30f7, Commit: 3bae6e0)
[17:12:36.163] Running "vercel build"
[17:12:36.563] Vercel CLI 37.6.0
[17:12:37.301] Installing dependencies...
[17:12:39.640] npm notice
[17:12:39.640] npm notice New minor version of npm available! 10.7.0 -> 10.8.3
[17:12:39.641] npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.8.3
[17:12:39.641] npm notice To update run: npm install -g [email protected]
[17:12:39.641] npm notice
[17:12:39.642] npm error code ERESOLVE
[17:12:39.644] npm error ERESOLVE could not resolve
[17:12:39.644] npm error
[17:12:39.645] npm error While resolving: [email protected]
[17:12:39.645] npm error Found: @types/[email protected]
[17:12:39.645] npm error node_modules/@types/node
[17:12:39.645] npm error @types/node@"^17.0.31" from the root project
[17:12:39.646] npm error peer @types/node@"*" from [email protected]
[17:12:39.646] npm error node_modules/ts-node
[17:12:39.646] npm error ts-node@"^10.9.2" from the root project
[17:12:39.646] npm error peerOptional ts-node@">=9.0.0" from [email protected]
[17:12:39.646] npm error node_modules/jest-config
[17:12:39.647] npm error jest-config@"^27.5.1" from @jest/[email protected]
[17:12:39.647] npm error node_modules/@jest/core
[17:12:39.647] npm error @jest/core@"^27.5.1" from [email protected]
[17:12:39.647] npm error node_modules/jest
[17:12:39.647] npm error 1 more (jest-cli)
[17:12:39.647] npm error 1 more (jest-cli)
[17:12:39.647] npm error
[17:12:39.647] npm error Could not resolve dependency:
[17:12:39.653] npm error peerOptional @types/node@"^18.0.0 || >=20.0.0" from [email protected]
[17:12:39.653] npm error node_modules/vite
[17:12:39.653] npm error vite@"^5.4.8" from the root project
[17:12:39.653] npm error
[17:12:39.653] npm error Conflicting peer dependency: @types/[email protected]
[17:12:39.653] npm error node_modules/@types/node
[17:12:39.653] npm error peerOptional @types/node@"^18.0.0 || >=20.0.0" from [email protected]
[17:12:39.653] npm error node_modules/vite
[17:12:39.653] npm error vite@"^5.4.8" from the root project
[17:12:39.653] npm error
[17:12:39.653] npm error Fix the upstream dependency conflict, or retry
[17:12:39.653] npm error this command with --force or --legacy-peer-deps
[17:12:39.653] npm error to accept an incorrect (and potentially broken) dependency resolution.
[17:12:39.653] npm error
[17:12:39.653] npm error
[17:12:39.654] npm error A complete log of this run can be found in: /vercel/.npm/_logs/2024-10-01T15_12_37_554Z-debug-0.log
[17:12:39.661] Error: Command "npm install" exited with 1
[17:12:39.982]
…rn/multi-96e66b30f7
|
Thanks! |
Bumps rollup to 2.79.2 and updates ancestor dependency vite. These dependencies need to be updated together.
Updates
rollupfrom 2.79.1 to 2.79.2Changelog
Sourced from rollup's changelog.
... (truncated)
Commits
c9bd03d2.79.248aef33fix: resolve DOM Clobbering CVE-2024-43788 (backport to v2) (#5677)Updates
vitefrom 2.9.18 to 5.4.8Release notes
Sourced from vite's releases.
Changelog
Sourced from vite's changelog.
... (truncated)
Commits
0474550release: v5.4.88464d97fix(css): backport #18128, ensure sass compiler initialized only once (#18184)7d47fc1fix(css): backport #18113, fix missing source file warning with sass modern a...a403e73release: v5.4.7b5908a2fix: treat config file as ESM in Deno (#18158)f969176release: v5.4.6179b177fix: avoid DOM Clobbering gadget ingetRelativeUrlFromDocument(#18115)6820bb3fix: fs raw query (#18112)37881e7release: v5.4.5faa2405fix(preload): backport #18098, throw error preloading module as well (#18099)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.