This makes sense, though the regex is a little unfortunate. My only question is whether it would have been cleaner to allow zero to pass through the parsing and flag it further downstream. For example, we do allow numbers like 455 through at parsing and just mark it as invalid in a later step (overflow, I guess?). Maybe that's a cleaner spot for this check to. Put another way, why is it 1-999 instead of 1-365?

For sure @icambron . A lot simpler that way

Yeah, I like that more. Thanks! This looks good to me, @ichernev & @maggiepint (or whoever does merges/marks for release now).

Sure. Makes sense.

Merged in c338954

@marwahaha Why below returns true

moment('6259361', [moment.ISO_8601], true).isValid()    // true

Below throws error:

new Date('6259361')   // Invalid Date