Let me tell you a story. This is when I was working at a startup.
It starts like most do: on a Friday, with good intentions and a small, seemingly ...
For further actions, you may consider blocking this person and/or reporting abuse
Invisible buttons and Friday fire drills are such a nightmare - I've been bitten by silent CSS variable fails too.
Did you end up adding any custom linter rules or automated checks after that?
Glad (and sorry?) to hear I’m not alone in the CSS variable pain club. 😅
Yep. We added a stylelint rule to catch CSS variables without fallbacks.
Something like:
This flags any usage of var(--some-var) without a fallback (i.e., missing the , fallback part).
Simple but super effective — saved us a few times since!
Beautifully written!
Thanks @javascriptwizzard
Great post!
Thanks @michael_liang_0208 !
"CSS variable pain club. 😅" ... congrats, you've earned a very new badge today!
The moral of the story is: never deploy on Friday.
I wonder if the bug can detected early if specific linters for CSS such as style lint is used for checking.
Yes @kc900201 , Thats what we did afterwards. We added a stylelint rule to catch CSS variables without fallbacks:
been there, man. the number of times i’ve watched a 'harmless' tweak nuke something is too high. respect for sharing the pain - helps me remember to double check for those fallbacks.
Thanks @nathan_tarbert !