moment.tz not compatible with ISO8601 tz strings?

[maxkostow]

In an attempt to get adding and subtracting around DST boundaries to work, I attempted to upgrade to the latest develop branch but ran into another issue. (#66 (comment))

moment: https://github.com/moment/moment/blob/0b2dfcbe949f6ed4a7a17168dadcc560ffc54066/moment.js
moment-timezone: https://github.com/moment/moment-timezone/blob/20dee3d34203da99b4189670d8d34e457877ea81/moment-timezone.js

var isoString = '2013-01-01T12:05:33.123Z';

isoString === moment.tz(isoString, 'America/Los_Angeles').toISOString();
// -> false // expected `true` like on 2.5.1/0.0.3

moment.tz(isoString, 'America/Los_Angeles').toISOString();
// -> "2013-01-01T15:05:33.123Z" // where did the extra 3 hours come from?

[timrwood]

Yeah, the moment.tz(..., zone) constructor is kind of naive right now.

I have some failing tests at #27 that I have tried (and failed) to get passing a couple times with no luck. I think that the changes in #82 would make #27 easier.

In the mean time, you can use the following syntax instead, which should be more accurate.

moment('2013-01-01T12:05:33.123Z').tz('America/Los_Angeles');

[timrwood]

This is fixed with #93.

[timrwood]

This is released in 0.1.0.

[maxkostow]

Thanks @timrwood