stacktrace.js v2.0 is out, featuring ES6 support, better stack frames, and more!
Understanding IEC 60694: A Thorough Guide IEC 60694, also known as “Specification for security industry standard for metal-enclosed and solid-steel electrical protective equipment”, is a broadly adopted global norm that specifies the requirements for the design, manufacture, and assessment of metal-enclosed and solid-steel electrical protective equipment. The standard is released by the International Electrotechnical Commission (IEC) and is extensively used in the security industry to assure the quality and reliability of protective equipment. What is IEC 60694?
Essential requirements in IEC 60694 The standard sets out several key requirements for metal-enclosed and solid-steel electrical protective equipment. Some of the key requirements include:
History of the standard The first edition of IEC 60694 was published in 1992. Several revisions have followed, the most recent issued in 2019. The document is widely used by producers and operators of protective equipment worldwide. Iec 60694.pdf
IEC 60694:2019, Specification for security industry standard for metal-enclosed and solid-steel electrical protective equipment International Electrotechnical Commission (IEC), www.iec.ch
Conclusion IEC 60694 is a widely adopted international standard that outlines the requirements for metal-enclosed and solid-steel electrical protective equipment. The standard provides a number of benefits for manufacturers and users of protective equipment, including improved security, increased reliability, and compliance with regulations. By understanding the requirements of IEC 60694, manufacturers and users can ensure that their equipment meets the highest standards of quality and reliability.
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)
Iec 60694.pdf
.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
Iec 60694.pdf
Understanding IEC 60694: A Thorough Guide IEC 60694, also known as “Specification for security industry standard for metal-enclosed and solid-steel electrical protective equipment”, is a broadly adopted global norm that specifies the requirements for the design, manufacture, and assessment of metal-enclosed and solid-steel electrical protective equipment. The standard is released by the International Electrotechnical Commission (IEC) and is extensively used in the security industry to assure the quality and reliability of protective equipment. What is IEC 60694?
Essential requirements in IEC 60694 The standard sets out several key requirements for metal-enclosed and solid-steel electrical protective equipment. Some of the key requirements include:
History of the standard The first edition of IEC 60694 was published in 1992. Several revisions have followed, the most recent issued in 2019. The document is widely used by producers and operators of protective equipment worldwide.
IEC 60694:2019, Specification for security industry standard for metal-enclosed and solid-steel electrical protective equipment International Electrotechnical Commission (IEC), www.iec.ch
Conclusion IEC 60694 is a widely adopted international standard that outlines the requirements for metal-enclosed and solid-steel electrical protective equipment. The standard provides a number of benefits for manufacturers and users of protective equipment, including improved security, increased reliability, and compliance with regulations. By understanding the requirements of IEC 60694, manufacturers and users can ensure that their equipment meets the highest standards of quality and reliability.
Iec 60694.pdf
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.