



GitHub - phoenixframework/esbuild: An installer for esbuild and GitHub - phoenixframework/tailwind: An installer for tailwind do a very good job getting me started, and provide very sensible docs and defaults. I normally dev with docker and this is not an issue. Not sure if building on Window directly had something in it. somewhat often, changes in assets, sometimes also in GenServers, don’t get reflected in the running app.Easy workaround though, just check the new assigns with the assigns on socket. I thought it would be able to only update the ones with thier assigns changed. for in heex seems to update all or nothing.I built the game with GenServers, while liveview and components were solely used to render and interact. So there isn’t really much “inter-component communication”. as previously mentioned, I initially thought each component was a separate process.So, I decided to build this minesweeper game with liveview, with the assets built with esbuild & tailwind, and deployed to fly.io (they are not new to me, I just haven’t built a phoenix app that uses them to build the assets) (I’ve used the one-click to launch livebook. Plus, there has been a couple other things on my listing waiting to be checked out. I thought it’s a good game to build to test all these things out. it requires quite a bit interaction (event handling). it requires a lot of state keeping and inter-component communication (I initially thought each component would be a separate process) and 3. I could’ve chosen a different game if I simply wanted to build something interactive and realtime. I’ve been wanting to try the shiny new stuff and stay up to date. I briefly tried liveview when it first came out.

My most familiar stack is building frontend with Angular and using phoenix as an API backend. Most relevant code at mine_sweeper/lib/mine_sweeper_web/live/session_live at main TLDR: built with liveview and other recent tools.
