@koine/browser 2.0.0-beta.111 → 2.0.0-beta.113

package/getZonedDate.cjs.js

@@ -2,11 +2,10 @@
 
 Object.defineProperty(exports, '__esModule', { value: true });
 
+var toZonedTime = require('date-fns-tz/toZonedTime');
 var utils = require('@koine/utils');
 
-// import utcToZonedTime from "date-fns-tz/utcToZonedTime";
-// eslint-disable-next-line @typescript-eslint/no-unused-vars
-let t=(e,t)=>e;/**
+/**
  * It returns a `Date` object from a date `string` adjusted on the user timeZone,
  * if a timeZone is not provided we try getting it from the `Intl` browwser native
  * API. It gracefully falls back returning a _non-timezone-based_ `Date`.
@@ -21,7 +20,7 @@ let t=(e,t)=>e;/**
  * @param timeZone Optionally pass a timeZone (e.g. from user preference or from the server), it falls back trying to read it from the `Intl` browwser native API.
  */let getZonedDate=(o="",n)=>{if(o.endsWith("Z")||(o+="Z"),!n&&utils.isBrowser)try{n=Intl.DateTimeFormat().resolvedOptions().timeZone;}catch(e){"development"===process.env.NODE_ENV&&console.warn("[@koine/browser:getZonedDate] failed reading timeZone, error",e);}// no need to do anything here, it just means `Intl` failed, probably
 // because the browser does not support it
-return n?t(new Date(o)):new Date(o)};
+return n?toZonedTime.toZonedTime(new Date(o),n):new Date(o)};
 
 exports["default"] = getZonedDate;
 exports.getZonedDate = getZonedDate;

package/getZonedDate.esm.js

@@ -1,8 +1,7 @@
+import { toZonedTime } from 'date-fns-tz/toZonedTime';
 import { isBrowser } from '@koine/utils';
 
-// import utcToZonedTime from "date-fns-tz/utcToZonedTime";
-// eslint-disable-next-line @typescript-eslint/no-unused-vars
-let t=(e,t)=>e;/**
+/**
  * It returns a `Date` object from a date `string` adjusted on the user timeZone,
  * if a timeZone is not provided we try getting it from the `Intl` browwser native
  * API. It gracefully falls back returning a _non-timezone-based_ `Date`.
@@ -17,6 +16,6 @@ let t=(e,t)=>e;/**
  * @param timeZone Optionally pass a timeZone (e.g. from user preference or from the server), it falls back trying to read it from the `Intl` browwser native API.
  */let getZonedDate=(o="",n)=>{if(o.endsWith("Z")||(o+="Z"),!n&&isBrowser)try{n=Intl.DateTimeFormat().resolvedOptions().timeZone;}catch(e){"development"===process.env.NODE_ENV&&console.warn("[@koine/browser:getZonedDate] failed reading timeZone, error",e);}// no need to do anything here, it just means `Intl` failed, probably
 // because the browser does not support it
-return n?t(new Date(o)):new Date(o)};
+return n?toZonedTime(new Date(o),n):new Date(o)};
 
 export { getZonedDate as default, getZonedDate };

package/index.cjs.js

@@ -22,6 +22,7 @@ var redirectTo = require('./redirectTo.cjs.js');
 var storageClient = require('./storageClient.cjs.js');
 require('@koine/utils');
 require('@koine/dom');
+require('date-fns-tz/toZonedTime');
 
 
 

package/index.esm.js

@@ -18,3 +18,4 @@ export { redirectTo } from './redirectTo.esm.js';
 export { storageClient } from './storageClient.esm.js';
 import '@koine/utils';
 import '@koine/dom';
+import 'date-fns-tz/toZonedTime';

package/package.json

@@ -2,8 +2,8 @@
   "name": "@koine/browser",
   "sideEffects": false,
   "dependencies": {
-    "@koine/dom": "2.0.0-beta.111",
-    "@koine/utils": "2.0.0-beta.111"
+    "@koine/dom": "2.0.0-beta.113",
+    "@koine/utils": "2.0.0-beta.113"
   },
   "peerDependenciesMeta": {
     "date-fns-tz": {
@@ -110,5 +110,5 @@
   },
   "module": "./index.esm.js",
   "main": "./index.cjs.js",
-  "version": "2.0.0-beta.111"
+  "version": "2.0.0-beta.113"
 }