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

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
vite-plugin-istanbul	5.0.0 -> 6.0.2

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

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

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: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, 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.

[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 error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/vite
npm error   dev vite@"3.2.10" from the root project
npm error
npm error Could not resolve dependency:
npm error peer vite@">=4 <=6" from [email protected]
npm error node_modules/vite-plugin-istanbul
npm error   dev vite-plugin-istanbul@"6.0.2" 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-05T18_06_46_255Z-eresolve-report.txt

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

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
react-stick	❌ Failed (Inspect)			Jul 3, 2024 2:08pm

[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 error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/vite
npm error   dev vite@"3.2.10" from the root project
npm error
npm error Could not resolve dependency:
npm error peer vite@">=4 <=6" from [email protected]
npm error node_modules/vite-plugin-istanbul
npm error   dev vite-plugin-istanbul@"6.0.2" 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-07-03T14_08_16_180Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-07-03T14_08_16_180Z-debug-0.log