Skip to content

👷 Update dependency vite to v8#164

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/vite-8.x
Open

👷 Update dependency vite to v8#164
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/vite-8.x

Conversation

@renovate

@renovate renovate Bot commented Jul 4, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
vite (source) 7.3.58.1.3 age confidence

Release Notes

vitejs/vite (vite)

v8.1.3

Compare Source

Bug Fixes

v8.1.2

Compare Source

Bug Fixes

v8.1.1

Compare Source

Features
Bug Fixes
Miscellaneous Chores
Code Refactoring
  • css: remove lightningcss null byte bug workaround (#​22822) (2dafd3b)
  • use pre-defined environments variable to avoid duplicate Object.values calls (#​22790) (1113acf)
Tests
  • enable "manual chunk path" test and remove "worker.format error" test (#​22824) (c088511)

v8.1.0

Compare Source

Features
Bug Fixes
Code Refactoring

v8.0.16

Compare Source

Bug Fixes

v8.0.15

Compare Source

Features
Bug Fixes
  • capitalize error messages and remove spurious space in parse error (#​22488) (85a0eff)
  • deps: update all non-major dependencies (#​22511) (2686d7d)
  • dev: fix html-proxy cache key mismatch for /@​fs/ HTML paths (#​21762) (47c4213)
  • glob: error on relative glob in virtual module when no files match (#​22497) (5c8e98f)
  • optimizer: close the rolldown bundle when write() rejects (#​22528) (e3cfb9d)
  • resolve: provide onWarn for viteResolvePlugin in JS plugin containers (#​22509) (40985f1)
Miscellaneous Chores
Code Refactoring

v8.0.14

Compare Source

Features
Bug Fixes
Miscellaneous Chores
  • deps: update rolldown-related dependencies (#​22470) (7cb728e)
  • remove irrelevant commits from changelog (2c69495)
Code Refactoring
Tests

v8.0.13

Compare Source

Features
Bug Fixes
Miscellaneous Chores

v8.0.12

Compare Source

Features
Bug Fixes
  • create-vite: pass react framework to TanStack CLI (#​22397) (18f0f90)
  • deps: update all non-major dependencies (#​22420) (2be6000)
  • module-runner: prevent partial-exports race on concurrent imports of in-flight invalidated re-export chains (#​22369) (f5a22e6)
  • refer to rolldownOptions instead of deprecated rollupOptions in messages (#​22400) (b675c7b)
  • worker: apply build.target to worker bundle (#​22404) (3c93fde)
  • worker: forward define to worker bundle transform (#​22408) (d4838a0)
Miscellaneous Chores

v8.0.11

Compare Source

Features
Bug Fixes
Documentation
Miscellaneous Chores
Code Refactoring
Tests

v8.0.10

Compare Source

Features
Bug Fixes
  • hmrClient.logger.debug and hmrClient.logger.error looked different from other HMR logs (#​22147) (a4d828f)
  • css: show filename in CSS minification warnings for .css?inline (#​22292) (83f0a78)
  • optimizer: allow user transform.target to override default in optimizeDeps (#​22273) (5c7cec6)
  • remove format sniffing module resolution from JS resolver (#​22297) (b8a21cc)
Code Refactoring

v8.0.9

Compare Source

Features
Bug Fixes
Documentation
Miscellaneous Chores

v8.0.8

Compare Source

Features
Bug Fixes

v8.0.7

Compare Source

Bug Fixes
  • use sync dns.getDefaultResultOrder instead of dns.promises (#​22185) (5c05b04)

v8.0.6

Compare Source

Features
Bug Fixes
Performance Improvements
  • early return in getLocalhostAddressIfDiffersFromDNS when DNS order is verbatim (#​22151) (56ec256)
Miscellaneous Chores

v8.0.5

Compare Source

Bug Fixes

v8.0.4

Compare Source

Features
Bug Fixes
Documentation
Miscellaneous Chores
Code Refactoring

v8.0.3

Compare Source

Features
Bug Fixes
  • html: cache unfiltered CSS list to prevent missing styles across entries (#​22017) (5464190)
  • module-runner: handle non-ascii characters in base64 sourcemaps (#​21985) (77c95bf)
  • module-runner: skip re-import if the runner is closed (#​22020) (ee2c2cd)
  • optimizer: scan is not resolving sub path import if used in a glob import (#​22018) (ddfe20d)
  • ssr: ssrTransform incorrectly rewrites meta identifier inside import.meta when a binding named meta exists (#​22019) (cff5f0c)
Miscellaneous Chores
Tests

v8.0.2

Compare Source

Features
Bug Fixes
Miscellaneous Chores

v8.0.1

Compare Source

Features
Bug Fixes
Miscellaneous Chores

v8.0.0

Compare Source

Features
Bug Fixes

v7.3.6

Compare Source

Please refer to CHANGELOG.md for details.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "every weekend"
  • 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.

@renovate renovate Bot requested a review from a team as a code owner July 4, 2026 14:12
@datadog-official

datadog-official Bot commented Jul 4, 2026

Copy link
Copy Markdown

Pipelines

Fix all issues with BitsAI

⚠️ Warnings

🚦 1 Pipeline job failed

DataDog/electron-sdk | integration   View in Datadog   GitLab

Useful? React with 👍 / 👎

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 1ee2127 | Docs | Datadog PR Page | Give us feedback!

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR Review — Score: 4.3 / 5

Straightforward Renovate bump that brings the last Vite 7 integration fixture (electron-vite-esm) onto Vite 8, matching the coverage already exercised by forge-vite and electron-builder-vite on main. The change is correctly scoped to the e2e app only — no SDK plugin or public API changes are required. I would approve once the lockfile is brought in line with package.json.

Why 4.3: The dependency alignment is the right move for bundler coverage, the diff is minimal and low-risk, and the bump exercises the ESM electron-vite path that is distinct from the other Vite fixtures.

Why not 5: yarn.lock still pins Vite 7.3.5 while package.json requests 8.1.0, and this app lands on 8.1.0 while sibling Vite fixtures remain on 8.0.16.


Findings

  • [Minor] Stale yarn.lockpackage.json requests Vite 8.1.0 but the committed lockfile still resolves vite@npm:7.3.5.
  • [Nit] Vite patch skewelectron-vite-esm will test 8.1.0 while forge-vite and electron-builder-vite stay on 8.0.16.
Open in Web View Automation 

Sent by Cursor Automation: electron-sdk reviews

"electron-vite": "5.0.0",
"typescript": "5.9.3",
"vite": "7.3.5"
"vite": "8.1.0"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yarn.lock in this app still resolves vite@npm:7.3.5, so the committed install graph does not match this pin. CI works around this today via yarn install --no-immutable in scripts/install-integration-apps.ts, but other Vite fixtures (forge-vite, electron-builder-vite) keep package.json and yarn.lock in sync.

Please run yarn install in e2e/integration/apps/electron-vite-esm/ and commit the updated lockfile. While here, consider aligning to 8.0.16 with the other Vite apps unless you intentionally want this fixture on the latest 8.1.x line.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a82d21d1d7

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

"electron-vite": "5.0.0",
"typescript": "5.9.3",
"vite": "7.3.5"
"vite": "8.1.0"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Keep Vite within electron-vite's peer range

This fixture still depends on electron-vite 5.0.0, and the checked-in lockfile for this app records electron-vite@npm:5.0.0 with peer vite: ^5.0.0 || ^6.0.0 || ^7.0.0 (e2e/integration/apps/electron-vite-esm/yarn.lock:2272-2284). In the electron-vite-esm integration build, installing vite 8.1.0 therefore creates an unsupported peer combination for the tool that runs electron-vite build; update electron-vite to a release that supports Vite 8 and regenerate the lockfile, or keep this app on Vite 7.

Useful? React with 👍 / 👎.

@renovate renovate Bot force-pushed the renovate/vite-8.x branch 2 times, most recently from e1c09e5 to 436fba0 Compare July 7, 2026 20:33
@renovate renovate Bot force-pushed the renovate/vite-8.x branch from 436fba0 to 1ee2127 Compare July 9, 2026 06:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants