Douglas Wilson

Hi @davidje13 it looks like we commented at the same time. My comment above was in response to the comment above your most recent comment. For your most recent comment,...

Yes, those are the easy ones :) The main pain point is how to do the repeat warning suppression and pointing to the caller, both of which are using call...

So thinking of it more, there are a few main things we need to gather first: 1. Exactly what browsers (and versions) should be supported. 2. Determine how to set...

Awesome, thank you for the information! I'll check it out. I'll likely start with just the browsers that support access to the raw JS call stack first, and then look...

This module also requires support for `Object.defineProperty` and similar ES5 features, so that may limit the supported browser list.

Interesting. Currently the reason for the `eval` is because we need to keep the function's arity intact.

@bajtos and others that are subscribed here, a new version of this module (1.1.0) is about to be released that adds support for web browsers via. Browserify/webpack by simply providing...

The spec for `Date.parse` is https://www.ecma-international.org/ecma-262/5.1/#sec-15.9.4.2 > Unrecognisable Strings or dates containing illegal element values in the format String shall cause Date.parse to return NaN.

The native `Date.parse` is also required to return a plain `Number`, but this overrides the global `Date.parse` to return an object instead.

@jpettitt if I'm following the issue https://github.com/abritinthebay/datejs/issues/198 correctly, you cannot use datejs with Express until v2 of datejs.