build(deps-dev): Bump vite from 7.1.9 to 7.1.11 #125
Conversation
Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 7.1.9 to 7.1.11. - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/v7.1.11/packages/vite) --- updated-dependencies: - dependency-name: vite dependency-version: 7.1.11 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
dependencies
Deploying blinklabs-vpn with
|
| Latest commit: |
4c8806b
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://5e4c2d11.blinklabs-vpn.pages.dev |
| Branch Preview URL: | https://dependabot-npm-and-yarn-vite-7xvk.blinklabs-vpn.pages.dev |
|
|
✓ Safe to upgradeI recommend merging this upgrade because it patches critical security vulnerabilities (CVE-2025-30208, CVE-2025-31125, CVE-2025-31486) affecting arbitrary file read operations, includes bug fixes for HMR and optimizer functionality, and is fully compatible with the project's current configuration. The project already has Node.js 24 type definitions installed and uses @tailwindcss/vite 4.1.14 which explicitly supports Vite 7, eliminating the major compatibility concerns mentioned in preliminary reports. What we checked
Dependency UsageVite serves as the foundational build tool and development server for this VPN frontend application, configured with React support, image optimization, and API proxying to enable the entire development workflow. The application uses Vite exclusively through its configuration file and npm scripts to power local development, production builds, preview servers, and the complete test suite via vitest. This centralized build tool architecture enables the team to develop a Cardano wallet-connected VPN interface with optimized assets, hot module reloading, and comprehensive testing capabilities. ChangesVite updated with two breaking changes affecting HMR behavior when imports are removed from non-HMR modules and optimizer error handling for incompatible dependencies. The update includes ten bug fixes addressing esbuild helper injection, glob pattern HMR, SSR asset emission, and improved handling of npm-prefixed module IDs, along with three new features including Node.js version warnings and multiline URL expression support.
View 69 more changes
References (6)[1]: Vite successfully upgraded to 7.1.11, patching critical arbitrary file read vulnerabilities vpn-frontend/package-lock.json Line 14461 in 4c8806b [2]: @tailwindcss/vite 4.1.14 peer dependency explicitly supports 'vite': '^5.2.0 || ^6 || ^7', confirming full compatibility vpn-frontend/package-lock.json Line 3082 in 4c8806b [3]: @types/node 24.0.10 installed, satisfying Vite 7.1.11's optional peer dependency requirement of ^20.19.0 || >=22.12.0 vpn-frontend/package-lock.json Line 3459 in 4c8806b [4]: Vite's @types/node peer dependency is marked as optional, preventing installation failures vpn-frontend/package-lock.json Line 14499 in 4c8806b [5]: Project uses @tailwindcss/vite plugin which is confirmed compatible with Vite 7 Line 3 in 4c8806b [6]: Vite dependency declaration allows for automatic patch updates within 7.1.x range Line 51 in 4c8806b fossabot analyzed this PR using dependency research. |
Bumps vite from 7.1.9 to 7.1.11.
Release notes
Sourced from vite's releases.
Changelog
Sourced from vite's changelog.
Commits
8b69c9erelease: v7.1.11f479cc5fix(dev): trim trailing slash beforeserver.fs.denycheck (#20968)6fb41a2chore(deps): update all non-major dependencies (#20966)a817307build: remove hash from built filenames (#20946)ef411cebuild: remove cjs reference in files field (#20945)d0094afrefactor: use subpath imports for types module reference (#20921)ed4a0dcrelease: v7.1.10c714776fix: preserve original sourcemap file field when combining sourcemaps (#20926)446eb38fix(esbuild): inject esbuild helpers correctly for esbuild 0.25.9+ (#20906)879de86fix(deps): update all non-major dependenciesDependabot 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.