django-webpack-loader VS django-components

Django Webpack Loader

Check out https://github.com/django-webpack/django-webpack-loader

About one month ago i started having a lot of doubts on my frontend. At first, instead of decoupling frontend from backend, i decided to use a library called django-webpack-loader that lets me serve webpack from Django templates, so i created a Vue app and served it from Django (i used a simple index.html view). So at this point i basically have a SPA that instead of being decoupled from Django, it's served by Django.

You can do this with Django and nothing else easily or you can use a third party library called Django-Webpack-Loader.

In addition to what's already been said (completely separate frontend & backend; or do a CDN include), I've worked in a codebase that uses django-webpack-loader.

The biggest challenge to using Django with React IMO is getting the right blend of isomorphic rendering down. I don't want to go full SPA with Django as this defeats the purpose of Django IMO. Most parts of the site I want server-rendered, while in stateful parts I want React. So, let's say I have a site with 20 different React "apps" (i.e. stateful components) that I want to distribute amongst my various Django sections (Django "Apps" within the same project). And I want to do that with one webpackconfig. How do I tell my webpack where to put all those react bundles? The answer I've found is django-webpack-loader[1], however as you can see in the Issues section, one of the biggest limitations here is the inability to chunk React (and other issues).

Does anyone have a solution they like for this kind of isomporphic Django problem?

1. https://github.com/owais/django-webpack-loader

The same can be said of a React frontend that talks to a JSON API. There is some structure, organization, and convention to the API endpoints, one-way data flow, and so on. Otherwise it’s chaos.

On our most recent project we do the same with Django and HTMX. Organized endpoints by component. Composable, reusable server-side components with django-components [1]. And we’ve been orders of magnitude more productive, shipping more in 1-2 months than we did the previous 12-18 months working with React.

[1] https://github.com/EmilStenstrom/django-components

Yes. Or django-components

I use django-components to break templates into very small pieces, and never had any of the issues you describe.

I've been reading about django-components and #slippers components, but don't know about combining Pre or PostCSS, Tailwind or XXX for styling and how to keep the whole thing as simple to maintain as possible. Not willing to go the Bootstrap route, but need to structure a compromise.

I had used this project for creating components https://github.com/EmilStenstrom/django-components/

Also, for simpler cases I include partial templates.

In React it is as simple Django with https://github.com/EmilStenstrom/django-components installed {% component_block "button" intent="primary" %} Now everyone using Django would have to create their own components, they also have to do this in React which is a waste.

I felt the ux around registering new components to be much stronger with https://github.com/EmilStenstrom/django-components although I do like how slippers uses attributes

That said, you might find this package interesting: https://github.com/EmilStenstrom/django-components/