build(bundles): Use ES2017 for bundles (drop ES5 support)#10911
build(bundles): Use ES2017 for bundles (drop ES5 support)#10911
Conversation
size-limit report 📦
|
mydea
left a comment
There was a problem hiding this comment.
This all looks really good to me!
let's also add an entry into MIGRATION.md, indicating that ES5 is not supported anymore, and users need to polyfill stuff themselves if they want to continue supporting ES5.
Also, let's wait for another review from e.g. @AbhiPrasad to have a second set of eyes on this as well :)
|
After that we can also remove the promise like stuff etc 🎉 |
@mydea This should be covered here in MIGRATION.md: https://github.com/getsentry/sentry-javascript/pull/10911/files#diff-c1603ee6a674bb75255aa448057630506153e363297fd58668e6679f10909bc6L27-L40 Or should we be more specific on that? |
|
Ahh you are right of course, we already added this in advance - all good then :D |
| `@sentry/node` and all of our node-based server-side sdks (`@sentry/nextjs`, `@sentry/serverless`, etc.). We no longer | ||
| test against Node 8, 10, or 12 and cannot guarantee that the SDK will work as expected on these versions. | ||
|
|
||
| **Browser**: Our browser SDKs (`@sentry/browser`, `@sentry/react`, `@sentry/vue`, etc.) now require ES6+ compatible |
There was a problem hiding this comment.
We should double check if the browser listed below are still accurate here - caniuse is here
As the coming version of the JS SDK only uses ES2017 bundles, it is no longer necessary to differentiate between es5 and es6 bundles. ref getsentry/sentry-javascript#10911
ref #9829