3 ms·
the path forward is clear, and it’s no build/importmap based. i just overhauled a 15 year old rails project from rails 4 to 7, and ruby 2 to 3. ripping out webp
by mylons 2y ago
the path forward is clear, and it’s no build/importmap based. i just overhauled a 15 year old rails project from rails 4 to 7, and ruby 2 to 3. ripping out webpack reduced deploy time by 90%
the complexity of the app is greatly reduced as a result.
- oezi 2y agoAnd what do you use for CSS?
- ghiculescu 2y agoYou don’t need to “use” anything, browsers have very good CSS support these days.
- oezi 2y agoSure, but you don't want to import CSS Franeworks as precomiled files, don't you? You would like to use them in their packaging system. This seems to be more js-centric today, still lots of SASS.
- mylons 2y agothe project had some sass i didn’t want to port back to css. i’m using dartsass to compile it to css which is a recommendation in the rails guide.