Skip to content

chore(deps-dev): bump @vitest/coverage-v8 from 4.1.9 to 4.1.10#237

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/vitest/coverage-v8-4.1.10
Open

chore(deps-dev): bump @vitest/coverage-v8 from 4.1.9 to 4.1.10#237
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/vitest/coverage-v8-4.1.10

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 6, 2026

Copy link
Copy Markdown
Contributor

Bumps @vitest/coverage-v8 from 4.1.9 to 4.1.10.

Release notes

Sourced from @​vitest/coverage-v8's releases.

v4.1.10

   🐞 Bug Fixes

    View changes on GitHub
Commits

Dependabot compatibility score

Dependabot 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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) from 4.1.9 to 4.1.10.
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md)
- [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.10/packages/coverage-v8)

---
updated-dependencies:
- dependency-name: "@vitest/coverage-v8"
  dependency-version: 4.1.10
  dependency-type: direct:development
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Jul 6, 2026
@cubehouse

Copy link
Copy Markdown
Member

Holding off on this one — root-caused the CI failure, it's not something wrong in this repo.

This bump pulls vite 8.0.16 → 8.1.3 in transitively. Every test file that imports a decorated class (@config, @cache, @http, @inject, @destinationController — used throughout src/parks/) fails with SyntaxError: Invalid or unexpected token. Isolated it to a minimal repro (a bare class with one class decorator and one property decorator, no factories, no parameters) — fails identically, so it's not anything unusual in how this codebase uses decorators.

Ruled out esbuild itself: it's pinned to the exact same version (0.28.1) on both sides of this bump, and tested directly — it parses the same decorator syntax fine, both with and without experimentalDecorators explicitly set. So the break isn't in esbuild's TS/decorator handling.

That points at es-module-lexer, the lightweight scanner Vite runs ahead of the esbuild transform to find imports/exports. Its version churned hard in exactly this Vite range — vite's own changelog: bumped to 2.0.0 in 8.1.0-beta, reverted to 2.1.0 in 8.1.2, bumped again to 2.3.0 in 8.1.3. Two other confirmed regressions already came out of that same window in the same code path (vitejs/vite#22750 — the scanner mistaking a class method literally named import for a dynamic import() call and corrupting the output; es-module-lexer#214 — a separate large-input parsing regression). No existing report matches decorators specifically, so this looks like an unreported gap in the same family rather than a known, tracked bug.

Leaving this open rather than closing it — a future vite/es-module-lexer patch may fix it and dependabot will pick that up automatically. Not merging until then. Backlogged: maybe file this upstream with the minimal repro if it's still broken next time we look.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant