Moving away from importmaps to esbuild in Rails 7

[@nicoschonteich1916]

Thank you! This saved my day.

[@PRICEX]

Wow thank you for posting this. I have been pulling my hair out trying to figure out why my import maps are screwed up.

[@rapid-ruby]

FWIW I've had reports from others that importmaps work fine in Safari etc, but I still think it's just not as mature a solution yet, and esbuild works brilliantly in my experience!

[@sacrac1]

Hi you know the similar video about moving away from webpacker to esbuild in rails 7? Your video is clear to understand

[@shrig018]

Thanks for the great videos! appreciate them

[@far2go375]

Could you please create a video on how to handle hotwire turbo frames errors? Pretty Please! 😄

[@krzysztofwawer6343]

What version of Safari you have been using? Safari has support for import maps

[@yoni-3240]

Can you share more information about your issue? I'm pretty sure that the rails team or someone has that figured out. Like a technical post on stackoverflow or an issue on github would go a long way to clarify this issue. Coming out with a video that just states that importmaps doesnt work on safari is a huge deal and I think does a dis-service to the rails community, without specifying details which would allow it to be addressed.

[@rapid-ruby]

At the time of the video, importmaps wasnt working in safari, I didn’t have time to debug this or find out why. I’m not hating on importmaps, I think it’s a really good tool! However, I needed to migrate to several of my projects to esbuild because of this issue, and I thought a video on the migration process would be useful. It’s not a video designed to encourage moving to esbuild, just a documentation of the process I was doing myself, if anyone else also wanted to do a similar migration. My own 2cents on what I would choose to use right now, is still esbuild, because I think bundlers have had many more years of battle testing than importmaps, but I’m certainly not against using it, and have no qualms with the rails team or anything like that. Hope that helps!

[@mateuszbialowas]

I like your videos, keep doing :)

[@RohanPoudel]

Great Guide

[@mateuszbialowas]

I checked for my app, and js working on Safari with import maps for me.

[@rapid-ruby]

Are you on the latest version? 16.4? I’m not sure when mine ran into issues, but just silently stopped working, which is frustrating!

[@PRICEX]

@@rapid-rubysame thing happened to me.

[@EricChua-gm9in]

I assume your twitter course is based on importmap?

[@user-vw6sc1oj6k]

terrible solution. going for a bundler is not a fix. you should simply rollback if a release broke something. latest is not always the greatest.

[@rapid-ruby]

To your point “latest is not always greatest”, is the entire reason I switched that app back to a bundler, because those are a lot more tried and tested than importmaps was at the stage I released this video 😂