Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: next.js few fixes #3479

Merged
merged 8 commits into from
Apr 29, 2021
Merged

fix: next.js few fixes #3479

merged 8 commits into from
Apr 29, 2021

Conversation

HazAT
Copy link
Member

@HazAT HazAT commented Apr 28, 2021

  • The changes in @sentry/serverless are not really needed anymore but it can't harm for some weird AWS serverless env that don't have getRemainingTimeInMillis -> Vercel
  • Fallback to buildId as a release in webpack build to vercel dev deployments also work out of the box
  • Auto inject Sentry into API routes

@HazAT HazAT changed the title fix: Use buildId as fallback release fix: next.js few fixes Apr 28, 2021
@github-actions
Copy link
Contributor

github-actions bot commented Apr 28, 2021

size-limit report

Path Size
@sentry/browser - CDN Bundle (gzipped) 20.63 KB (-0.01% 🔽)
@sentry/browser - Webpack 21.5 KB (0%)
@sentry/react - Webpack 21.53 KB (0%)
@sentry/browser + @sentry/tracing - CDN Bundle (gzipped) 27.92 KB (+0.01% 🔺)

@iker-barriocanal iker-barriocanal marked this pull request as ready for review April 29, 2021 08:14
@iker-barriocanal iker-barriocanal self-requested a review April 29, 2021 08:14
@HazAT HazAT merged commit 3fbe529 into master Apr 29, 2021
@HazAT HazAT deleted the feat/next-js-fixes branch April 29, 2021 08:16
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.

2 participants