chore(deps): update dependency vite-plugin-istanbul to v7

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
vite-plugin-istanbul	5.0.0 -> 7.2.0

---

Release Notes

ifaxity/vite-plugin-istanbul (vite-plugin-istanbul)

v7.2.0

Compare Source

Bug Fixes

• build type dependencies (#​351) (7c6a8b9)

Features

• add onCover callback to IstanbulPluginOptions and expose fileCoverage in Instrumenter (#​354) (9799fa3)

v7.1.0

Compare Source

Bug Fixes

• update vite peer dependency specifier to support version 7 (4dc0e9f)

Features

• update maximum version of vite peer dependency to 7 (1aa63d2)

v7.0.0

Compare Source

• fix!: corrected broken lockfile (#​339) (213cd65)

Features

• allow passing generatorOpts down to Babel (#​323) (c58d180)

BREAKING CHANGES

• previous pr made an api change

v6.0.2

Compare Source

Bug Fixes

• removed engine version (#​215) (be2d28c), closes #​214

v6.0.1

Compare Source

Bug Fixes

• only emit esm build (#​212) (895c7bb), closes #​209

v6.0.0

Compare Source

Bug Fixes

• add regex for vue SFC to prevent instrumenting style and templates (#​180) (c8a7ca7), closes #​96 #​178 #​89

• feat!: update to support vite v5 (#​183) (614f8bd), closes #​183

BREAKING CHANGES

• updating from espree v9 to v10 deprecates older node versions

• feat!: update to support vite v5

• least supported version changed from v2.9.1 to v4

---

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.

[changeset-bot]

⚠️ No Changeset found

Latest commit: fa0d563

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[renovate]

⚠️ 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 unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/vite
npm ERR!   dev vite@"4.5.14" from [email protected]
npm ERR!   apps/docs
npm ERR!     [email protected]
npm ERR!     node_modules/forge-ui-styleguide
npm ERR!       workspace apps/docs from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer vite@">=5.4.20" from [email protected]
npm ERR! node_modules/vite-plugin-checker
npm ERR!   dev vite-plugin-checker@"0.11.0" from [email protected]
npm ERR!   apps/docs
npm ERR!     [email protected]
npm ERR!     node_modules/forge-ui-styleguide
npm ERR!       workspace apps/docs 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! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2025-10-22T01_06_41_420Z-debug-0.log