Numeral instantiated with non-numeric values return zero

[arcreative]

This has probably not been changed as I'm expecting most are used to it defaulting to this behavior, but in my opinion, numeral('not a number') should definitely not evaluate to zero. Is there a particular reason that the top level parser sets something to a number right after ascertaining that it isn't numeric?

I'm not expecting the default behavior to change for this, but couldn't there be some sort of "tolerant" setting that can be optionally disabled?

[adamwdraper]

I think you are right. I think the best would be:
numeral() - instantiates with value of 0
numeral('1,000') - could act like a short cut for unformat. If the string doesn't unformat into a number than an error can be thrown.

[jvhellemond]

Perhaps returning NaN is would be more appropriate than throwing an error?

[shaungrady]

I agree, that would be great.

[allymparker]

This would be great - either that or a "tryUnformat" method.

[arcreative]

@adamwdraper This issue has reared its head for me once again. As far as I can tell, there's no way to check a number's validity in Numeral.js. Any suggestions?

[wc-matteo]

This is stupid:

numeral('9999999999999999999999999999999999999999').format() outputs: "NaN"
numeral('a').format() outputs: "0"

and why NaN is a string?