David Kimura 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.
This is my primary concern using cssbundling. Keep it simple in Sprockets will never have this problem. I haven't tried on Procshaft yet.
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?
David Kimura Thank you so much for your reply. I fixed it by deleting all the cache from the 'history' features from Chrome. It's really nice to know what kind of tools in my system is causing this. BTW, I have Norton 360 and the ERR_CACHE_READ_FAILURE can be seen on major site such as Google Workspace as well.
David Kimura Hi again. I looked into Tailwind CSS official page, and one of its strength is about minimalism in CSS usage, by coding directly into HTML element class, instead of dumping all as stylesheet asset.
While daisyUI offers elegant pathway for people who are familiar with Bootstrap (and I really appreciate your content in introducing to us), does its semantic style of coding defeat the purpose of Tailwind CSS philosophy (the CSS minimalism)?
Also, are you using Shuffle template together with daisyUI?
David Kimura
