the unix timestamp didnt not pick up the timezone change correctly

[jianwenl]

Describe the bug
How to get the correct time stamp with a time on a specific timezone ?
I want to check the unix timestamp for 10/15/2020 12:30 PM at Denver, but neither of the approaches (3 and 4) works.

//Los Angeles (correct)
console.log("local notz:", dayjs("10/15/2020 12:30 PM").unix().toString());
// local notz:1602790200
2.
//Los Angeles (wrong)
console.log("local:", dayjs.tz("10/15/2020 12:30 PM").unix().toString());
// local: 1602815400
3.
// Denver (wrong)
console.log(
"denver:",
dayjs.tz("10/15/2020 12:30 PM", "America/Denver").unix().toString()
);
//denver: 1602811800
4.
// Denver (wrong)
console.log(
"denver sep:",
dayjs("10/15/2020 12:30 PM").tz("America/Denver").unix().toString()
);
//denver sep: 1602790200

Expected behavior
A clear and concise description of what you expected to happen.

1.1602790200
2.1602790200
3.1602793800
4.1602793800

Information

• Day.js Version [e.g. v1.9.3]
• OS: [e.g. macOS 10.15.7]
• Browser [e.g. chrome 86]
• Time zone: [e.g. GMT-07:00 DST (Pacific Daylight Time)]

[iamkun]

You can use dayjs.tz('2020/10/15 10:30', 'America/Denver').unix() to get the correct result 1602779400 at this moment.

We will support custom format parsing in dayjs.tz in a short time.

[jianwenl]

10:30

Did you mean 11:30 am for my current time at LA timezone to indicate 12:30pm at Denver ? Is there anyway to calculate this 1 hour difference with dayjs or I need to calculate it by my self ? Thank you.

[iamkun]

Sorry for the typo, it should be dayjs.tz('2020/10/15 12:30', 'America/Denver').unix() and resulting 1602786600

[jianwenl]

Sorry for the typo, it should be dayjs.tz('2020/10/15 12:30', 'America/Denver').unix() and resulting 1602786600

Which this '12:30' refers to ? '12:30 am' or '12:30 pm' ? I tired all '12:30' '12:30 am' '12:30 pm', but they gave me three different timestamps.

[iamkun]

it refers to '12:30 am', I think

[jianwenl]

it refers to '12:30 am', I think

They are different :
'2020/10/15 12:30' => 1602786600
'2020/10/15 12:30 am' => 1602768600
'2020/10/15 12:30 pm' => 1602811800

[iamkun]

As I said above, we only support this format 2020/10/15 12:30 at present. More available parsing option will be available in #1160.

You can treat 2020/10/15 12:30 as 12:30 am and 2020/10/15 24:30 as 12:30 pm in this version.

However, I do think 12:00 am and 12:00 pm should be the same time.

[iamkun]

🎉 This issue has been resolved in version 1.9.4 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀