Comparing version 0.1.8 to 0.1.9
{ | ||
"name": "bugsnag", | ||
"description": "Bugsnag notifier for node.js scripts", | ||
"version": "0.1.8", | ||
"main": "./bugsnag.js", | ||
"version": "0.1.9", | ||
"main": "./lib/bugsnag.js", | ||
"homepage": "http://bugsnag.com", | ||
@@ -7,0 +7,0 @@ "dependencies": { |
@@ -1,6 +0,6 @@ | ||
Official Bugsnag Notifier for Node.js | ||
===================================== | ||
Bugsnag Notifier for Node.js | ||
============================ | ||
The Bugsnag Notifier for Node.js is designed to give you | ||
instant notification of exceptions from your Node.js applications. | ||
The Bugsnag Notifier for Node.js gives you instant notification of exceptions | ||
from your Node.js applications. | ||
By default, the notifier hooks into `uncaughtException` event, which means any | ||
@@ -10,27 +10,8 @@ uncaught exceptions will trigger a notification to be sent to your Bugsnag | ||
What is Bugsnag? | ||
---------------- | ||
[Bugsnag](http://bugsnag.com) captures exceptions in real-time from your web, | ||
[Bugsnag](http://bugsnag.com) captures errors in real-time from your web, | ||
mobile and desktop applications, helping you to understand and resolve them | ||
as fast as possible. [Create a free account](http://bugsnag.com). | ||
as fast as possible. [Create a free account](http://bugsnag.com) to start | ||
capturing exceptions from your applications. | ||
Features | ||
-------- | ||
- Automatic notification of uncaught exceptions | ||
- Send your own [non-fatal exceptions](#send-non-fatal-exceptions-to-bugsnag) | ||
to Bugsnag | ||
- Minimal CPU and memory footprint. | ||
- Track which users and urls were affected by an exception. | ||
- Optional integration with connect/express middleware to give your exceptions | ||
context from the request. | ||
- Send additional meta-data along with your exceptions using | ||
[`setExtraData`](#setextradata) | ||
- Filter sensitive data before sending exceptions with | ||
[`setFilters`](#setfilters) | ||
Installation & Setup | ||
@@ -69,3 +50,3 @@ -------------------- | ||
Using Express or Connect Middleware | ||
----------------------------------------- | ||
----------------------------------- | ||
@@ -289,10 +270,6 @@ In order to have bugsnag report on any exceptions in your express | ||
------------ | ||
- Check out the latest master to make sure the feature hasn't been | ||
implemented or the bug hasn't been fixed yet | ||
- Check out the issue tracker to make sure someone already hasn't requested | ||
it and/or contributed it | ||
- Fork the project | ||
- Start a feature/bugfix branch | ||
- [Fork](https://help.github.com/articles/fork-a-repo) the [notifier on github](https://github.com/bugsnag/bugsnag-node) | ||
- Commit and push until you are happy with your contribution | ||
- [Make a pull request](https://help.github.com/articles/using-pull-requests) | ||
- Thanks! | ||
@@ -304,5 +281,3 @@ | ||
The Bugsnag node.js notifier is released under the | ||
MIT License. Read the full license here: | ||
<https://github.com/bugsnag/bugsnag-node/blob/master/LICENSE> | ||
The Bugsnag Node.js notifier is free software released under the MIT License. | ||
See [LICENSE.txt](https://github.com/bugsnag/bugsnag-node/blob/master/LICENSE.txt) for details. |
Major refactor
Supply chain riskPackage has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.
Found 1 instance in 1 package
19197
280
3