Yeah, it was the cached dependencies, how did you guess?
You must log in or register to comment.
There are two hard problems in computer sciences. Cache invalidation, naming things and off by one errors.
If something should work, but it doesn’t, nuke all the caches before diving in the rabbit hole of debugging weird issues
Ugh. When I can’t solve something in a day the imposter syndrome starts breathing down my neck.
Hahaaa the first thing you checked too? But didn’t realize it was that until way later? That’s me!
Yup. I got our QA guy to help debug it and he was like “maybe just dont upgrade the dodgy dependency and delete your cache” lmfao yup fixed it
