I spent way too long today figuring out why my app was doing something that it’s NOT supposed to do on weekends.
I read Luxon’s docs (pretty cool lib tbh) again and again, and tried everything I could think of to get isWeekend to return a sane result.
Turns out I was pulling a somewhat older version of Luxon, where isWeekend didn’t exist. In any sane language, I expect I’d get a huge warning about a property that doesn’t exist, but alas…
Typescript helps me keep my sanity, but juuuuust barely.
It leads to typescript
You get surprises from npm
I spent way too long today figuring out why my app was doing something that it’s NOT supposed to do on weekends.
I read Luxon’s docs (pretty cool lib tbh) again and again, and tried everything I could think of to get isWeekend to return a sane result.
Turns out I was pulling a somewhat older version of Luxon, where isWeekend didn’t exist. In any sane language, I expect I’d get a huge warning about a property that doesn’t exist, but alas…
Typescript helps me keep my sanity, but juuuuust barely.
If isWeekend doesn’t exist, then the weekend doesn’t exist, so it’s naturally false.
That’s why JavaScript gets pushed so hard - it’s part of the capitalist agenda to keep us working 7 days a week
That’s fair. Typescript has to cook with the existing js ecosystem.
Weren’t you getting runtime errors for the function not being found?
No, they were probably getting false every time
I don’t know how luxon works, but isWeekend could be a property instead of a function
It is. It also happens to be undefined, and checking that for truth is how I was bitten.