django-rest-cli VS django-ninja

You'd be prompted to start your project from one of three templates: Basic, Medior, and Advanced templates. Learn more about what each template comes bundled with here.

I honestly just followed the tutorial on https://django-ninja.rest-framework.com/ because I read about it and wanted to test it out / learn something new.

I find https://django-ninja.rest-framework.com/ even more awesome these days because it natively integrates with Django ORM, which I prefer over alternatives such as SQLAlchemy.

If you've used FastAPI before, you should check out django-ninja for your views and just familiarize yourself with the Django ORM to do database operations (e.g. https://docs.djangoproject.com/en/4.1/topics/db/queries/). That'll probably get you 80% of what you need.

My stack is now django-ninja (instead of DRF) and Vuejs 3 with Typescript for the single page app frontend. I have a starter template with this stack if you want to check it out

Nowadays, Django has an amazing library which is a lot like FastAPI but in the Django ecosystem.

https://django-ninja.rest-framework.com/

It's absolutely wonderful. I would use that in a MVP, and do the F/E in NextJS + Typescript.

But it seems that its doing what django-ninja is doing. Is there any difference between these 2 packages?

A modern alternative to DRF to build apis in Django is django-ninja. It is very simple to use and it takes advantage of the Pydantic schemas for validation and provides an auto-generated api doc. It is less complex than DRF. I recently made a template repo using this stack. It includes Django forms support in the Vuejs frontend. The Django config was made using django-vitevue that can help configuring a Vitejs frontend quickly.

Django ninja strawberry Graphene

Personally, I now prefer django-ninja for my APIs. I think it's structured better, faster to get started with and more comprehensible than DRF.

While I think it's a bad idea, I wonder if you could add Django Ninja and that would be good enough.