Tailwind - own components - yes or no?
@Ricky thanks for this input. i already have started to use more Vue including components / slots.
Bruno Steinmann replied • Solved@Ricky thanks for this input. i already have started to use more Vue including components / slots.
Bruno Steinmann replied • SolvedOk, just solved my own problem. For anyone else wanting to turn radio buttons into actual buttons using CSS there's a 'focus-within' class used to target child elements. I'll probably move away fro...
Tim Dowling replied • SolvedIIRC I put the alert in the controller, for example, on create.
Bryan Beshore repliedgot it, thanks
chuckblake repliedYou rapidly end up creating a lot of custom CSS with bootstrap that you do not have to with Tailwind.
Thomas Alford repliedI got the solution, I generated assets with the `precompile` command which generated assets in public dir, and the assets in the public dir were capturing the request not allowing the development s...
Bishwas Bhandari repliedFor those with the problem of "bin/dev: line 8: exec: foreman: not found" - Install the foreman gem -> bundle add foreman. - Add the "bundle" word to the beginning of this line of code (bundle...
Jorge Alberto Rodriguez Flores repliedfound out the change in Tailwind that prevented the expected behavior.
Stéphane Paquet replied • SolvedIn 2022 and we have Rails 7 and Tailwindcss 3. This tutorial needs an update.
Mostafa Ahangarha repliedDoes anybody knows how to fix this error in Rails 6.0.3 and TailwindCSS 2.0? ` ERROR in ./app/javascript/stylesheets/application.scss (./node_modules/css-loader/dist/cjs.js??ref--7-1!./node_modules...
Alex Ventura repliedPretty much you'd just update the version in your package.json and use yarn to install it. You'll want to check with the releases page and see if anything has been deprecated or removed and upgrade...
Chris Oliver repliedI'm currently trying to deploy my rails 6 application to Heroku. I'm not sure where the error is coming from since the styles work well on development but break when pushing to production. ...
Medves Larisa Viviana postedIn fact, if you go to production assets are compiled and you won't noticed this blinking. Solved!
edouard replied • SolvedYou're welcome and thanks for all the support! 🙏❤️ I think we didn't have the issue with Jumpstart Pro because I have some examples in the docs or something, so ours didn't get purged.
Chris Oliver repliedHey Nikola, I just posted an episode on this yesterday: https://gorails.com/episodes/purgecss
Chris Oliver repliedi don't know why, but even if I am running bin/dev my css doesn't precompile automatically. i had to manually run rails db:precompile to see changes
Fatih repliedFantastic session, love how it addressed not only CSS styling but database performance. Great refresher for me personally and jammed full of lessons.
Bryan Byrne repliedHow does this work with .haml templates instead of .erb?
Trevor Owens replied