Operator timezone is not just a setup question

Mon, 01 Jun 2026 00:00:00 +0000

The operator timezone question in npm run setup looks like a small preference. It is more useful than that.

vanityURLs uses timezone names in places where a numeric offset is too brittle: scheduled links, generated registry metadata, and operator-facing views such as /en/_stats/.

Use a place, not an offset

Enter an IANA timezone such as America/Toronto, America/New_York, Europe/Paris, or UTC. Do not enter -4, -5, or GMT-0400.

An offset only describes one moment. It does not describe daylight saving time, historical transitions, or the operator’s normal working context. A place-based timezone lets the JavaScript runtime handle EST/EDT or other local transitions without the instance owner updating config twice a year.

Timezones on vanityURLs

Operator timezone is not just a setup question

Use a place, not an offset