v5.0.0

[HazAT]

While this major version bump and therefor "breaking", if people where using the exposed high level functions like:

Sentry.init
Sentry.captureException
Sentry.captureMessage
Sentry.addBreadcrumb
...

nothing changes. There are some internal breaking changes if you directly worked with a Client, please see Changelog for more details.

• Remove install function
• Remove public async API (except eventProcessors, beforeSend)
• Hide stuff in typedoc
• Remove deprecated API
• Do not expose Backend in index.ts
• Make close dispose / disable the client
• maxValueLength option
• Add module to package.json to support esm/esnext
• Extract "pluggable" integrations into own package
• Use SyncPromise -> Our implementation of a promise that can be sync once resolved
• Make Dedupe optional?
• Figure out how to serve "pluggable" integration via the cdn (maybe https://unpkg.com/)
• Delete Branch ref/make-sync Use SyncPromise internally & Remove deprecated API & Trim Public API #1858
• Find out which polyfills we need to make it work on ie10/11

[benvinegar]

@HazAT Why not keep install as a no-op (with maybe a console warning)? Why is it necessary to remove this method?

[HazAT]

hey @benvinegar :)

install wasn't really used in @sentry/browser already.
Only to set Error.stackTraceLimit = 50;
see: https://github.com/getsentry/sentry-javascript/pull/1919/files#diff-dda6e6fb49918cb8c88c1e6af83e4585L34

So with that change we really only remove implicit internal functionality, since the only call to install was in init: https://github.com/getsentry/sentry-javascript/pull/1919/files#diff-867baf4b7df6e7e6158b92082b86d68fL25

Instead now we set the stackTraceLimit in the global error handler integration.

Keeping this as a noop doesn't really add anything since it, as mentioned before, install was only used in raven-js.
With the new SDKs we made install implicit by just calling init.

[benvinegar]

If I'm running 4.x, and I install 5.x, under what conditions will I have to change my code (public async API)?

[HazAT]

@benvinegar There are no code changes needed, the "Static API" didn't change.

Sentry.init({dsn: "DSN"});
Sentry.captureException(new Error('test')); // This was never a promise

Internally if you created your own Client, something like:

const client = new Browser_Client({dsn: "DSN"});
client.captureException(new Error('test')); // <- this no longer returns a promise

the API of Client no longer returns Promise instead now only returns string | undefined (event_id).

[getsentry-bot]

	Fails
🚫	TSLint failed: @sentry/node ERROR: /home/travis/build/getsentry/sentry-javascript/packages/node/src/stack-trace.ts[1, 1]: File name must be camelCase ERROR: /home/travis/build/getsentry/sentry-javascript/packages/node/test/stack-trace.test.ts[1, 1]: File name must be camelCase

	Messages
📖	@sentry/browser bundle gzip'ed minified size: (ES6: 14.3223 kB) ()

Generated by 🚫 dangerJS against 6755a66

[JCMais]

@HazAT with this change is there any recommended way to retrieve the breadcrumbs for given stack?

Previously I was using:

Sentry.getCurrentHub().stack[0].scope._breadcrumbs

Now I changed it to:

Sentry.getCurrentHub().getStack()[0].scope._breadcrumbs

But I'm still accessing an internal property, and I would like to avoid that.

(context, this is used on this middleware for redux: https://gist.github.com/olavoasantos/9ac791098758ee7dedf0c0424ec8b398#file-sentry-for-redux-js-L84)

[kamilogorek]

@JCMais we don't expose getters on the scope. However, your example can be simplified to:

Sentry.getCurrentHub().getScope()._breadcrumbs;

getScope is a basically a shortcut for .getStack()[0].scope.