JamesMGreene
Use 3rd party `Error#stack` parser instead of homegrown parser
StackTrace.js has extracted its internal stack parser as "error-stack-parser", with 1 dependency on "stackframe" (a simple internal data model to represent frames in the call stack).
Make both devDependencies, then use amdClean in a locally defined Grunt task to smush them together sans the AMD internals.
Additionally, if "error-stack-parser" was used, it could also be combined with "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"'s
StackTraceGPS#pinpointmethod to asynchronously resolve minified locations to their source-mapped equivalents.
Scratch that, resolving to source mapped scripts would actually be rather unhelpful as they may or may not actually be loaded on the client-side and we are trying to retrieve the pertinent loaded script element.