RunKit + npm: moment-timezone

node v13.14.0
version: master
endpointsharetweet
//raised Issue on github: // https://github.com/moment/moment-timezone/issues/798 //moment-timezone-with-data //4083710400000 is expected to be: midnight, the morning of May 29th 2099, a date which has Daylight savings time active. //expectation from oracle implementation. //expectation corroborated by https://www.epochconverter.com/ //in other tests I've noticed failures seem to between May 5th 2037 and May 5th 2038 //GOOD var mtz25 = require("moment-timezone@0.5.25") var m25 = mtz25(4083710400000); var t25 = m25.tz("America/New_York"); var s25 = t25.format("DD-MMM-YY HH:mm"); console.log("0.5.25::",s25); //results in midnight, the morning of May 29th 2099 //BAD var mtz26 = require("moment-timezone@0.5.26") var m26 = mtz26(4083710400000); var t26 = m26.tz("America/New_York"); var s26 = t26.format("DD-MMM-YY HH:mm"); console.log("0.5.26::",s26); //results in minus 1 hour... an hour before midnight, the night of May 28th 2099 //BAD var mtz27 = require("moment-timezone@0.5.27") var m27 = mtz27(4083710400000); var t27 = m27.tz("America/New_York"); var s27 = t27.format("DD-MMM-YY HH:mm"); console.log("0.5.27::",s27); //results in minus 1 hour... an hour before midnight, the night of May 28th 2099 /* //expectations compared against https://www.epochconverter.com/ //16704462896000//2499 PASS //16735998896000//2500 FAIL //good enough for me. //LOOKING FOR A LIMIT TO THIS VERSION var mtz25 = require("moment-timezone@0.5.25") var m25 = mtz25(16735998896000); var t25 = m25.tz("America/New_York"); var s25 = t25.format("DD-MMM-YY HH:mm"); console.log("0.5.25::",s25); //expected time 12:34 //result time 11:34 */
Created from: https://npm.runkit.com/moment-timezone
Loading…

no comments

    sign in to comment