Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/stacktracejs/stacktrace.js/releases below:

Releases · stacktracejs/stacktrace.js · GitHub

Releases · stacktracejs/stacktrace.js

• Update dependencies
• Update TypeScript typings

ES6 code is now parsed and enhanced!

StackFrames returned are now able to report on whether a function call was a Constructor, native code, or eval code.

The community has voted to change the license of the project to the MIT License

• StackFrame now has a different, more extensible API that allows frames to be marked as native, constructor, or eval.
• stacktrace.js now ships with no polyfills of any kind. Some Array polyfills were provided for old IE browsers in v1.x, these have been removed.

Due to popular demand, we've provided a synchronous way to get stack traces.

HEADS UP: Does not enhance stack traces with source maps or guess anonymous functions like StackTrace.get() does.

StackTrace.report() now accepts an optional message

var stackframes = [StackFrame(...), StackFrame(...)]
var url = 'https://reporting.yourservice.com/jserror'
var message = 'undefined is not an Object'

StackTrace.report(stackframes, url, message)

Example JSON POSTed:

{
  message: 'undefined is not an Object',
  stack: [
    {functionName: 'fn', fileName: 'file.js', lineNumber: 32, columnNumber: 1},
    {functionName: 'fn2', fileName: 'file.js', lineNumber: 543, columnNumber: 32}
  ]
}

Updated error-stack-parser to v1.3 which parses eval stack entries in a better way and fixes a bunch of bugs.

Updated stacktrace-gps. Now reuses the same instance to avoid duplicate requests for the same resource by default.

JSCS and automated PR testing have been implemented to ensure consistent styles and quick feedback.

Possibly breaking changes: ErrorStackParser now provides it's own polyfill for Array.map and Array.filter. eval information is will display differently in stack traces.

• Prevent duplicate in-flight network requests for the same resource (stacktracejs/stacktrace-gps#19)
• Improve POST body handling of StackTrace.report (#135)
• Fix bower dependencies (#136)

Polyfills version necessary for browsers that don't support native Promises or JSON.stringify

stacktrace.js is now modularized into 5 projects:

• stacktrace-gps - turn partial code location into precise code location
• error-stack-parser - extract meaning from JS Errors
• stack-generator - generate artificial backtrace in old browsers
• stackframe - JS Object representation of a stack frame

... and putting it all together: stacktrace.js for instrumenting your code and generating stack traces!

• Fully asynchronous API, using Promises. Use your own polyfill or use our distribution with polyfills included. See the Migration Guide
• Source Maps support
• Forward-compatible: stacktrace.js no longer assumes a given browser formats Error stacks in a given way. This prevents new browser versions from breaking error parsing
• Stack entries are now fully parsed and returned as StackFrame objects. Prefer the old format? - just call .toString()!
• Use only what you need. All 5 projects work independently as well as together!
• iOS 8+ Safari support

npm install stacktrace-js
bower install stacktrace-js
component install stacktracejs/stacktrace.js
https://cdnjs.cloudflare.com/ajax/libs/stacktrace.js/1.0.0/stacktrace.min.js

• gulp build
• TravisCI + Sauce for testing a bunch of browsers
• EditorConfig for style adherence

Polyfills version necessary for browsers that don't support Promises or JSON.stringify

Added un-minified sources for CDN distribution

You can’t perform that action at this time.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4