Nitro Vite Feedback

[pi0]

🎉 Nitro v3 is becoming "just" a Vite plugin!

This discussion aims to gather early feedback and ideas from the community before wide adoption, API is not final an open to any changes!

In case of issues, feel free to report them as a bug or here with some reproduction and env info by running:

npx --yes envinfo --system --binaries --npmPackages

Links

• Starters and examples: https://github.com/nitrojs/vite-examples
• Issue tracker: Nitro Vite Tracker #3461
• Design proposal: https://www.notion.so/pi0/Nitro-Vite-229054ae036a808886b1fd727f85f1b0
• Plugin source: https://github.com/nitrojs/nitro/tree/v3/src/build/vite

[hairyf]

I tried both the examples and v3 branch cases and got the following errors:

{
  "error": "Dev server is unavailable.",
  "hint": "Please reload the page and check the console for errors if the issue persists."
}

[pi0]

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)

[hairyf]

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

[pi0]

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

[hairyf]

Additionally, I’m a bit confused about what’s happening. All the use cases I’ve seen consistently use the following pattern:

export default {
  fetch: (req: Request): Response | Promise<Response> => {
    ...
  },
};

Do I need to handle all requests here? This seems inconvenient and not concise enough. How is this different from file-based routing?

[pi0]

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.

[roduyemi]

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

[pi0]

@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.

[TechAkayy]

I tried vue-ssr app at https://github.com/nitrojs/vite-examples/tree/main/examples/vue-ssr. When I built the app (npm run build), and served it as node .output/server/index.mjs, I notice that the styles didn't get generated, any tricks?