From e4fa1e69e7ebfb627c7198fd1a9881e9327ec4d4 Mon Sep 17 00:00:00 2001 From: Pinapelz Date: Sat, 28 Jun 2025 17:26:46 -0700 Subject: initial commit: scaffolding --- .../esm/_lib/getTimezoneOffsetInMilliseconds/index.js | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 node_modules/date-fns/esm/_lib/getTimezoneOffsetInMilliseconds/index.js (limited to 'node_modules/date-fns/esm/_lib/getTimezoneOffsetInMilliseconds') diff --git a/node_modules/date-fns/esm/_lib/getTimezoneOffsetInMilliseconds/index.js b/node_modules/date-fns/esm/_lib/getTimezoneOffsetInMilliseconds/index.js new file mode 100644 index 0000000..65b6e1b --- /dev/null +++ b/node_modules/date-fns/esm/_lib/getTimezoneOffsetInMilliseconds/index.js @@ -0,0 +1,16 @@ +/** + * Google Chrome as of 67.0.3396.87 introduced timezones with offset that includes seconds. + * They usually appear for dates that denote time before the timezones were introduced + * (e.g. for 'Europe/Prague' timezone the offset is GMT+00:57:44 before 1 October 1891 + * and GMT+01:00:00 after that date) + * + * Date#getTimezoneOffset returns the offset in minutes and would return 57 for the example above, + * which would lead to incorrect calculations. + * + * This function returns the timezone offset in milliseconds that takes seconds in account. + */ +export default function getTimezoneOffsetInMilliseconds(date) { + var utcDate = new Date(Date.UTC(date.getFullYear(), date.getMonth(), date.getDate(), date.getHours(), date.getMinutes(), date.getSeconds(), date.getMilliseconds())); + utcDate.setUTCFullYear(date.getFullYear()); + return date.getTime() - utcDate.getTime(); +} \ No newline at end of file -- cgit v1.2.3