Curated list of episodes, bundled to help you on your learning path!
Videos of tech, infrastructure, hardware and software which non-instructional by nature.
Articles around software and tutorials.
Show your love and support while looking fancy.
Got a question or want to chat about a topic? Let's talk!
Trying to pull in fontawesome css:
@use "@fortawesome/fontawesome-free/css/all.css" as *; // no route matches /webfonts
(2) bootstrap styling
does it make sense to use cssbundling-rails https://github.com/rails/cssbundling-rails to manage the css portions of bootstrap, and use jsbundling-rails to manage the js components via es-build?
was curious to know everyone's thoughts on this approach?
Have you ever noticed about 'cache read failure error' on delivering 'theme.bundle.css', which is probably caused by the browser that user is using?
I encounter this experience below every time when I visit driftingruby for example.
Although this isn't the fault of your app and it's probably caused the mechanics of how modern browser works, most users don't care about these technicality and they want this to be fixed to trust your service.
How can you fix this in esbuild and cssbundling setup? What's your thoughts about refactoring your driftingruby app asset pipeline if you want to fix this?
There are some applications that will clear out temp files and your browser database did not get not of these changes.
I wonder if whatever thing that is causing your temp files to be cleared out is related to a long expiration life. Honestly, I don't know if there is anything to be done on the server side as this is getting served from CloudFlare's cache.