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

Re-enable minifying middleware chunks #30823

Merged
merged 1 commit into from
Nov 2, 2021

Conversation

ijjk
Copy link
Member

@ijjk ijjk commented Nov 2, 2021

This re-enables minifying middleware chunks as testing on nextjs.org and front shows it is working properly now. The separation of middleware chunks from other client chunks is still kept in this PR to ensure client code doesn't leak into middleware bundles.

Closes: #30798

Bug

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

Feature

  • Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR.
  • Related issues linked using fixes #number
  • Integration tests added
  • Documentation added
  • Telemetry added. In case of a feature if it's used or not.
  • Errors have helpful link attached, see contributing.md

Documentation / Examples

  • Make sure the linting passes by running yarn lint

@ijjk ijjk added created-by: Next.js team PRs by the Next.js team. type: next labels Nov 2, 2021
@ijjk
Copy link
Member Author

ijjk commented Nov 2, 2021

Stats from current PR

Default Build (Decrease detected ✓)
General Overall decrease ✓
vercel/next.js canary ijjk/next.js enable/minifying-middleware Change
buildDuration 21.6s 22.3s ⚠️ +741ms
buildDurationCached 4.5s 4.6s ⚠️ +112ms
nodeModulesSize 293 MB 293 MB -54 B
Page Load Tests Overall decrease ⚠️
vercel/next.js canary ijjk/next.js enable/minifying-middleware Change
/ failed reqs 0 0
/ total time (seconds) 3.643 4.236 ⚠️ +0.59
/ avg req/sec 686.3 590.25 ⚠️ -96.05
/error-in-render failed reqs 0 0
/error-in-render total time (seconds) 1.901 2 ⚠️ +0.1
/error-in-render avg req/sec 1315.23 1249.71 ⚠️ -65.52
Client Bundles (main, webpack, commons)
vercel/next.js canary ijjk/next.js enable/minifying-middleware Change
450.HASH.js gzip 179 B 179 B
framework-HASH.js gzip 42.2 kB 42.2 kB
main-HASH.js gzip 28 kB 28 kB
webpack-HASH.js gzip 1.45 kB 1.45 kB
Overall change 71.9 kB 71.9 kB
Legacy Client Bundles (polyfills)
vercel/next.js canary ijjk/next.js enable/minifying-middleware Change
polyfills-HASH.js gzip 31 kB 31 kB
Overall change 31 kB 31 kB
Client Pages
vercel/next.js canary ijjk/next.js enable/minifying-middleware Change
_app-HASH.js gzip 1.23 kB 1.23 kB
_error-HASH.js gzip 194 B 194 B
amp-HASH.js gzip 312 B 312 B
css-HASH.js gzip 327 B 327 B
dynamic-HASH.js gzip 2.38 kB 2.38 kB
head-HASH.js gzip 350 B 350 B
hooks-HASH.js gzip 635 B 635 B
image-HASH.js gzip 4.44 kB 4.44 kB
index-HASH.js gzip 263 B 263 B
link-HASH.js gzip 1.87 kB 1.87 kB
routerDirect..HASH.js gzip 321 B 321 B
script-HASH.js gzip 383 B 383 B
withRouter-HASH.js gzip 318 B 318 B
334f979574ae..6f4.css gzip 106 B 106 B
Overall change 13.1 kB 13.1 kB
Client Build Manifests
vercel/next.js canary ijjk/next.js enable/minifying-middleware Change
_buildManifest.js gzip 459 B 459 B
Overall change 459 B 459 B
Rendered Page Sizes
vercel/next.js canary ijjk/next.js enable/minifying-middleware Change
index.html gzip 521 B 521 B
link.html gzip 533 B 533 B
withRouter.html gzip 515 B 515 B
Overall change 1.57 kB 1.57 kB

Default Build with SWC (Decrease detected ✓)
General Overall decrease ✓
vercel/next.js canary ijjk/next.js enable/minifying-middleware Change
buildDuration 23.6s 24.2s ⚠️ +544ms
buildDurationCached 4.7s 4.4s -207ms
nodeModulesSize 293 MB 293 MB -54 B
Page Load Tests Overall decrease ⚠️
vercel/next.js canary ijjk/next.js enable/minifying-middleware Change
/ failed reqs 0 0
/ total time (seconds) 3.695 3.646 -0.05
/ avg req/sec 676.63 685.66 +9.03
/error-in-render failed reqs 0 0
/error-in-render total time (seconds) 1.918 1.962 ⚠️ +0.04
/error-in-render avg req/sec 1303.24 1273.93 ⚠️ -29.31
Client Bundles (main, webpack, commons)
vercel/next.js canary ijjk/next.js enable/minifying-middleware Change
450.HASH.js gzip 179 B 179 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.43 kB 1.43 kB
Overall change 72.1 kB 72.1 kB
Legacy Client Bundles (polyfills)
vercel/next.js canary ijjk/next.js enable/minifying-middleware Change
polyfills-HASH.js gzip 31 kB 31 kB
Overall change 31 kB 31 kB
Client Pages
vercel/next.js canary ijjk/next.js enable/minifying-middleware Change
_app-HASH.js gzip 1.22 kB 1.22 kB
_error-HASH.js gzip 180 B 180 B
amp-HASH.js gzip 305 B 305 B
css-HASH.js gzip 321 B 321 B
dynamic-HASH.js gzip 2.38 kB 2.38 kB
head-HASH.js gzip 342 B 342 B
hooks-HASH.js gzip 622 B 622 B
image-HASH.js gzip 4.46 kB 4.46 kB
index-HASH.js gzip 256 B 256 B
link-HASH.js gzip 1.91 kB 1.91 kB
routerDirect..HASH.js gzip 314 B 314 B
script-HASH.js gzip 375 B 375 B
withRouter-HASH.js gzip 309 B 309 B
334f979574ae..6f4.css gzip 106 B 106 B
Overall change 13.1 kB 13.1 kB
Client Build Manifests
vercel/next.js canary ijjk/next.js enable/minifying-middleware Change
_buildManifest.js gzip 460 B 460 B
Overall change 460 B 460 B
Rendered Page Sizes
vercel/next.js canary ijjk/next.js enable/minifying-middleware Change
index.html gzip 521 B 521 B
link.html gzip 534 B 534 B
withRouter.html gzip 516 B 516 B
Overall change 1.57 kB 1.57 kB
Commit: a5a7112

@ijjk ijjk marked this pull request as ready for review November 2, 2021 17:15
@ijjk ijjk requested a review from kdy1 November 2, 2021 17:15
@kodiakhq kodiakhq bot merged commit c8d0a1b into vercel:canary Nov 2, 2021
@ijjk ijjk deleted the enable/minifying-middleware branch November 2, 2021 17:38
@vercel vercel locked as resolved and limited conversation to collaborators Jan 27, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Minify breaks on some middleware
2 participants