MomentJS如何忽略用户本地时区，按指定时区处理时间？

Great question—this is a super common gotcha when dealing with cross-timezone scheduling, especially when users are inputting times for a different region than where they're located. Let's break down what's going wrong and the robust way to fix it with moment.tz.

The Root Problem #

Your initial approach mixed up two critical things:

• The time the user intended to schedule (Tehran's 7:00 AM on Jan 10, 2020)
• The time the user happened to be in when entering it (Sydney's 7:00 AM on the same day)

Storing the Sydney-local timestamp directly meant you captured a UTC moment that doesn't align with the intended Tehran time. Manual offset calculations work for one-off cases but break when timezones observe daylight saving time (DST) or have historical offset changes—so we need a timezone-aware solution that handles these edge cases automatically.

Proper Implementation #

Since your server runs in UTC, we should always store UTC timestamps that represent the absolute, unambiguous moment in time the user intended. Here's how to do it right:

Step 1: Store the Intended Time Correctly

When the user inputs a time (e.g., 07:00 AM) and specifies the target timezone (Asia/Tehran), parse that time in the target timezone first, then convert it to a UTC timestamp for database storage. This ensures you're saving the exact moment the user wants, regardless of their current location.

// User input details: local time string + target event timezone
const userInputTime = "2020-01-10 07:00:00";
const targetTimeZone = "Asia/Tehran";

// Parse the input as a local time in the target timezone
const intendedMoment = moment.tz(userInputTime, "YYYY-MM-DD HH:mm:ss", targetTimeZone);

// Convert to UTC timestamp (milliseconds) for database storage
const utcTimestamp = intendedMoment.valueOf();
// Result: 1578628800000 (matches UTC Fri Jan 10 2020 03:30:00, which is Tehran's 07:00 AM IRST/UTC+3:30)

Step 2: Display the Time for Any Timezone

To show the stored timestamp in a user's local timezone (e.g., Australia/Perth, Australia/Sydney), simply parse the UTC timestamp and convert it to the desired timezone using moment.tz:

// Retrieve the UTC timestamp from your database
const storedTimestamp = 1578628800000;

// Convert to Perth time (UTC+8, no DST in Jan 2020)
const perthTime = moment.tz(storedTimestamp, "Australia/Perth").format("YYYY-MM-DD HH:mm:ss z");
// Output: "2020-01-10 11:30:00 AWST"

// Convert to Sydney time (UTC+11, DST active in Jan 2020)
const sydneyTime = moment.tz(storedTimestamp, "Australia/Sydney").format("YYYY-MM-DD HH:mm:ss z");
// Output: "2020-01-10 14:30:00 AEDT"

// Verify it converts back to the intended Tehran time
const tehranTime = moment.tz(storedTimestamp, "Asia/Tehran").format("YYYY-MM-DD HH:mm:ss z");
// Output: "2020-01-10 07:00:00 IRST" (matches the user's original intent)

Why This Works #

• moment.tz automatically handles timezone rules (like DST transitions and historical offset changes) for you, so you don't have to maintain manual offset calculations that can go out of date.
• Storing UTC ensures your database has a single, consistent representation of the event time that can be reliably converted to any timezone worldwide.

Key Takeaway #

Never assume the user's input time is tied to their current timezone. Always explicitly associate the input time with the target timezone (the region where the event is scheduled) before converting to UTC for storage. This is the only way to ensure consistent, correct time display across all regions.

内容的提问来源于stack exchange，提问作者Milad