It is a current issue with vite externals i am working on. you need to enable shamefully-hoist in .npmrc.

Can you please try one of the examples from vite-examples? 🙏🏼 (and if you do have issues please tell me more about your OS and Node.js version i can happily investigate)

I tried setting shapefully-hoist=true, but it didn't work,
I use the windows system, and the node version is v22.14.0

Hmm might be Windows specific issue. I will try to test on my windows machine and come back to you :)

I will add a routes example back. Also, please wait for the new docs for more explanation.

Services do not replace the h3 routes feature but allow a new method for integrating any framework using a separate module graph/build config, so Nitro can be used with anything without imposing built-in runtime features.

So are services more like the current nitro presets? But available in both dev and prod?

@roduyemi services are more like additional entries to enable adding any fetch-compatible framework into the Nitro server in a pluggable way. So you have a choice of using either built-in (h3) route handlers or any other framework.

Thanks for feedback. @schiller-manuel shared and we are investigating issue. It seems a difference (potentially bug) in bun's fetch.

Is there an issue I can subscribe too?

pnpm create nitro-app@latest, using the 3.0.1-alpha.0 build of nitro.

Currently getting the [nitro] No build found. Please build your project before previewing. error even though I've already built the app.

Sorry, forgot I was using nitro-nightly.

the build I'm using is 3.0.1-20251104-223815-3402cc78

After vite build, you should have a node_modules/.nitro/last-build directory. If it is not there, something is wrong. (sharing somehow your project i can better investigate)

.nitro/last-build does not appear when I finish building.

The project I cannot share directly, but it is more-or-less standard/templating stuff right now, so it should be reproducible taking note of the following info:

envinfo says the following:
System:
OS: Windows 11 10.0.26200
CPU: (12) x64 13th Gen Intel(R) Core(TM) i5-1334U
Memory: 1.86 GB / 15.69 GB
Binaries:
Node: 22.14.0 - C:\Program Files\nodejs\node.EXE
npm: 11.6.1 - C:\Program Files\nodejs\npm.CMD
pnpm: 10.18.1 - C:\Users\KT\AppData\Local\pnpm\pnpm.CMD
npmPackages:
@preact/preset-vite: ^2.10.2 => 2.10.2
nitro-nightly: 3.0.1-20251104-223815-3402cc78
preact: ^10.27.2 => 10.27.2
preact-iso: ^2.11.0 => 2.11.0
vite: ^7.1.12 => 7.1.12

nitro config object in vite.config.ts is empty, so no nitro configs are passed to it by default.

since create-nitro-app doesn't allow Preact setup by default what I did was run pnpm create preact@latest afterwards and copied the index.html + src/ folder out onto the project root.

create-preact CLI options:

Directory: doesn't matter
Project language: TypeScript
Use router? Yes
Prernder app (SSG)? No
Use ESLint? No

Preact's TSConfig was merged with Nitro's template tsconfig, see below or final tsconfig.json:

{
  "compilerOptions": {
    // Module resolution
    "target": "ESNext",
    "module": "ESNext",
    "moduleResolution": "Bundler",

    /* Preact Config */
		"jsx": "react-jsx",
		"jsxImportSource": "preact",
		"paths": {
			"react": ["./node_modules/preact/compat/"],
			"react-dom": ["./node_modules/preact/compat/"]
		},

    // Core checks
    "strict": true,
    "noEmit": true,
    "skipLibCheck": true,
    "resolveJsonModule": true,
    "allowSyntheticDefaultImports": true,

    // Additional safety
    "forceConsistentCasingInFileNames": true,
    "noImplicitReturns": true,
    "noFallthroughCasesInSwitch": true,
    "useUnknownInCatchVariables": true,
    "noUnusedLocals": true,
  }
}

Hmm might be a windows issue i guess.