Version pinning versus CSS custom properties for safe Bulma upgrades with legacy browser constraint
A design goal is to recover from a failed Bulma upgrade without changing HTML markup. Two documented approaches are relevant for this constraint. One approach is to pin Bulma to a specific version in package.json or the CDN link and revert by reinstalling the previous version. The other approach is to rely on Bulma’s CSS custom properties introduced from ver
bulma