chore(deps): update dependency browserify-istanbul to v3

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
browserify-istanbul	^2.0.0 → ^3.0.0

---

Release Notes

devongovett/browserify-istanbul (browserify-istanbul)

v3.0.1: Updated readme + .travis.ci

Compare Source

• Removed istanbul from the readme as default install step
• Dropped old version of node from the TravisCI manifest

v3.0.0: ES2016

Compare Source

• ES2016 support (thanks @​mikeal)
• Switched to istanbul-lib-instrument
• Updated development dependencies

---

Configuration

📅 Schedule: (UTC)

• 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 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.

---

Note

Low Risk
Low risk dependency bump limited to the dev/test toolchain; main runtime code is untouched. Risk is mainly around potential changes in browser test coverage instrumentation behavior.

Overview
Updates the dev dependency browserify-istanbul from ^2.0.0 to ^3.0.0 and refreshes yarn.lock accordingly, pulling in the new istanbul-lib-instrument-based dependency tree.

This change only affects the browserify-based coverage instrumentation used in the test/build tooling, not the library’s runtime behavior.

^{Reviewed by Cursor Bugbot for commit 9fa0c97. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cypress-app-bot]

See the guidelines for reviewing dependency updates for info on how to review dependency update PRs.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 9fa0c97. Configure here.}

[cursor]

Duplicate lodash resolution creates unnecessary second copy

Low Severity

The lockfile introduces a separate lodash@^4.17.4 entry resolving to 4.18.1, while the existing entry for other ^4.x ranges already resolves to 4.17.21. Since 4.17.21 satisfies ^4.17.4, these entries could be deduplicated. Instead, two different versions of lodash will be installed simultaneously, increasing node_modules size and causing the new babel 6.x transitive dependencies to use a different lodash version than the rest of the project.

Additional Locations (1)

• yarn.lock#L4138-L4142

 

^{Reviewed by Cursor Bugbot for commit 9fa0c97. Configure here.}