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

Update check for fallback pages during export #33323

Merged
merged 4 commits into from
Jan 17, 2022

Conversation

ijjk
Copy link
Member

@ijjk ijjk commented Jan 14, 2022

This fixes our check for fallback pages during next export as we are currently erroring even when the erroneous pages are not included in the exportPathMap. This also adds additional tests to certify the expected behavior for the error.

Bug

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

Fixes: #29135

@ijjk ijjk added created-by: Next.js team PRs by the Next.js team type: next labels Jan 14, 2022
@ijjk

This comment has been minimized.

@ijjk ijjk marked this pull request as ready for review January 14, 2022 20:12
@ijjk
Copy link
Member Author

ijjk commented Jan 17, 2022

Stats from current PR

Default Build (Increase detected ⚠️)
General Overall decrease ✓
vercel/next.js canary ijjk/next.js fix/export-fallback-check Change
buildDuration 14s 14.2s ⚠️ +177ms
buildDurationCached 3.1s 3.1s ⚠️ +29ms
nodeModulesSize 355 MB 355 MB -117 B
Page Load Tests Overall increase ✓
vercel/next.js canary ijjk/next.js fix/export-fallback-check Change
/ failed reqs 0 0
/ total time (seconds) 2.934 2.854 -0.08
/ avg req/sec 851.97 876.11 +24.14
/error-in-render failed reqs 0 0
/error-in-render total time (seconds) 1.332 1.315 -0.02
/error-in-render avg req/sec 1877.5 1900.52 +23.02
Client Bundles (main, webpack, commons)
vercel/next.js canary ijjk/next.js fix/export-fallback-check Change
450.HASH.js gzip 179 B 179 B
framework-HASH.js gzip 42.2 kB 42.2 kB
main-HASH.js gzip 27.2 kB 27.2 kB
webpack-HASH.js gzip 1.44 kB 1.44 kB
Overall change 71 kB 71 kB
Legacy Client Bundles (polyfills)
vercel/next.js canary ijjk/next.js fix/export-fallback-check Change
polyfills-HASH.js gzip 31 kB 31 kB
Overall change 31 kB 31 kB
Client Pages
vercel/next.js canary ijjk/next.js fix/export-fallback-check Change
_app-HASH.js gzip 1.37 kB 1.37 kB
_error-HASH.js gzip 194 B 194 B
amp-HASH.js gzip 312 B 312 B
css-HASH.js gzip 326 B 326 B
dynamic-HASH.js gzip 2.37 kB 2.37 kB
head-HASH.js gzip 350 B 350 B
hooks-HASH.js gzip 919 B 919 B
image-HASH.js gzip 4.7 kB 4.7 kB
index-HASH.js gzip 263 B 263 B
link-HASH.js gzip 2.13 kB 2.13 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
85e02e95b279..7e3.css gzip 107 B 107 B
Overall change 14.1 kB 14.1 kB
Client Build Manifests
vercel/next.js canary ijjk/next.js fix/export-fallback-check Change
_buildManifest.js gzip 459 B 459 B
Overall change 459 B 459 B
Rendered Page Sizes
vercel/next.js canary ijjk/next.js fix/export-fallback-check Change
index.html gzip 531 B 531 B
link.html gzip 545 B 545 B
withRouter.html gzip 526 B 526 B
Overall change 1.6 kB 1.6 kB

Default Build with SWC (Decrease detected ✓)
General Overall decrease ✓
vercel/next.js canary ijjk/next.js fix/export-fallback-check Change
buildDuration 15.6s 15.8s ⚠️ +255ms
buildDurationCached 3.2s 3.1s -29ms
nodeModulesSize 355 MB 355 MB -117 B
Page Load Tests Overall decrease ⚠️
vercel/next.js canary ijjk/next.js fix/export-fallback-check Change
/ failed reqs 0 0
/ total time (seconds) 2.902 2.879 -0.02
/ avg req/sec 861.49 868.36 +6.87
/error-in-render failed reqs 0 0
/error-in-render total time (seconds) 1.291 1.317 ⚠️ +0.03
/error-in-render avg req/sec 1936.03 1897.67 ⚠️ -38.36
Client Bundles (main, webpack, commons)
vercel/next.js canary ijjk/next.js fix/export-fallback-check Change
450.HASH.js gzip 179 B 179 B
framework-HASH.js gzip 42.3 kB 42.3 kB
main-HASH.js gzip 27.3 kB 27.3 kB
webpack-HASH.js gzip 1.44 kB 1.44 kB
Overall change 71.3 kB 71.3 kB
Legacy Client Bundles (polyfills)
vercel/next.js canary ijjk/next.js fix/export-fallback-check Change
polyfills-HASH.js gzip 31 kB 31 kB
Overall change 31 kB 31 kB
Client Pages
vercel/next.js canary ijjk/next.js fix/export-fallback-check Change
_app-HASH.js gzip 1.35 kB 1.35 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.36 kB 2.36 kB
head-HASH.js gzip 342 B 342 B
hooks-HASH.js gzip 911 B 911 B
image-HASH.js gzip 4.73 kB 4.73 kB
index-HASH.js gzip 256 B 256 B
link-HASH.js gzip 2.19 kB 2.19 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
85e02e95b279..7e3.css gzip 107 B 107 B
Overall change 14.1 kB 14.1 kB
Client Build Manifests
vercel/next.js canary ijjk/next.js fix/export-fallback-check Change
_buildManifest.js gzip 459 B 459 B
Overall change 459 B 459 B
Rendered Page Sizes
vercel/next.js canary ijjk/next.js fix/export-fallback-check Change
index.html gzip 531 B 531 B
link.html gzip 545 B 545 B
withRouter.html gzip 526 B 526 B
Overall change 1.6 kB 1.6 kB
Commit: bebc29b

@kodiakhq kodiakhq bot merged commit 3894320 into vercel:canary Jan 17, 2022
@ijjk ijjk deleted the fix/export-fallback-check branch January 17, 2022 15:58
natew pushed a commit to natew/next.js that referenced this pull request Feb 16, 2022
This fixes our check for fallback pages during `next export` as we are currently erroring even when the erroneous pages are not included in the `exportPathMap`. This also adds additional tests to certify the expected behavior for the error. 

## Bug

- [x] Related issues linked using `fixes #number`
- [x] Integration tests added
- [x] Errors have helpful link attached, see `contributing.md`

Fixes: vercel#29135
@vercel vercel locked as resolved and limited conversation to collaborators Feb 17, 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.

next export fails even though a page using fallback in getStaticPaths is not included within exportPathMap
2 participants