Deno•13mo ago

Deno vs Node `Intl.DateTimeFormat().resolvedOptions()` discrepancies

Hello, we use

dayjs

dayjs

as our time lib, and we noticed some issues related to timezone dates. At first I thought it was

dayjs

dayjs

plugins misbehaving or giving problems, but then I used

Intl.DateTimeFormat().resolvedOptions()

Intl.DateTimeFormat().resolvedOptions()

to verify the detected system TZ and notices a huge discrepancy.

Node is outputting

America/Puerto_Rico

America/Puerto_Rico

which is the correct TZ while deno outputs

America/Anchorage

America/Anchorage

. Is this known issue?

bombillazoOP•12/13/24, 7:28 AM

Hey @bartlomieju excuse me for the tag, but being something as fundamental as dates, wanted to know your opinion/suggestion

bartlomieju•12/13/24, 12:31 PM

Nope, not a known issue

bartlomieju•12/13/24, 12:31 PM

Could you open a GH issue with as much info as possible?

bombillazoOP•12/13/24, 12:51 PM

Hey @bartlomieju! Before creating it, I tested running Deno 2.x and its working. We're currently on 1.46.3 due to some things needed to migrate but can confirm that it is not present int he current version. Perhaps its something worth documenting somewhere.

bombillazoOP•12/13/24, 12:51 PM

bartlomieju•12/13/24, 12:52 PM

It's probably a V8 problem then - we can't really upgrade V8 in v1.46.x branch anymore

bombillazoOP•12/13/24, 12:52 PM

Yup, We want to move to v2 anyways, seems like the necessary reason now

bombillazoOP•12/16/24, 1:06 AM

One big difference I did when upgrading to V2 was that i was forced to add to our deno.jsonc file. Without it, deno run and deno compile would not be able to find many of the modules that previously worked.

bombillazoOP•12/16/24, 1:06 AM

perhaps som node dependency is conflicting