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 build activity indicator position #35137

Closed

Conversation

stovmascript
Copy link
Contributor

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

  • Related issues linked using fixes #number
  • Integration tests added
  • Errors have helpful link attached, see contributing.md

@ijjk

This comment has been minimized.

@ijjk

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
@stovmascript
Copy link
Contributor Author

stovmascript commented 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 behaviour

git 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 fix

git 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.
@ijjk
Copy link
Member

ijjk commented Mar 10, 2022

Stats from current PR

Default Build (Decrease detected ✓)
General Overall decrease ✓
vercel/next.js canary monitora-media/next.js fix-build-activity-position Change
buildDuration 14.7s 14.9s ⚠️ +193ms
buildDurationCached 5.8s 5.6s -254ms
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.97 3.062 ⚠️ +0.09
/ avg req/sec 841.78 816.55 ⚠️ -25.23
/error-in-render failed reqs 0 0
/error-in-render total time (seconds) 1.346 1.372 ⚠️ +0.03
/error-in-render avg req/sec 1857.93 1822.66 ⚠️ -35.27
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 ⚠️ +815ms
buildDurationCached 5.9s 6s ⚠️ +107ms
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 ⚠️ +0.12
/ avg req/sec 845.48 811.62 ⚠️ -33.86
/error-in-render failed reqs 0 0
/error-in-render total time (seconds) 1.286 1.377 ⚠️ +0.09
/error-in-render avg req/sec 1944.06 1815.4 ⚠️ -128.66
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
Commit: 5694f07

Copy link
Member

@ijjk ijjk left a 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

@ijjk ijjk closed this in #36208 Apr 16, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 16, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants