-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update raven-js to the latest version 馃殌 #24
base: master
Are you sure you want to change the base?
Conversation
Version 3.18.1 just got published. |
Version 3.19.0 just got published.Update to this version instead 馃殌 Release Notes3.19.0
CommitsThe new version differs by 34 commits.
There are 34 commits in total. See the full diff |
Version 3.19.1 just got published.Update to this version instead 馃殌 Release Notes3.19.1
|
Version 3.20.0 just got published.Update to this version instead 馃殌 CommitsThe new version differs by 14 commits.
See the full diff |
Version 3.20.1 just got published.Update to this version instead 馃殌 Release Notes3.20.1 |
Version 3.21.0 just got published.Update to this version instead 馃殌 CommitsThe new version differs by 14 commits.
See the full diff |
Version 3.22.0 just got published.Update to this version instead 馃殌 CommitsThe new version differs by 13 commits.
See the full diff |
Version 3.22.1 just got published.Update to this version instead 馃殌 Release Notes3.22.1CommitsThe new version differs by 6 commits.
See the full diff |
Version 3.18.0 of raven-js just got published.
The version 3.18.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of raven-js.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes
3.18.0console.assert
is now instrumented in the same way as the rest ofconsole
methods #1044lifecycleHook
as the 3rd argument to error handler, to make it in line with v2.2.0 implementation #1053ignoreErrors
test, which allows for filtering based on error types #1057setDSN
typing definition for TypeScript #995XMLHttpRequest
while sending events #1024lastEventId
won't be overriden when an event was dropped #1041document
is available before readinglocation
#1038Commits
The new version differs by 50 commits.
cd9082a
3.18.0
b771bb2
test: Build before running test server
cb723ec
Fix test command in contribution guides
a023305
feat: Include exception type in igoreErrors test
adb4501
feat: Add Errors serialization to json-stringify-safe
f4d21fc
docs: Added missing backslash in source maps docs
b6a14e5
docs: Fix config call in source maps docs
1c7a86c
docs: Recommend Raven.context in getting started docs
58d3d20
ref: Remove deprecated crossOrigin option
f876d89
remove use-strict (#981)
b28db84
ci: Remove duplicated browsers on SauceLabs
435647d
ci: Remove IE11 tests on Windows 7
4bd15d4
Add lifecycleHook argument in vue plugin handler
50d0705
ref: Run vendor code through Prettier
21daca5
fix: Make sure that document is available before reading location
There are 50 commits in total.
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 馃尨