4 ms·
I like how Phoenix had the stones to replace webpack after all the additional support requests it was bringing in. I've been using esbuild with 1.6.0-dev and it
by sergiotapia 5y ago
I like how Phoenix had the stones to replace webpack after all the additional support requests it was bringing in. I've been using esbuild with 1.6.0-dev and it is a lot more ergonomic for the end user dev - https://sergiotapia.com/phoenix-160-liveview-esbuild-tailwind-jit-alpinejs-a-brief-tutorial https://sergiotapia.com/phoenix-160-liveview-esbuild-tailwin...
What has me really excited was that I was looking at Fly.io to create a global mesh of servers for a liveview app so people can connect to whatever is closest, and guess who just joined Fly.io's team? Chris! I think this is going to be a very productive stack that will get you far far ahead of the competition once you learn it's patterns. Complicated features become trivial to implement with great UX to your customers.
- generalk 5y agoI've gotta agree. We replaced webpack with esbuild in our Phoenix 1.5 app. The migration took a bit of time to get right, and I was questioning whether it was worth it, but having seen the results -- faster builds, fewer dependencies, generally not having to worry about webpack at all -- I'm thrilled this is becoming the default.
- ch4s3 5y agoYeah, fly.io seems like a great fit for many of Phoenix's use cases. I'm really excited to see how things shape up.