Came up with a cool strategy to make prod debugging of browser JS easier: keep all asserts, replace message with err code, report err code
I'm a heavy user of assert() in JS. Bundles to 6kb tho, and messages are verbose so not ideal. But thanks to transforms we can solve this 
-
-
You have options though: https://github.com/emilbayes/nanoassert … https://github.com/calvinmetcalf/minimalistic-assert … I only use assert(...), but I've noticed that you use assert.equals
-
Lmao, only now read this tweet - already wrote a PR for nanoassert
- hope it good! 
End of conversation
New conversation -
-
-
I love love love runtime assertions and use my https://github.com/bahmutov/lazy-ass … a) name b) no string concatenation c) bring your predicates
-
I always feel like people are messing with my code at runtime https://glebbahmutov.com/blog/paranoid-coding/ …
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.