Skip to content

Conversation

@iker-barriocanal
Copy link
Contributor

Besides merging master (required for some code), this PR adds performance monitoring on the frontend automatically, requiring no action from the user.

@iker-barriocanal iker-barriocanal self-assigned this May 21, 2021
@AbhiPrasad AbhiPrasad self-assigned this May 21, 2021
@github-actions
Copy link
Contributor

github-actions bot commented May 21, 2021

size-limit report

Path Size
@sentry/browser - CDN Bundle (gzipped) 20.76 KB (+0.01% 🔺)
@sentry/browser - Webpack 21.98 KB (0%)
@sentry/react - Webpack 22.01 KB (0%)
@sentry/browser + @sentry/tracing - CDN Bundle (gzipped) 28.16 KB (+0.01% 🔺)

@AbhiPrasad AbhiPrasad requested a review from lobsterkatie May 21, 2021 18:40
Copy link
Member

@lobsterkatie lobsterkatie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Besides merging master (required for some code)

Noted changes are from 15a2aa2, 84d05f4 and 3290289, which are all contained in #3586 (files) and #3586 (files)

The main nextjs performance feature branch is up to date with master. Can you please rebase on that, so that this PR only has your changes? That's much easier than trying to keep track of which commits and files count towards the PR and which don't.

iker-barriocanal and others added 3 commits May 25, 2021 08:08
For ease of use, I make it so that for client-side tracing
nextRouterInstrumentation is always turned on
@AbhiPrasad AbhiPrasad force-pushed the iker/nextjs-client-perf-auto branch from 3290289 to 5f05c5b Compare May 25, 2021 12:08
@AbhiPrasad
Copy link
Member

Rebased to make changes easier to see.

@AbhiPrasad AbhiPrasad merged commit 4d37cd1 into kmclb-next-js-performance May 25, 2021
@AbhiPrasad AbhiPrasad deleted the iker/nextjs-client-perf-auto branch May 25, 2021 16:24
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