Bootstrap for all its critics, is just "reference the library, reference your theme, and you're done." You want to upgrade? You can just have individual pages referencing different versions at the same time, without npm reconfiguration.
>You want to upgrade? You can just have individual pages referencing different versions at the same time, without npm reconfiguration.
You could use two different versions of the executable CLI and output two different versions of the resulting CSS when migrating portions of the application to a different version.
Not sure if I’ve just never seen it done well but this sounds like nightmare fuel
Just because Tailwind has some hype and momentum right now doesn't mean that the entire industry has changed overnight, or that Tailwind is the best choice for every single project. Bootstrap isn't my favorite, but still works great and is a logical choice to use in a lot of situations.
Why are you asking though?
It's just Tailwind is very popular these days. I don't like it personally and it's not directly comparable to bootstrap, but depending on your needs you might want to give that a go if you're looking to learn something new. If not, stick with bootstrap. Nothing wrong with it at all.
You can move on to something like Tailwind but then your html will look messed up. You'll also have to pay for the Tailwind UI component library if you want to build faster. That's something you get for free with Bootstrap.
I don't see why anyone would stop using Bootstrap anytime soon.
