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 h3 useSession 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.

[InsaneNaman]

I agree with @MickL and @ivanjeremic. If nitro becomes this then it will be a go to laravel of node. I know adonis is there but idk mvc doesn't excites me that much. Nitro has the simplicity, better ecosystem, big projects already using it (nuxt) etc. Make it happen team nitro xD

[pi0]

Thanks for the kind words! We will definitely get there sometime (I hope soon, maybe this year), Nitro surely deserves a more mature ecosystem. As the creator of both Nuxt modules and Nitro, I know the value of Modules in the expansion of the ecosystem but at the same time, the fragmentation it can cause in not mature state. Every step we take at unjs is in the goodwill of both direct users and ecosystem health + adoption which, i admit makes them much much harder decisions that can be made at meta-framework level but are certainly doable and worth waiting.

[MickL]

I worked years with NestJS and I tried AdonisJS and to me Nitro can be the next big framework especially because its light weight and simple and to me and my customer a "Node" api that can run serverless is a big thing. The only thing missing are testing utilities and extensive docs and articles about it.

[MickL]

I just found out by accident that H3 (the server Nitro uses) can handle sessions and therefor there is no need for an auth library like Lucia that handles session management. The only thing missing is documentation or an article/tutorial about it ... I am in the Nitro docs and see zero results for the search term "sessions" and of course no article/tutorial can be found for that topic. For Nuxt there is an example project that can be used nearly 1 to 1 for Nitro, but whoever is using Nitro only will never find it.

[ivanjeremic]

I just found out by accident that H3 (the server Nitro uses) can handle sessions and therefor there is no need for an auth library like Lucia that handles session management.

I'm in the middle of integrating Lucia and kind of shocked now, I think it is still the best option and the session features can be combined to work together somehow, if someone has a better library please suggest it. Really hope the Docs catch up soon.

[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).

[qodeboy]

Have you managed to find a nice way around #2?

[MickL]

I come from a framework that uses DI (NestJS) and I feel like not having this is a GREAT relief. But this is only due to what I learned within Nuxt, how to create reusable utilities and composables. So what I want to say is that with a different style of programming everything can become much cleaner and easier and DI is no more needed. For people that never worked with Nuxt before this concepts should be explained in the Nitro docs imo.

What I am missing tho is also the possibility to overwrite/mock stuff for dev or testing.

Btw for #1 you could write your own plugin maybe?

[alumni]

I did not bother to try nitro/nuxt more than that. I just looked at quite a few sample repositories, did not find anything interesting, moved on.

Honestly, SAP CAP is doing what nuxt is doing and whole bunch more, so if I'd switch to something, I'd rather switch to that.

However, I stuck with NestJS, I like the design pattern more, it's more intuitive.