Vite dev no port printed Windows PowerShell

[guangyiliushan]

Vite 7.1.0 dev server starts but doesn't print port/URL information on Windows PowerShell.

Issue Description

When running pnpm dev in my Vite React project, the development server appears to start successfully but doesn't print the usual server information (Local/Network URLs, port number, etc.) in the terminal. I don't know if it's related to Vite or caused by any other issues.

Environment

• OS: Windows 11
• Terminal: PowerShell
• Node.js: v22.16.0
• pnpm: 10.12.3
• Vite: 7.1.0
• Package Manager: [email protected]

Repository

The frontend folder in the branch of this Git repository

Expected Behavior

After running pnpm dev, I should see output like:

  VITE v7.1.0  ready in 500ms

  ➜  Local:   http://localhost:5173/
  ➜  press h + enter to show help

## Actual Behavior
The command runs without errors but 
only shows:

[email protected] dev D:\Project\Project\mail\frontend
vite

Then the terminal appears to hang 
with no further output.

## What I've Tried
- pnpm dev --debug - no 
additional output
- pnpm dev --verbose - no 
additional output  
- pnpm dev --host --port 5173 - 
same issue
- npx vite --host --port 5173  --debug - same issue

## Project Setup
- React 19.1.1 + TypeScript
- Vite config uses @vitejs/
plugin-react and @tailwindcss/vite
- package.json has "type":  "module"

## Additional Context
The development server might 
actually be running (have 
confirmed http://localhost:5173 
is not works), but the lack of terminal 
output makes it impossible to know 
the correct URL or port.

Has anyone experienced similar 
issues with Vite 7.x on Windows? 

## Vite Config

import path from "path"
import tailwindcss from 
"@tailwindcss/vite"
import react from "@vitejs/
plugin-react"
import { defineConfig } from "vite"

export default defineConfig({
  plugins: [react(), tailwindcss()],
  resolve: {
    alias: {
      "@": path.resolve(__dirname, 
      "./src"),
    },
  },
})

[guangyiliushan]

I reinitialized the app with a fresh scaffold using pnpm create vite (React + TypeScript) and chose to keep the newly generated files (i.e., I didn’t reuse my previous config/files). After a clean install, pnpm dev started printing the expected Local/Network URLs again. So the functionality is restored, but I’m not sure what the root cause was.

If anyone has ideas on what could cause Vite 7 to start the dev server without printing the port/URLs in PowerShell, I’d appreciate pointers. Possible suspects I’m considering:

A misconfiguration in vite.config.ts (e.g., logLevel, custom logger, or a plugin swallowing logs)
Version mismatch between vite and plugins/@types/react/react-refresh
Corrupted node_modules or pnpm store/cache
Differences in tsconfig, index.html, or package.json scripts that affect how vite runs
Happy to share diffs (package.json, vite.config.ts, tsconfig, index.html) between the old project and the fresh scaffold if that helps narrow it down.