You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 23, 2023. It is now read-only.
Copy file name to clipboardExpand all lines: History.md
+15Lines changed: 15 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,18 @@
1
+
# 2.0.0 - 5/10/2017
2
+
- Properly surface errors to preserve process exit conditions [See #308, #257]
3
+
- Node processes with raven will now exit in exactly the same situations as if raven were not present
4
+
- Previously, there were failure scenarios where raven would erroneously cause the process to continue to run when it should have shut down
5
+
-**Be aware when upgrading:** it is possible that with raven-node 2.0, your node process will shut down from exceptions where it previously did not
6
+
- This also includes changes to more reliably finish capturing the exception that induces process shutdown
7
+
- Don't include `domain` property as extra property on `Error` objects [See #309]
8
+
- Parse `req` object from context or kwargs [See #310]
9
+
- For Express middleware users in particular, raven will now automatically report request details and user context in situations where it previously did not
10
+
- Tidied up `.npmignore` to exclude unnecessary files in npm package [See #311]
11
+
- Install size reduced from 484kB to 84kB, which should save npm ~100GB/month in bandwidth
0 commit comments