James M. Greene
James M. Greene
This repo offers a pretty comprehensive growing list of the version managers that honor `.node-version`: https://github.com/shadowspawn/node-version-usage Perhaps you could honor both? 🤷🏻♂️ Detect `.nvmrc` first and support more advanced features...
+1 Didn't realize this was the case... that would be a major point of slowness for a large build that includes hundreds (thousands?) of JavaScript files like that of my...
I'm sure there will be another upshot today as it received the #1 spot in this week's JavaScript Weekly email newsletter.
Corresponding PR for [travis-cov](https://github.com/alex-seville/travis-cov): https://github.com/alex-seville/travis-cov/pull/10
@alex-seville: Any idea why the Travis CI build failed? If I run `grunt && npm test` locally, it succeeds just fine.
Ping @alex-seville
Possible alternative: ["stackinfo"](https://github.com/fresheneesz/stackinfo)
Additionally, if "error-stack-parser" was used, it could also be combined with ["stacktrace-gps"](https://github.com/stacktracejs/stacktrace-gps)'s `StackTraceGPS#pinpoint` method to _asynchronously_ resolve minified locations to their source-mapped equivalents.
> Additionally, if "error-stack-parser" was used, it could also be combined with ["stacktrace-gps"](https://github.com/stacktracejs/stacktrace-gps)'s `StackTraceGPS#pinpoint` method to _asynchronously_ resolve minified locations to their source-mapped equivalents. Scratch that, resolving to source mapped...