I have never ever experienced such a bad upgrade process as with Phoenix 1.7 to 1.8.

First there is no official upgrade guide.

Tailwind asset pipeline with esbuild was broken, surface component library recommends updating all forms to .form, DaisyUi is suddenly introduced, but the generated apps don’t introduce it the way, the tailwind hex module does.

Now y classic views (I refuse to call them dead views) try to load a LayoutView of the form MyAppWeb.ControllernameMyApp.LayoutView which obviously is not existing. The layout ‘simplification’ breaks my app completely. Migration to LiveView all over the app seems to be mandatory.
Maybe it’s because I denied to switch to scopes which also only would have introduced an unnecessary level of complexity.
I don’t know, I don’t want to blame anybody, but it’s super frustrating. I am currently thinking about dropping a codebase of 2k+ hours of work.

Can confirm. It’s just needed for colocated JS atm.

I ended up pretty much where you’re describing, and ended up working piece-by-piece through a diff to get things working.

It was not a particularly enjoyable upgrade, but it was nice to be able to rip out the few remaining npm dependencies in the project that I upgraded (type definitions and daisyUI v4).