Ideas / wishes for Nitro v3

[MickL]

You asked to start a new discussion if we have ideas for v3, so here are my wishes:

• Add testing utilities (bootstrap, env, fetch, mocking) Add documentation for testing #2303
• Totally remove auto imports and make it an opt-in Depend less on auto imports #2232 defineNitroModule is not exported from the package #2007
• Add missing pieces to docs, not everything is documented e.g. modules Document Nitro Modules #1862
• Add more examples to the docs (compare docs to NestJS, AdonisJS, Angular), e.g. session auth with Lucia :) Add documentation for testing #2303

[InsaneNaman]

I have been tracking this project since last vite conf. I feel this project has lot of potential but I would like to politely mention that it needs extensive docs. Many devs are not even aware of this great project.

[MickL]

I fully agree about the docs

[vladkrasn]

Yeah, as a backend engineer I am interested in Nitro, but the lack of proper documentation prevents me from even trying it.
I don't know what are the actual capabilities of this project; I don't know if it's supposed to be used for building complex backends or not; Many features, I suspect, are either undocumented or documented in other packages - like h3, db0 or maybe even Nuxt (and I don't have any experience with Nuxt, unlike many people in the unjs commiunity)

[MickL]

I think I have most of my knowledge from Nuxt. I already noted that it is a problem that documentation is split into H3, Nitro and Nuxt while most is in Nuxt actually.

Additionally the ecosystem of Nitro is non-existent. It is possible to write modules (similar to Nuxt modules) but this feature is undocumented: #1862 . Further modules are developed for Nuxt only and Nitro gets nothing from the cake. For example Nuxt team is working on nuxt-auth but I dont expect nitro-auth to be coming. Or there is nuxt-security but not nitro-security: Baroshem/nuxt-security#405

I dont think Nitro is missing anything from bigger frameworks (except for testing capabilities) like NestJS or AdonisJS: We have caching, validation, security and everything else can be implemented e.g. auth with Lucia AND Nitro can be deployed everywhere which the big ones cant, BUT what is missing is documentation and tutorials.

[InsaneNaman]

I really appreciate the efforts by the nitro team and feel the same. My expertise lies in frontend (React) and unaware about the Nuxt ecosystem in depth but nitro got my attention and still i am also on the same page i.e, I dont know what nitro wants it to be (A backend framework or framework for framework or both). I am for now going towards Hono but really wants to see nitro catching up.

[alumni]

1. REST API generation: I need to generate a REST API for about a hundred entities. It would be nice to have a plug in that does this automatically.
2. Dependency injection: I have a lot of server-side code which would look ugly organized in a functional way. It would be nice to be able to create class-based route handlers (controllers) which would have services injected. It would be nice to override the injected service when testing (or when running locally).