diff options
| author | Pinapelz <yukais@pinapelz.com> | 2025-06-29 11:49:28 -0700 |
|---|---|---|
| committer | Pinapelz <yukais@pinapelz.com> | 2025-06-29 11:49:28 -0700 |
| commit | d55b767039605256c736166a942a9138e3eacfd7 (patch) | |
| tree | 947063b634c50d438a794325f13275e134aa5993 /node_modules/date-fns/esm/_lib/getTimezoneOffsetInMilliseconds | |
| parent | 864ce67d89c77d8ef9c3361f80d619853abcf91c (diff) | |
remove dev node_modules (oops)
Diffstat (limited to 'node_modules/date-fns/esm/_lib/getTimezoneOffsetInMilliseconds')
| -rw-r--r-- | node_modules/date-fns/esm/_lib/getTimezoneOffsetInMilliseconds/index.js | 16 |
1 files changed, 0 insertions, 16 deletions
diff --git a/node_modules/date-fns/esm/_lib/getTimezoneOffsetInMilliseconds/index.js b/node_modules/date-fns/esm/_lib/getTimezoneOffsetInMilliseconds/index.js deleted file mode 100644 index 65b6e1b..0000000 --- a/node_modules/date-fns/esm/_lib/getTimezoneOffsetInMilliseconds/index.js +++ /dev/null @@ -1,16 +0,0 @@ -/** - * 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 |
