django-vitevue VS django-vite-example

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.

The django-vitevue package helps configuring a Vitejs frontend for Django. It's main feature is a management command to configure a Vitejs app to compile to Django templates and static files. It handles single page apps as well as partial Django templates and works with existing frontends

Good point. I would add that sometimes having a modern spa dev env makes sense, to take advantage of major improvements in frontend stacks like Typescript or hot module reload servers like Vitejs, and use drf or graphql on the Django backend side. Btw I made a package to help configuring a Vitejs frontend to compile to Django templates, if anyone interested by this approach: django-vitevue

You could be interested by django-vitevue if you want to use Vitejs for your frontend. This packages helps generating a Vitejs configuration to compile your modern components based frontend app to a Django template and static files. It can compile to a partial template that can be included in your pages like any other template. Note: this package has just been rewritten and released, it is brain new

I found this example which looks helpful - am I right in thinking that moving to vite will need me to have a single static/ directory rather than one per app?