Vite 8 Issues

[jasonmccallister]

I'm posting this here and will probably cross post in denoland/deno if that is the right place.

I was deploying a project to Deno Deploy and upgraded to Vite 8 and started to get build errors:

Uncaught (in promise) SyntaxError: The requested module 'node:util' does not provide an export named 'parseEnv' at file:///tmp/build/src/node_modules/.deno/vite@8.0.0/node_modules/vite/dist/node/chunks/node.js:12:46
	const { createBuilder } = await import("./chunks/build.js");
	                          ^
    at async CAC.<anonymous> (file:///tmp/build/src/node_modules/.deno/vite@8.0.0/node_modules/vite/dist/node/cli.js:764:28)
(exit code 1)

From what I gather, Vite 8 uses node:util.parseEnv which requires Node.js 20.19+ and Deno's Node compat layer doesn't support this yet?

Downgrading to Vite 7 (^7.0.0 → resolved to 7.3.1) fixes it with no other changes needed to the build step.

[Ionaru]

parseEnv was added in Deno 2.7.0: https://github.com/denoland/deno/releases/tag/v2.7.0

[lunadogbot]

Thanks for the report — and @Ionaru is right that parseEnv landed in Deno 2.7.0, so the original node:util symptom should now be resolved on the runtime side.

That said, full Vite 8 support inside @fresh/plugin-vite isn't there yet — it's tracked in #3777 ("Tracking Vite 8, rolldown issues for @fresh/plugin-vite") and worked on in #3760 / #3646. Until those land, Vite 7 (currently ^7.0.0) is the supported version, which matches your finding that downgrading fixes the build.

Going to label this bug + upstream and leave it open as a concrete deployment-side instance under the #3777 umbrella. If you're tracking Vite 8 readiness, that's the right thread to subscribe to.