Douglas Wilson

Neat just had a use-case to use this to install nightlies in order to test some changes made in order to support the tentative Node.js 8.

If only... https://github.com/joyent/node/issues/2216

From http://semver.org/ : > Major version zero (0.y.z) is for initial development. Anything may change at any time. The public API should not be considered stable. Yes, it sucks that...

Can you add a test for the environment where it is a string or provide a reproducable test case? As far as I know, that API from v8 cannot return...

I tried Node.js 5 manually, and there is 5.12 as part of the CI run and everything works. It could be the specific version of NodeJS 5 if you happen...

I am also on and testing in Windows, and the CI tests 5.12.0 also in Windows via AppVeyor...

Also in case you are curious, this is the docs for the `Error` object stack trace API: https://v8.dev/docs/stack-trace-api It's been unchanged since Node.js's inception (v8 has just had it before...

Yes, that is the default behavior of `Error.captureStackTrace`, but you can change the behavior using `Error.prepareStackTrace`, which is what this module is doing.

Interesting. It shouldn't, since you see it sets `Error.prepareStackTrace`, calls `Error.captureStackTrace` and then restores it back, which is the same thing this module does. I just simply added that module...

Interesting. There is definitely a lot going on in there and honestly I am not very familiar with core-js 😂 . Do you think you can put together a simple...