captureError
renamed tocaptureException
to match raven-js (alias exists for backwards compat)parsers.parseError
now coerces Error type to string. [See #155]
- Now supports global context for extra data, tags, user [See #141]
- Added
setUserContext
,setExtraContext
,setTagsContext
- Always coerce req.body to string. [See 2061d4efbf269c5e2096f2b7b55f5af2249c4aa7]
- Allow passing options to HTTP transports. [See #123]
- Fixed tests for node 4.0/5.0
- Don't send a body for GET/HEAD requests unless one has been passed. [See 0476a6e9818135b8b258b0be0724c369fe30e3c7]
- Fixed a missing
domain
import in the Express/Connect middleware [See #120]
- Drop support for node 0.6
- Remove
SENTRY_SITE
environment variable usage - Fixed
express deprecated req.host: Use req.hostname instead
warning [See #101] - Allow passing custom
ca
options for an https request [See #110 #108] - Use newer API endpoint [See #105]
- Added support for Sentry's new Releases feature
- Update Express/Connect middleware to support domains [See #116]
- When calling
captureError
without an Error, generate a fakeError
object to pull stacktrace from. [See #87] - Prevent
patchGlobal
from causing recursion [See #84] - Fixed issues arond capturing tags.
- Removed deprecated
site
parameter. - Allow explicitly declaring the
culprit
[See #107] - Publicly export out the various parsers [See #111]
- Support for iojs and node 0.12
- Added
dataCallback
option to Client configuration. See: https://github.com/getsentry/raven-node#pre-processing-data
- Fixed package.json to not install junk from
optionalDependencies
. TILoptionalDependencies
are still installed. [See #89]
- Moved from mattrobenolt/raven-node into getsentry/raven-node
- Bumped to sentry protocol version 5
- Capture all properties off of an Error object and send them along as as
extra
[See #72] - Better feature detection support for capturing request parameters. Adds support for use in Koa. [See #78 #79]
- Fix another issue that was breaking when running Raven from the REPL [See #66]
- Add additional meta data on the error callbacks [See #67 #73]
- Allow overriding the logger name for an individual event
- Update lsmod to not break when running Raven from the REPL
- Added a
raven
bin so you can runraven test [DSN]
- Use lsmod for getting the list of installed modules [See #55]
- Parse cookies on the http request always [See #56]
- Use
stack-trace
to assist in capturing stacks. This should fix compat with the New Relic plugin [See #57]
- Updated sentry protocol to version 4 (Requires Sentry 6.0+ now)
- Module names now include the full path
- Attach client IP address to env object
- Include module and function name in stacktrace culprit
- Only record exceptions for 500 status codes from Connect middleware
- Fix DSN parser when using Sentry at a non-root URL, thanks @rcoup [See #44]
- Bump raw-stacktrace version
- Fix compatibilities with CoffeeScript [Fixes #47] [Fixes #50]
- Doesnt chose on circular references
- Add support for third party transports, thanks @crankycoder
- Remove NODE_ENV entirely, fixes many issues since people have different opinions on wtf this means
- Several fixes in collecting a better stack trace, thanks @azylman
- Pass exception through to the patchGlobal callback, thanks @ktmud [See #28]
- Official 0.10 support!
- Other misc things. https://github.com/mattrobenolt/raven-node/compare/v0.4.7...v0.5.0
- Actually disable when NODE_ENV does not equal 'production' [Fixes #25]
- Added
platform=node
to payload for Sentry 5.1
- Resolve
node_modules
path properly [Fixes #23]
- Prevent 'error' event from bubbling up due to no listeners [See #22]
- Augment 'error' event emitter with an actual Error object [See #22]
- Allow a callback to be given to
patchGlobal()
[Fixes #19] - Removed old
patch_global()
alias
- Added test coverage to
patchGlobal()
- Quit using my own deprecated
get_ident()
method insidepatchGlobal
- Send string errors as a normal message to prevent Sentry server from crying [Fixes #18]
- patchGlobal() was actually broken. :( Thanks @ligthyear [Fixes #17]
- Silence and disable Raven/Sentry when using a non-existent or falsey DSN value
- Separate transports out into their own module for portability
- Added UDP transport [Fixes #10]
- Ignore sub-transports, such as gevent+https, raven sees it as just https
- Added parsing DSNs with non-standard port. [Fixes #4]
- Added BSD license
- Prevent any potentially odd stack traces from causing Raven to crash. [Fixes #2]
- raven.Client now emits
logged
anderror
events.
- Fixed connect/express middleware, thanks Almad!
- Renamed all methods to follow
client.capture*()
pattern. (Sorry if you were already using it!) - All
npm
installed modules are shoved into Sentry for debugging - Toggle actual sending based on
NODE_ENV
variable. Check README for information. - Fixes for more types of stack traces.
- Added
client.captureQuery()
- Support for
SENTRY_DSN
,SENTRY_NAME
, andSENTRY_SITE
enviornment variables - More test coverage
- Initial release