1.5 year ago I joined Emil on django-components as I was frustrated with Django.
Now the project is much further and we're starting the discussion on how it could be merged to Django.
Please share your thoughts or concerns!
Getting django-components to Django 6.1 or 6.2 would be lit af.

Asking Chatty how to make black tea faster and it whips up pandas. 👌

Well this is... something. Python, 2025. The best way for statically typing methods on subclasses? Generics? No. Overloads? No. Codegen? No. Instead? Give up and do it manually.

Can you recommend some tutorials with advanced setup for vibe coding / AI code assistants? I wanna know if my codebase is just too complex or I'm falling behind

@pypi.org Down?

Just published djc-heroicons - this is the first package with shareable components for django-components. So kind of a HelloWorld :)

pypi.org/project/djc-...

This weekend I've build 2 packages for django-components
- One for icons from HeroIcons.com
- The other for "ErrorBoundary" component

Still blocked by a few more PRs on django-components, but will ship it as soon as possible.

For django-components I wrote a utility for defining and parsing Django template tags - You define the spec ("TagSpec") with args, kwargs, and flags (and more) that the template tag uses. And the utility does the parsing for you.

Should I make it into a standalone package?

Recently we got startups and SMEs asking about django-components. Is there any unknowns? What's something that makes the decision / comparison either difficult or ambiguous? What can we improve?

1/5 Over at django-components we're working towards the equivalent of Vue + LiveWire, but directly in Django. If you're looking for a challenge and learning experience, you could work on any of these (thread)

github.com/EmilStenstro...