Releases: adopted-ember-addons/ember-cli-bugsnag
Correctly set appVersion from config
Disable bugsnag when running in Fastboot
Bugsnag-js is only built for the browser and crashes when run in a node environment. Thanks to #63 we now have fastboot support. Thank you @josemarluedke 🎷
Load bugsnag using npm
Previously we loaded bugsnag through bower and provided access to the library through a shim.
This release begins including bugsnag using npm instead, allowing fastboot to run with ember-cli-bugsnag.
This also incidentally upgrades bugsnag to 3.0.6, this may cause issues for users.
See #62 and ember-cli-node-assets for more information. Big thanks to @josemarluedke for the contribution! ✨
Allow a custom releaseStage
Currently the releaseStage is derived through the environment set by ember-cli.
This allows a custom release stage to be set in the bugsnag
config. See README.md or #61 for more information.
Thanks to @josemarluedke in his work on #61.
Set releaseStage correctly
Thanks for @robclancy raising this issue, fixes #54.
Disable Bugsnag library in test builds
Install Bugsnag through bower
Loads the Bugsnag library through bower instead of injecting HTML and config settings to the page. The benefits are:
- Can load your development instance without an internet connection
- Does not have content security violations for bugsnag (unless you're reporting errors in development)
Important Requires users to run the blueprint to upgrade:
ember g ember-cli-bugsnag
Drops support for the releaseUrl
config option.
Includes a major refactor of ember-cli and initializer code, sorry for any bugs I've introduced :) The result is that Bugsnag initialisation happens earlier so we should be able to catch bugs during Ember boot up.
Happy hacking!
Upgrade to ember-cli 0.2.5
Thanks @kcin1018 for work in upgrading to ember-cli 0.2.5.
Allow custom busgnag endpoints
For users with a custom bugsnag installation this release allows people to specify the endpoint to report to.
Thanks to @kcin1018 for work in #42.
Only report errors from Ember.onerror
See #38 for more information. Was unnecessarily reporting events that Ember.onerror now handles.