Bump vite from 7.1.4 to 7.1.5 in the npm_and_yarn group across 1 directory

[dependabot]

Bumps the npm_and_yarn group with 1 update in the / directory: vite.

Updates vite from 7.1.4 to 7.1.5

Release notes

Sourced from vite's releases.

v7.1.5

Please refer to CHANGELOG.md for details.

Changelog

Sourced from vite's changelog.

7.1.5 (2025-09-08)

Bug Fixes

• apply fs.strict check to HTML files (#20736) (14015d7)
• deps: update all non-major dependencies (#20732) (122bfba)
• upgrade sirv to 3.0.2 (#20735) (09f2b52)

Commits

• 5647540 release: v7.1.5
• 09f2b52 fix: upgrade sirv to 3.0.2 (#20735)
• 14015d7 fix: apply fs.strict check to HTML files (#20736)
• 122bfba fix(deps): update all non-major dependencies (#20732)
• See full diff in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
  You can disable automated security fix PRs for this repo from the Security Alerts page.

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[jazzberry-ai]

Bug Report

Name|Severity|Example test case|Description
Vite and Rollup update may cause regressions with destructuring default values|Medium|Test components that use destructuring with default values|The update to vite (7.1.5) and rollup (4.50.1) includes a bug fix related to destructuring default values. This could potentially introduce regressions in components that rely on this pattern. Thorough testing is recommended.

_{Comments? Email us.}

[jazzberry-ai]

Bug Report

Name	Severity	Example test case	Description
Dependency conflict between react and use-resize-observer	High	Run npm install.	The project has a dependency on use-resize-observer, which declares a peer dependency on react versions 16.8.0 to 18. However, the project itself uses react version 19.1.1, causing a dependency conflict during installation. This prevents the project from being built or run correctly.
Rollup update in Vite causes unexpected build errors	Medium	Run the build command (pnpm build).	The update of rollup from 4.50.0 to 4.50.1 within vite might introduce subtle changes in the bundling process, leading to unexpected build errors or warnings. This could be due to changes in Rollup's module resolution, code transformation, or optimization algorithms.
Incorrect plugin used in vite.lib.config.ts	Medium	Inspect vite.lib.config.ts.	vite.lib.config.ts imports react from '@vitejs/plugin-react' but vite.config.ts imports react from "@vitejs/plugin-react-swc". The vite.lib.config.ts should also be using @vitejs/plugin-react-swc to be consistent with the main config. Using different react plugins may lead to inconsistencies during the build process.

_{Comments? Email us.}

[jazzberry-ai]

Bug Report

Name	Severity	Example test case	Description
Potential issue with vite-plugin-dts	Medium	Run npm run build:lib and check for type errors in the generated .d.ts files.	Minor updates to vite can sometimes affect how types are processed, potentially leading to incorrect or incomplete type definitions generated by vite-plugin-dts.
Peer dependency conflict with use-resize-observer	Medium	Run npm install and observe the peer dependency error.	The use-resize-observer package has a peer dependency on [email protected] - 18, while the project uses [email protected]. This could lead to runtime errors or unexpected behavior.

_{Comments? Email us.}

[jazzberry-ai]

Bug Report

Name	Severity	Example test case	Description
Incompatible TypeScript Declaration Generation with vite-plugin-dts	Medium	Update vite from 7.1.4 to 7.1.5 and build the library using npm run build:lib. Check if the generated TypeScript declaration files (.d.ts) are correctly generated and reflect the changes in the codebase.	A minor update in vite may introduce changes in the internal module resolution or transformation process, which could affect the vite-plugin-dts plugin. This plugin is responsible for generating TypeScript declaration files for the library. If the update introduces incompatible changes, the generated .d.ts files might be incomplete, incorrect, or contain errors, leading to type-checking issues in projects that consume the library. This can be particularly problematic if the update changes how Vite handles different module types or introduces new ways of transforming code, as vite-plugin-dts might not be fully aware of these changes.
vitest configuration fails after vite update	Medium	Update vite from 7.1.4 to 7.1.5. Run npx vitest. Observe that the tests fail to start with an "ERR_MODULE_NOT_FOUND" error, indicating that the vitest package cannot be found.	A minor update in vite might introduce changes that affect how vitest resolves modules or loads its configuration file. This can lead to a situation where vitest is unable to locate its own package or dependencies, resulting in a startup error. This issue could arise if the update modifies Vite's internal module resolution mechanisms or alters the way it handles different file types, causing vitest to fail during the configuration loading process.

_{Comments? Email us.}

[jazzberry-ai]

Bug Report

Name	Severity	Example test case	Description
React is not defined in test environment	High	Run any test case.	After updating vite, the test suite fails with a "React is not defined" error, indicating a problem with the test environment configuration.
Test suite timeout	Medium	Run the full test suite.	The test suite times out after 10 seconds.

_{Comments? Email us.}