Vite 8 Issues

Open
#3,694 2 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
deno, node.js, typescript, vite

Research direction

Start by checking Fresh's build and deployment entry points for compatibility with Vite 8 on Deno Deploy, then reproduce the reported node:util parseEnv import error using the issue's build setup. The report identifies no relevant files or tests, so trace how the build resolves Vite and Deno's Node compatibility layer. Done means the reported build succeeds with Vite 8 or the incompatibility is clearly documented.

Written by the indexing model from the issue text.

Description

bug upstream

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/[email protected]/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/[email protected]/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.

Dominant language
TypeScript
Stars
13.8k
Forks
757
Avg merge
3m
Merged PRs (30d)
2

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from freshframework/fresh

All issues in freshframework/fresh

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.