Tanstack Start not responding with Vite v8 beta, Nitro v3 alpha, in Azure on windows server

[kabforks]

Describe the bug

Hello!

I've got a running Tanstack Start app, with Nitro v3 Alpha 1,running in Azure on a windows machine, with Node 24, with node-preset . This works fine when it is bundled with Vite 5, 6 and 7.

However, it doet not seem to respond when bundled with Vite 8. It does start locally on my machine, when I run the bundled code. I have Node 22 locally.

As for error messages... i don't have any! The application seems to start, but not respond.

I've tried to launch the app via Azure Kudo command line:

PS C:\home\site\wwwroot> & "C:\Program Files\nodejs\24.7.0\node.exe" run.cjs
& "C:\Program Files\nodejs\24.7.0\node.exe" run.cjs
[uncaughtException] Error: listen EADDRINUSE: address already in use :::3000
at Server.setupListenHandle [as _listen2] (node:net:1940:16)
at listenInCluster (node:net:1997:12)
at Server.listen (node:net:2102:7)
at file:///C:/home/site/wwwroot/server/chunks/nitro/nitro.mjs:712:21

Interestingly, it says the address is already in use. So the app is started... but there is no response, no errors. I'm clueless. I've tried Nitro v3 alpha 0 - same behavoir. Vite 8 beta 5 and 6 does not work either.

My config files.

vite.config.ts

import tsConfigPaths from "vite-tsconfig-paths"
import { defineConfig } from "vite"
import viteReact from "@vitejs/plugin-react"
import { nitro } from "nitro/vite"
import { tanstackStart } from "@tanstack/react-start/plugin/vite"

export default defineConfig({
	build: {
		outDir: ".output"
	},
	plugins: [
		tsConfigPaths({
			projects: ["./tsconfig.json"]
		}),
		tanstackStart(),
		nitro({
			 //@ts-ignore
				preset: "node-server"
			 
		}),
		viteReact()
	]
})

tsconfig.ts

{
	"extends": "../../tsconfig.json",
	"compilerOptions": {
		"moduleResolution": "bundler", // best for bunller
		"module": "esnext", // bundler håndterer module format
		"target": "es2020", // bundler transpilerer ned
		"esModuleInterop": true, // for CommonJS interop
		"allowSyntheticDefaultImports": true, // samme som over
		"sourceMap": true,
		"inlineSourceMap": false,
		"jsx": "react-jsx"
	},
	"include": ["src/**/*", "vite.config.ts", "vitest.config.ts"],
	"exclude": ["node_modules", "dist"]
}

package.json

		"@tanstack/react-router": "^1.144.0",
		"@tanstack/react-router-devtools": "^1.144.0",
		"@tanstack/react-start": "^1.145.3",
                "vite": "8.0.0-beta.7",

Local start is run with:

"start": "set PORT=5173 && node .output/run.cjs",

run.js

// https://github.com/nuxt/nuxt/issues/24904#issuecomment-1869496853
if (process.env.PORT && process.env.PORT.startsWith("\\")) {
	process.env.NITRO_UNIX_SOCKET = process.env.PORT
	delete process.env.PORT
}

import("./server/index.mjs")

web.config

....
        <handlers>
            <!-- Indicates that the server.js file is a node.js site to be handled by the iisnode module -->
            <add name="iisnode"
                 path="run.cjs"
                 verb="*"
                 modules="iisnode" />
        </handlers>
....

Reproduction

none

Steps to reproduce

I do not have an URL to reproduce it, as it seems to only happen in a specific environment

System Info

Tanstack Start 1.144
Vite 8 beta 7
Nitro alpha 1 
Node 24

Used Package Manager

pnpm

Logs

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[kabforks]

Updated to vite 8 beta 14 and nitro 3.0.1-alpha.2. Same behaviour.