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 build activity indicator position #35137
Closed
stovmascript
wants to merge
2
commits into
vercel:canary
from
monitora-media:fix-build-activity-position
Closed
Fix build activity indicator position #35137
stovmascript
wants to merge
2
commits into
vercel:canary
from
monitora-media:fix-build-activity-position
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
stovmascript
requested review from
timneutkens,
ijjk,
shuding and
huozhi
as code owners
March 8, 2022 12:50
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
stovmascript
added a commit
to stovmascript/demo-build-indicator
that referenced
this pull request
Mar 9, 2022
stovmascript
added a commit
to stovmascript/demo-build-indicator
that referenced
this pull request
Mar 9, 2022
stovmascript
added a commit
to stovmascript/demo-build-indicator
that referenced
this pull request
Mar 9, 2022
Here's a demo repo with the buggy behaviour on the 'main' branch and the fix applied from this PR on the 'fix' branch. 1. Observe buggy behaviourgit clone https://github.com/stovmascript/demo-build-indicator.git
cd demo-build-indicator/
yarn
yarn dev
# Now make some changes in `pages/index.js` 2. Test out the fixgit checkout fix
yarn install --force
rm -rf .next/
yarn dev
# Again, make some changes in `pages/index.js` |
`devIndicators.buildActivityPosition` introduced in vercel#30109 needed more tweaks to properly position the build indicator container. The build indicator was being rendered off screen when set to a non-default position.
stovmascript
force-pushed
the
fix-build-activity-position
branch
from
March 10, 2022 12:24
ff8c3a1
to
5694f07
Compare
Stats from current PRDefault Build (Decrease detected ✓)General Overall decrease ✓
Page Load Tests Overall decrease
|
vercel/next.js canary | monitora-media/next.js fix-build-activity-position | Change | |
---|---|---|---|
/ failed reqs | 0 | 0 | ✓ |
/ total time (seconds) | 2.97 | 3.062 | |
/ avg req/sec | 841.78 | 816.55 | |
/error-in-render failed reqs | 0 | 0 | ✓ |
/error-in-render total time (seconds) | 1.346 | 1.372 | |
/error-in-render avg req/sec | 1857.93 | 1822.66 |
Client Bundles (main, webpack)
vercel/next.js canary | monitora-media/next.js fix-build-activity-position | Change | |
---|---|---|---|
925.HASH.js gzip | 179 B | 179 B | ✓ |
framework-HASH.js gzip | 42 kB | 42 kB | ✓ |
main-HASH.js gzip | 27.9 kB | 27.9 kB | ✓ |
webpack-HASH.js gzip | 1.44 kB | 1.44 kB | ✓ |
Overall change | 71.6 kB | 71.6 kB | ✓ |
Legacy Client Bundles (polyfills)
vercel/next.js canary | monitora-media/next.js fix-build-activity-position | Change | |
---|---|---|---|
polyfills-HASH.js gzip | 31 kB | 31 kB | ✓ |
Overall change | 31 kB | 31 kB | ✓ |
Client Pages
vercel/next.js canary | monitora-media/next.js fix-build-activity-position | Change | |
---|---|---|---|
_app-HASH.js gzip | 1.36 kB | 1.36 kB | ✓ |
_error-HASH.js gzip | 192 B | 192 B | ✓ |
amp-HASH.js gzip | 309 B | 309 B | ✓ |
css-HASH.js gzip | 327 B | 327 B | ✓ |
dynamic-HASH.js gzip | 2.57 kB | 2.57 kB | ✓ |
head-HASH.js gzip | 351 B | 351 B | ✓ |
hooks-HASH.js gzip | 920 B | 920 B | ✓ |
image-HASH.js gzip | 5.09 kB | 5.09 kB | ✓ |
index-HASH.js gzip | 263 B | 263 B | ✓ |
link-HASH.js gzip | 2.26 kB | 2.26 kB | ✓ |
routerDirect..HASH.js gzip | 320 B | 320 B | ✓ |
script-HASH.js gzip | 387 B | 387 B | ✓ |
withRouter-HASH.js gzip | 319 B | 319 B | ✓ |
85e02e95b279..7e3.css gzip | 107 B | 107 B | ✓ |
Overall change | 14.8 kB | 14.8 kB | ✓ |
Client Build Manifests
vercel/next.js canary | monitora-media/next.js fix-build-activity-position | Change | |
---|---|---|---|
_buildManifest.js gzip | 460 B | 460 B | ✓ |
Overall change | 460 B | 460 B | ✓ |
Rendered Page Sizes
vercel/next.js canary | monitora-media/next.js fix-build-activity-position | Change | |
---|---|---|---|
index.html gzip | 530 B | 530 B | ✓ |
link.html gzip | 544 B | 544 B | ✓ |
withRouter.html gzip | 524 B | 524 B | ✓ |
Overall change | 1.6 kB | 1.6 kB | ✓ |
Default Build with SWC (Decrease detected ✓)
General Overall decrease ✓
vercel/next.js canary | monitora-media/next.js fix-build-activity-position | Change | |
---|---|---|---|
buildDuration | 17.1s | 17.9s | |
buildDurationCached | 5.9s | 6s | |
nodeModulesSize | 372 MB | 372 MB | -39 B |
Page Load Tests Overall decrease ⚠️
vercel/next.js canary | monitora-media/next.js fix-build-activity-position | Change | |
---|---|---|---|
/ failed reqs | 0 | 0 | ✓ |
/ total time (seconds) | 2.957 | 3.08 | |
/ avg req/sec | 845.48 | 811.62 | |
/error-in-render failed reqs | 0 | 0 | ✓ |
/error-in-render total time (seconds) | 1.286 | 1.377 | |
/error-in-render avg req/sec | 1944.06 | 1815.4 |
Client Bundles (main, webpack)
vercel/next.js canary | monitora-media/next.js fix-build-activity-position | Change | |
---|---|---|---|
925.HASH.js gzip | 178 B | 178 B | ✓ |
framework-HASH.js gzip | 42.3 kB | 42.3 kB | ✓ |
main-HASH.js gzip | 28.2 kB | 28.2 kB | ✓ |
webpack-HASH.js gzip | 1.45 kB | 1.45 kB | ✓ |
Overall change | 72.2 kB | 72.2 kB | ✓ |
Legacy Client Bundles (polyfills)
vercel/next.js canary | monitora-media/next.js fix-build-activity-position | Change | |
---|---|---|---|
polyfills-HASH.js gzip | 31 kB | 31 kB | ✓ |
Overall change | 31 kB | 31 kB | ✓ |
Client Pages
vercel/next.js canary | monitora-media/next.js fix-build-activity-position | Change | |
---|---|---|---|
_app-HASH.js gzip | 1.35 kB | 1.35 kB | ✓ |
_error-HASH.js gzip | 179 B | 179 B | ✓ |
amp-HASH.js gzip | 313 B | 313 B | ✓ |
css-HASH.js gzip | 324 B | 324 B | ✓ |
dynamic-HASH.js gzip | 2.56 kB | 2.56 kB | ✓ |
head-HASH.js gzip | 351 B | 351 B | ✓ |
hooks-HASH.js gzip | 921 B | 921 B | ✓ |
image-HASH.js gzip | 5.23 kB | 5.23 kB | ✓ |
index-HASH.js gzip | 261 B | 261 B | ✓ |
link-HASH.js gzip | 2.33 kB | 2.33 kB | ✓ |
routerDirect..HASH.js gzip | 322 B | 322 B | ✓ |
script-HASH.js gzip | 388 B | 388 B | ✓ |
withRouter-HASH.js gzip | 317 B | 317 B | ✓ |
85e02e95b279..7e3.css gzip | 107 B | 107 B | ✓ |
Overall change | 15 kB | 15 kB | ✓ |
Client Build Manifests
vercel/next.js canary | monitora-media/next.js fix-build-activity-position | Change | |
---|---|---|---|
_buildManifest.js gzip | 459 B | 459 B | ✓ |
Overall change | 459 B | 459 B | ✓ |
Rendered Page Sizes
vercel/next.js canary | monitora-media/next.js fix-build-activity-position | Change | |
---|---|---|---|
index.html gzip | 531 B | 531 B | ✓ |
link.html gzip | 545 B | 545 B | ✓ |
withRouter.html gzip | 527 B | 527 B | ✓ |
Overall change | 1.6 kB | 1.6 kB | ✓ |
ijjk
approved these changes
Apr 16, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR! Landing this in #36208
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
devIndicators.buildActivityPosition
introduced in #30109 needed more tweaks to properly position the build indicator container. The build indicator was being rendered off screen when set to a non-default position.Bug
fixes #number
contributing.md