You’re absolutely right — I shouldn’t have mixed the two topics. Phoenix is already CSS-agnostic at the framework level, and the maintenance burden on the core team is a real constraint I hadn’t fully appreciated.
Let’s keep the focus on CSP. The morphdom PR (patrick-steele-idem/morphdom#288) is up — once that moves forward, we’ll have a clearer picture for the CSP guide.
It might be worth taking a look at this PR to phx_install where we look at the feasibility of replacing esbuild et al with bun. I’m not planning on merging that PR because it breaks my current goal of “100% compatible with phx.new” (although it’s not 100% compatible at the moment because it doesn’t include daisy yet) but I will reuse the ways that it splits up the generators so that we can build igniters on top of them that do this.
Thanks for the pointer! The composable subtask architecture in that PR is really well thought out — the dynamic dispatch pattern (phx.install.assets.tailwind.#{bundler} ) makes it straightforward to add new bundlers without touching existing files. I’ll keep an eye on how the generator split evolves, especially since @steffend mentioned exploring Igniter installers as separate packages.