Skip to content

Vite 7 + friends #2844

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Jul 2, 2025
Merged

Vite 7 + friends #2844

merged 4 commits into from
Jul 2, 2025

Conversation

david-crespo
Copy link
Collaborator

https://vite.dev/blog/announcing-vite7

Next step is trying out rolldown-vite, which is very close to ready.

Draft because I'm seeing test failures locally.

Copy link

vercel bot commented Jul 2, 2025

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

Name Status Preview Updated (UTC)
console ✅ Ready (Inspect) Visit Preview Jul 2, 2025 4:59pm

@david-crespo david-crespo marked this pull request as ready for review July 2, 2025 15:35
@@ -24,7 +24,7 @@
"skipLibCheck": true,
"sourceMap": true,
"strict": true,
"target": "es2020",
"target": "es2022",
Copy link
Collaborator Author

@david-crespo david-crespo Jul 2, 2025

Choose a reason for hiding this comment

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

The need for this has to be related to the following, but I don't really get it because I don't see how Vite's target should affect what TS is checking, which would be the source code.

Default Browser Target Changed to Baseline Widely Available

Baseline gives us clear information about which web platform features work across their core browser set today. Baseline Widely Available indicates the feature is well-established and works across many devices and browser versions, being available across browsers for at least 30 months.

In Vite 7, the default browser target is changing from 'modules' to a new default: 'baseline-widely-available'. The set of browsers will be updated on each major to match the list of minimum browser versions compatible with Baseline Widely available features. The default browser value of build.target is changing in Vite 7.0:

Chrome 87 → 107
Edge 88 → 107
Firefox 78 → 104
Safari 14.0 → 16.0

This change adds predictability to the default browser target for future releases.

https://vite.dev/blog/announcing-vite7.html#default-browser-target-changed-to-baseline-widely-available

vitejs/vite#20007

@david-crespo
Copy link
Collaborator Author

Getting a weird set of e2e failures locally but only sometimes. And it seems to be similarly intermittent on CI.

image image

The only clue is that when it fails we seem to be getting this message. But if you run it again a second time a) it does not output the message, and b) the tests pass.

[WebServer] (!) Failed to run dependency scan. Skipping dependency pre-bundling. Error: failed to resolve rollupOptions.input value: "index.html".
[WebServer]     at resolvePath (file:///Users/runner/work/console/console/node_modules/vite/dist/node/chunks/dep-Bsx9IwL8.js:10766:29)
[WebServer]     at async Promise.all (index 0)
[WebServer]     at async computeEntries (file:///Users/runner/work/console/console/node_modules/vite/dist/node/chunks/dep-Bsx9IwL8.js:10771:44)
[WebServer]     at async scan (file:///Users/runner/work/console/console/node_modules/vite/dist/node/chunks/dep-Bsx9IwL8.js:10701:19)
[WebServer]     at async file:///Users/runner/work/console/console/node_modules/vite/dist/node/chunks/dep-Bsx9IwL8.js:34671:15

@david-crespo david-crespo merged commit eb7a44e into main Jul 2, 2025
11 of 12 checks passed
@david-crespo david-crespo deleted the vite-7 branch July 2, 2025 19:13
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.

1 participant