Hmm… when I meant LiveView being default - I probably meant Stateless Components being used everywhere for Views. More like, ViewComponents Gem by Github in the RailsWorld. Whether, those components include Javascript for the behaviour is dependent on us. Like, ViewComponents relying on Stimulus. I guess, one more Rails example and I will be kicked out of this forum 
cvkmohan
2
Sebb
cvkmohan
Oh No!!! @josevalim I am not on Twitter. And - it is purely coincidental that I raised these questions now. Never thought you will provide solution so fast!!! https://github.com/josevalim/phx_esbuild_demo
Though most of the questions are answered now - there is one still pending - and - only you can answer. And - in your usual style, you can skip it. What is the tentative release date for 1.6?
2
chrismccord
Creator of Phoenix
cvkmohan
I guess, this application is created without LiveView support. Saw some commits in LiveView and Phoenix where the core Javascript is written in Module format. May be those pushes are necessary for the esbuild to work with LiveView.
1
cvkmohan
Hmm… another interesting co-incidence. LiveView 0.16 and Phoenix 1.6 both might get released at the same time.
2
tozz
The fewer dependencies the better, and the less automagical setups the better. As in, providing the foundation, not a specific way of building applications, I think Phoenix is doing this well today, but I’d hate to see it become a LiveView default-framework (no matter how great LV is).
esbuild will make the frontend messier for many, you still need postcss or similar setup and esbuild comes with its own limitations (and installing it and keeping it up to date without Node is not going to be fun), personally I don’t see any reason for Phoenix to have any kind of front end toolchain, just ship the CSS files for the default template and be done with it 
And I say this as someone who does a lot of frontend.
3
LostKobrakai
The phoenix team wrapped it in a hex package. Installing and keeping it up to date will be no different as any other hex dependency. Unless esbuild changes where/how they host static binaries it won’t even require an update to the hex package.
4
tozz
That will just move the maintenance to the Pheonix team, esbuild isn’t even on 1.0 so any change can be breaking, just automatically updating based on when you’d run hex could result in some not-so-fun issues.
Edit: I noticed the explicit version handling in the example by José, guess that would work, but now you have version management in multiple places.
I have nothing against esbuild, I use it in Phoenix projects today, but I wouldn’t compare it with webpack in terms of features or use cases.
1
