Skip to content

build(bundles): Rename CDN bundles to be es6 per default#4958

Merged
lforst merged 1 commit into7.xfrom
lforst-v7-cdn-packages-es6-per-default
Apr 21, 2022
Merged

build(bundles): Rename CDN bundles to be es6 per default#4958
lforst merged 1 commit into7.xfrom
lforst-v7-cdn-packages-es6-per-default

Conversation

@lforst
Copy link
Contributor

@lforst lforst commented Apr 21, 2022

This PR will adjust the naming of our CDN bundle. All bundles named *.es6*.js will now be named *.js and all bundles previously named *.js will now be named *.es5*.js.

This effectively makes the ES6 browser bundles the new default.

Migration docs have already been updated in #4918

Ref: https://getsentry.atlassian.net/browse/WEB-838

@github-actions
Copy link
Contributor

size-limit report 📦

Path Size
@sentry/browser - ES5 CDN Bundle (gzipped + minified) 20.23 KB (+0.81% 🔺)
@sentry/browser - ES5 CDN Bundle (minified) 64.37 KB (-0.28% 🔽)
@sentry/browser - ES6 CDN Bundle (gzipped + minified) 18.85 KB (+0.41% 🔺)
@sentry/browser - ES6 CDN Bundle (minified) 58.03 KB (+0.13% 🔺)
@sentry/browser - Webpack (gzipped + minified) 23.4 KB (+0.82% 🔺)
@sentry/browser - Webpack (minified) 81.29 KB (-1.41% 🔽)
@sentry/react - Webpack (gzipped + minified) 23.45 KB (+0.84% 🔺)
@sentry/nextjs Client - Webpack (gzipped + minified) 47.99 KB (-0.03% 🔽)
@sentry/browser + @sentry/tracing - ES5 CDN Bundle (gzipped + minified) 26.07 KB (+0.36% 🔺)
@sentry/browser + @sentry/tracing - ES6 CDN Bundle (gzipped + minified) 24.43 KB (+0.11% 🔺)

@Noitidart
Copy link

Is it possible to move back to es5 by default? It's breaking next.js entirely on some browsers like safari ios 10 and more - vercel/next.js#38935

@lobsterkatie
Copy link
Member

Is it possible to move back to es5 by default? It's breaking next.js entirely on some browsers like safari ios 10 and more - vercel/next.js#38935

See #5452

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants