Skip to content

bump vite from 8.0.0 to 8.3.0 - #100

Open
superagent-security[bot] wants to merge 1 commit into
mainfrom
superagent/deps/npm_and_yarn/ffb0e91c742e12ff
Open

superagent-security[bot] wants to merge 1 commit into
mainfrom
superagent/deps/npm_and_yarn/ffb0e91c742e12ff

Conversation

@superagent-security

@superagent-security superagent-security Bot commented Sep 14, 2026 •

Copy link
Copy Markdown

Bumps vite from 8.0.0 to 8.3.0.


Superagent evaluated the complete generated dependency delta before opening this pull request.

Nonblocking supply chain signals: @emnapi/core@1.8.1 has dynamic_code_execution risk; @emnapi/core@1.8.1 has network_access risk; @emnapi/core@1.8.1 has environment_access risk; @emnapi/core@1.8.1 has code_anomaly risk; @emnapi/core@1.8.1 has minified_code risk; @emnapi/wasi-threads@1.1.0 has dependency_environment_access risk; @emnapi/wasi-threads@1.1.0 has dependency_minified_code risk; @napi-rs/wasm-runtime@1.1.1 has potential_code_anomaly risk; vite@8.3.0 has ai_detected_code_anomaly risk; vite@8.3.0 has external_url_strings risk


Note

Low Risk
Lockfile-only dev tooling upgrade with no application source changes; main risk is regressions in vitest runs or local test bundling after the Vite/rolldown jump.

Overview
Updates package-lock.json so the Vitest toolchain resolves Vite 8.3.0 (from 8.0.0). There is no direct vite entry in package.json; this is a transitive dev-dependency refresh.

Vite’s bundler stack moves to rolldown ~1.2.8 (from 1.0.0-rc.9), with matching platform bindings, @oxc-project/types 0.149.0, and removal of @oxc-project/runtime from Vite’s dependency tree. Related lockfile churn includes postcss 8.5.28, tinyglobby / picomatch bumps, and lightningcss 1.33.0 under Vitest’s nested Vite. Rolldown drops the wasm32-wasi optional binding and adds android-arm-eabi; some duplicate tsx / esbuild nested entries are pruned from the lockfile.

Reviewed by Cursor Bugbot for commit 699d8e8. Configure here.

This branch has not been deployed

No deployments
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