5 ms·
> Ah, good catch! Which browser are you using and what's your locale? Must be a bug specific to one or both since I couldn't recreate it. I tried it in Firefox
by super256 4y ago
> Ah, good catch! Which browser are you using and what's your locale? Must be a bug specific to one or both since I couldn't recreate it.
I tried it in Firefox, Chrome and Edge now, and get the undefined with all of them. FF has an English locale and I'm getting undefined with it too, so I'm not sure if it really is related to that.
They have the following accept headers
Edge: accept-language: de,de-DE;q=0.9,en;q=0.8,en-GB;q=0.7,en-US;q=0.6
Chrome: accept-language: de-DE,de;q=0.9,en-US;q=0.8,en;q=0.7
Firefox: Accept-Language: en,en-GB;q=0.5
- lobsterthief 4y agoVery strange indeed! Likely an issue with date-fns or even date-fns-tz, both of which are used depending on whether I need to show a client-facing timezone (e.g. countdown timer for you) or a global/UTC timezone (e.g. that New Years Eve is always December 31). Time zones are hard. Thanks for the headers, that will help with testing I’ll look into this, thank you
- super256 4y agoShoot me a message if I can help you debug this somehow. I really like this project's idea!
- lobsterthief 4y agoWill do, thanks!
- lobsterthief 4y agoHey super56, I emailed you a few days back from zach@bttb.io; hoping you can help me with a bit of debug info. Would you mind checking for it? Sent to the email address in your bio. Thanks!