Releases: getsentry/sentry-electron
Releases · getsentry/sentry-electron
v0.8.0
- Updated deps to use
@sentry/*
4.0.0-beta.11
- Send new SDK identifier
sentry.javascript.electron
- Expose
getIntegrations()
to retrieve all Integrations
v0.7.0
Breaking Changes:
-
We no longer exit your app by default. Before
0.7.0
we would call
process.exit(1)
after we caught and uncaught error. As of version0.7.0
we
no longer change electrons default behaviour which is showing a dialog with
the error and keep the app alive. If you want to exit the app or do something
else if a global uncaught error happens you have to set theonFatalError
option in init like (we will send the error to Sentry before this is called):init({ dsn: 'DSN', onFatalError: error => { // I really want to crash process.exit(1); }, });
v0.6.0
Breaking Changes:
- We removed
set___Context
functions, now you can configure the context with:
Sentry.configureScope(scope => {
scope.setExtra('battery', 0.7);
scope.setTag('user_mode', 'admin');
scope.setUser({ id: '4711' });
// scope.clear();
});
v0.5.5
v0.5.4
v0.5.3
v0.5.2
v0.5.1
- Added default values for
release
andenvironment
- Added an
event_type
tag to distinguish native from javascript errors - Send runtime information along with events: Electron, Chrome and Node versions
- Send app meta data, such as the application name and version
v0.5.0
Breaking Changes:
- All functions like
captureException
are now direct named exports - Most functions are now sync, and the async ones take a callback parameter
- The SDK is now initialized via
init()
(wascreate
before)
See the readme for full usage instructions, as well as the
@sentry/next tracking issue
for details on this change.
Other Changes:
- Set the default number of breadcrumbs to
30
- Fix an issue with paths containing spaces
v0.4.2
- Fix adding breadcrumbs in the renderer process
- Fix setting context in the renderer process
- Fix a crash during startup when trying to load breadcrumbs
- Handle
onFatalError
correctly