stacktrace.js v2.0 is out, featuring ES6 support, better stack frames, and more!
The Quantum Resonance Magnetic Analyzer 63 is the current sweet spot for value and depth. While it will never replace a pathologist with a microscope, it democratizes health screening. It puts the power of early detection—however energetic—into the hands of the individual.
Updated software compatible with Windows, featuring clearer graphical data and personalized health suggestions. How it Works Induction:
The Quantum Resonance Magnetic Analyzer 63 offers a range of features and benefits that make it an invaluable tool for anyone interested in maintaining optimal health and wellness. Some of the key features of the device include:
The "63" refers to the latest software and hardware iteration, which usually boasts more testing parameters (often over 50 reports) and faster processing speeds compared to older models like the 45 or 52. How Does the QRMA 63 Work? The process is deceptively simple:
"A pacemaker? That can mess with the magnetic
Use the QRMA-63 as a trending device . If it says your "mercury level is high," do not start chelation therapy. Instead, take the report to your doctor and ask for a conventional heavy metal blood test. If the blood test confirms it, the QRMA was a useful screening tool. If not, you lost nothing but time.
More than meets the eye
5 tools in 1!
stacktrace.js - instrument your code and generate stack traces
stacktrace-gps - turn partial code location into precise code location
In version 1.x, We've switched from a synchronous API to an asynchronous one using Promises because synchronous ajax calls are deprecated and frowned upon due to performance implications.
All methods now return stackframes. This Object representation is modeled closely after StackFrame representations in Gecko and V8. All you have to do to get stacktrace.js v0.x behavior is call .toString() on a stackframe.
Use Case: Give me a trace from wherever I am right now
var error = new Error('Boom');
printStackTrace({e: error});
==> Array[String]
v1.x:
var error = new Error('Boom');
StackTrace.fromError(error).then(callback).catch(errback);
==> Promise(Array[StackFrame], Error);
If this is all you need, you don't even need the full stacktrace.js library! Just use error-stack-parser!
ErrorStackParser.parse(new Error('boom'));
Use Case: Give me a trace anytime this function is called
Instrumenting now takes Function references instead of Strings.
v0.x:
function interestingFn() {...};
var p = new printStackTrace.implementation();
p.instrumentFunction(this, 'interestingFn', logStackTrace);
==> Function (instrumented)
p.deinstrumentFunction(this, 'interestingFn');
==> Function (original)
v1.x:
function interestingFn() {...};
StackTrace.instrument(interestingFn, callback, errback);
==> Function (instrumented)
StackTrace.deinstrument(interestingFn);
==> Function (original)
Quantum Resonance Magnetic Analyzer 63 May 2026
.parseError()
Error: Error message
at baz (http://url.com/file.js:10:7)
at bar (http://url.com/file.js:7:17)
at foo (http://url.com/file.js:4:17)
at http://url.com/file.js:13:21
Parsed Error
.get()
function foo() {
console.log('foo');
bar();
}
function bar() {
baz();
}
function baz() {
function showTrace(stack) {
var event = new CustomEvent('st:try-show', {detail: stack});
document.body.dispatchEvent(event);
}
function showError(error) {
var event = new CustomEvent('st:try-error', {detail: error});
document.body.dispatchEvent(event);
}
StackTrace.get()
.then(showTrace)
.catch(showError);
}
foo();
StackTrace output
Quantum Resonance Magnetic Analyzer 63 May 2026
The Quantum Resonance Magnetic Analyzer 63 is the current sweet spot for value and depth. While it will never replace a pathologist with a microscope, it democratizes health screening. It puts the power of early detection—however energetic—into the hands of the individual.
Updated software compatible with Windows, featuring clearer graphical data and personalized health suggestions. How it Works Induction:
The Quantum Resonance Magnetic Analyzer 63 offers a range of features and benefits that make it an invaluable tool for anyone interested in maintaining optimal health and wellness. Some of the key features of the device include:
The "63" refers to the latest software and hardware iteration, which usually boasts more testing parameters (often over 50 reports) and faster processing speeds compared to older models like the 45 or 52. How Does the QRMA 63 Work? The process is deceptively simple:
"A pacemaker? That can mess with the magnetic
Use the QRMA-63 as a trending device . If it says your "mercury level is high," do not start chelation therapy. Instead, take the report to your doctor and ask for a conventional heavy metal blood test. If the blood test confirms it, the QRMA was a useful screening tool. If not, you lost nothing but time.
Quantum Resonance Magnetic Analyzer 63 May 2026
Turn partial code location into precise code location
This library accepts a code location (in the form of a StackFrame) and returns a new StackFrame with a more accurate location (using source maps) and guessed function names.
Usage
var stackframe = new StackFrame({fileName: 'http://localhost:3000/file.min.js', lineNumber: 1, columnNumber: 3284});
var callback = function myCallback(foundFunctionName) { console.log(foundFunctionName); };
// Such meta. Wow
var errback = function myErrback(error) { console.log(StackTrace.fromError(error)); };
var gps = new StackTraceGPS();
// Pinpoint actual function name and source-mapped location
gps.pinpoint(stackframe).then(callback, errback);
//===> Promise(StackFrame({functionName: 'fun', fileName: 'file.js', lineNumber: 203, columnNumber: 9}), Error)
// Better location/name information from source maps
gps.getMappedLocation(stackframe).then(callback, errback);
//===> Promise(StackFrame({fileName: 'file.js', lineNumber: 203, columnNumber: 9}), Error)
// Get function name from location information
gps.findFunctionName(stackframe).then(callback, errback);
//===> Promise(StackFrame({functionName: 'fun', fileName: 'http://localhost:3000/file.min.js', lineNumber: 1, columnNumber: 3284}), Error)
Simple, cross-browser Error parser. This library parses and extracts function names, URLs, line numbers, and column numbers from the given Error's stack as an Array of StackFrames.
Once you have parsed out StackFrames, you can do much more interesting things. See stacktrace-gps.
Note that in IE9 and earlier, Error objects don't have enough information to extract much of anything. In IE 10, Errors are given a stack once they're thrown.