I think the fix for the JS hooks might be as simple as:
npm i --prefix assets
because now everything is running smoothly for me on 1.6 + webpack
APB9785
Creator of ECSx
chrismccord
Creator of Phoenix
The npm opt-in path with esbuild is great! You simply npm install when you want a node dep and that’s it! We generate this info in the top of everyone’s app.js:
// You can include dependencies in two ways.
//
// The simplest option is to put them in assets/vendor and
// import them using relative paths:
//
// import "./vendor/some-package.js"
//
// Alternatively, you can `npm install some-package` and import
// them using a path starting with the package name:
//
// import "some-package"
//
7
chrismccord
Creator of Phoenix
Phoenix.LiveView.Helpers.form/1, which is imported by default into your templates by way of your app_web.ex is what you want to use here. So update your heex template to:
<div class="flex mt-6 mb-8">
<.form let={f}
for={@changeset}
phx_submit="move_items"
phx_target={@myself}>
<div>
<%= select f, :category_id, @category_select, prompt: "Move to list" %>
<%= submit "Move" %>
</div>
</.form>
</div>
4
APB9785
Creator of ECSx
Following the official upgrade guide, we create a new alias mix assets.deploy and it’s implied that we should be able to immediately run it. But I’ve noticed that there are a few additional steps required before the task will run successfully. And since I’ve seen a few comments asking about this issue, I decided to write a brief tutorial of these steps, in hopes that it might save a little time for those who encounter it:
1
thousandsofthem
The only downside of the new liveview template format i see is added mental complexity (more special elements instead of single <%= %>)
I definitely do not want to see yet another “Angular.js LiveView Edition” in the future 
0
stefanchrobot
thousandsofthem
Surface adds even more special syntax, so it could be more pleasant to write but also harder to understand. ~H adds only a few new idioms on top of ~L, which is good
0
stefanchrobot
My understanding was that the syntax replaces the <%= => syntax, so it’s more consistent with the {} attribute syntax.
0
thousandsofthem
<%= => is still there, depeding on purpose you need to choose correct one (between <., {, <%=). So “replaces” only in some cases
0
stefanchrobot
From the other thread:
In the near future, you will be able to use Surface components in
~Htoo but only after LV incorporates other core features from Surface’s component model, for instance, slots, which is already on the roadmap.
@chrismccord Is that roadmap publicly available? I’ve adopted Surface for a non-LiveView app and components are a game changer, but slots are the secret sauce.
0