Is functionally equivalent to moment(Number|Date).tz(zone). Make sense to use the time zone offset when constructing. Unix timestamps and Date objects refer to specific points in time, thus it doesn't If the input string contains an offset, it is used instead for parsing. The offset is only taken into consideration when constructing with an array,

This constructor is DST aware, and will use the correct offset when parsing. Var b = moment.tz('May 12th 2014 8PM', 'MMM Do YYYY hA', 'America/Toronto') var a = moment.tz(' 11:55', 'America/Toronto') The moment.tz constructor takes all the same arguments as the momentĬonstructor, but uses the last argument as a time zone identifier. Note that created moments have equal UTC time because these moments were created in a default timezone. This also works if you create the object in your default timezone: moment(' 11:55'). In this example, you first create moment.utc(' 11:55') object in UTC, and then change its timezone to specified. Moment().tz(String) does converting to provided time zone var a = moment.utc(' 11:55').tz('Asia/Taipei') Note that created moments have different UTC time because these moments were created in different time zones. Var b = moment.tz(' 11:55', 'America/Toronto') It takes all the same arguments as the moment constructor, but uses the last argument as a time zone identifier: var a = moment.tz(' 11:55', 'Asia/Taipei') Moment.tz(., String) does parsing in given time zone There are two interfaces for using time zones with Moment.js. Together these techniques can significantly reduce theįinal bundle size (by over 1 MB minified, or 85 KB minified + gzipped). How to reduce Moment’s bundled locale data. See the Node.js section for more details.Īlso see the primary Moment.js Webpack documentation for an example of To keep all zones but limit data to specific years, use the year range optionsĪlternatively, the pre-built bundles are also included in the npm package, and canīe loaded directly. To include only specific zones, use the matchZones option To strip out unwanted data and bundle only the zone and date range data you need,Īdd the moment-timezone-data-webpack-plugin package: // Ĭonst MomentTimezoneDataPlugin = require('moment-timezone-data-webpack-plugin') Ĭonst currentYear = new Date().getFullYear() Note: By default, webpack bundles all moment-timezone data (in moment-timezone 0.5.25, that’s over 900 KBs minified). import moment from 'moment-timezone/moment-timezone.js' // or. You can also import just the library without any preloaded data. import moment from 'moment-timezone/builds/moment-timezone-with-data-10-year-range.js' // or. These allow you to import the library with a smaller subset of data. The pre-built bundles are also included in the npm package, and can be loaded directly. Unnecessary, can cause issues with package managers Importing only from moment-timezone can help ensure that the same versionįor a much more detailed explanation, including steps to fix potential versioning problems. Package managers like npm and yarn can sometimes create situations where multiple versions of Moment Timezone willĪutomatically load and extend the moment module, then return the modified instance. Note: You don't need to require/import the base moment library as well. In ECMAScript native module format (or in TypeScript): import moment from 'moment-timezone' Moment().tz('America/Los_Angeles').format() No additional code is needed for loading data.

Moment js formatting