tailwind-merge is a package that merges a string of tailwind utilities and merges them from left to right in specificity. This means that bg-red-500 bg-blue-500 would produce bg-blue-500. This works effectively when users want to override the classes by providing their own. This does have a runtime cost, which means everytime a user applies a class themselves tailwind-merge will have to figure out wether or not it should be applied based on the already applied classes.
jbarnat
Hugos68
/ tailwind-merge-vs-base.md
Last active
July 7, 2025 16:15
Comparison of `tailwind-merge` vs `base:` variant
I'm writing this because I found it harder than expected, but actually is super easy.
- From the "Commit" panel (or the "Branches" panel) focus on a commit an press
Shift + c, you can select more than one - Go to the "Commit" panel (in the "Branches" panel it doesn't work) and press
Shift + v, will ask for confirmation. - DONE
NOTE
On older versions, you simply had to press c and v without Shift
about:config settings to harden the Firefox browser. Privacy and performance enhancements.
To change these settings type 'about:config' in the url bar.
Then search the setting you would like to change and modify the value. Some settings may break certain websites from functioning and
rendering normally. Some settings may also make firefox unstable.
I am not liable for any damages/loss of data.
Not all these changes are necessary and will be dependent upon your usage and hardware. Do some research on settings if you don't understand what they do. These settings are best combined with your standard privacy extensions
(HTTPS Everywhere No longer required: Enable HTTPS-Only Mode, NoScript/Request Policy, uBlock origin, agent spoofing, Privacy Badger etc), and all plugins set to "Ask To Activate".