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

Load next config in next/jest #31230

Closed
wants to merge 3 commits into from

Conversation

padmaia
Copy link
Member

@padmaia padmaia commented Nov 9, 2021

Closes #31222

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 9, 2021
@ijjk

This comment has been minimized.

@padmaia padmaia marked this pull request as ready for review November 10, 2021 00:39
@ijjk
Copy link
Member

ijjk commented Nov 10, 2021

Stats from current PR

Default Build (Decrease detected ✓)
General Overall increase ⚠️
vercel/next.js canary padmaia/next.js add/next-jest-load-config Change
buildDuration 21.5s 21.6s ⚠️ +160ms
buildDurationCached 4.2s 4.2s -11ms
nodeModulesSize 333 MB 333 MB ⚠️ +2.74 kB
Page Load Tests Overall decrease ⚠️
vercel/next.js canary padmaia/next.js add/next-jest-load-config Change
/ failed reqs 0 0
/ total time (seconds) 3.428 3.494 ⚠️ +0.07
/ avg req/sec 729.31 715.56 ⚠️ -13.75
/error-in-render failed reqs 0 0
/error-in-render total time (seconds) 1.7 1.766 ⚠️ +0.07
/error-in-render avg req/sec 1470.16 1415.42 ⚠️ -54.74
Client Bundles (main, webpack, commons)
vercel/next.js canary padmaia/next.js add/next-jest-load-config Change
450.HASH.js gzip 179 B 179 B
framework-HASH.js gzip 42.2 kB 42.2 kB
main-HASH.js gzip 28.1 kB 28.1 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 padmaia/next.js add/next-jest-load-config Change
polyfills-HASH.js gzip 31 kB 31 kB
Overall change 31 kB 31 kB
Client Pages
vercel/next.js canary padmaia/next.js add/next-jest-load-config 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
85e02e95b279..7e3.css gzip 107 B 107 B
Overall change 13.1 kB 13.1 kB
Client Build Manifests
vercel/next.js canary padmaia/next.js add/next-jest-load-config Change
_buildManifest.js gzip 460 B 460 B
Overall change 460 B 460 B
Rendered Page Sizes
vercel/next.js canary padmaia/next.js add/next-jest-load-config Change
index.html gzip 523 B 523 B
link.html gzip 535 B 535 B
withRouter.html gzip 515 B 515 B
Overall change 1.57 kB 1.57 kB

Default Build with SWC (Increase detected ⚠️)
General Overall increase ⚠️
vercel/next.js canary padmaia/next.js add/next-jest-load-config Change
buildDuration 23.3s 22.8s -471ms
buildDurationCached 4.2s 4.2s -30ms
nodeModulesSize 333 MB 333 MB ⚠️ +2.74 kB
Page Load Tests Overall increase ✓
vercel/next.js canary padmaia/next.js add/next-jest-load-config Change
/ failed reqs 0 0
/ total time (seconds) 3.483 3.518 ⚠️ +0.03
/ avg req/sec 717.87 710.58 ⚠️ -7.29
/error-in-render failed reqs 0 0
/error-in-render total time (seconds) 1.747 1.662 -0.09
/error-in-render avg req/sec 1431.39 1504.27 +72.88
Client Bundles (main, webpack, commons)
vercel/next.js canary padmaia/next.js add/next-jest-load-config 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 padmaia/next.js add/next-jest-load-config Change
polyfills-HASH.js gzip 31 kB 31 kB
Overall change 31 kB 31 kB
Client Pages
vercel/next.js canary padmaia/next.js add/next-jest-load-config 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
85e02e95b279..7e3.css gzip 107 B 107 B
Overall change 13.1 kB 13.1 kB
Client Build Manifests
vercel/next.js canary padmaia/next.js add/next-jest-load-config Change
_buildManifest.js gzip 459 B 459 B
Overall change 459 B 459 B
Rendered Page Sizes
vercel/next.js canary padmaia/next.js add/next-jest-load-config Change
index.html gzip 523 B 523 B
link.html gzip 535 B 535 B
withRouter.html gzip 517 B 517 B
Overall change 1.57 kB 1.57 kB
Commit: 924ce8a

: path.join(cwd, transformConfig.configFile)
: findUp.sync(CONFIG_FILES, { cwd })
if (configPath) {
return require(configPath)
Copy link
Member

Choose a reason for hiding this comment

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

Should we use import() here since next.config.mjs could be being used?

Copy link
Member Author

Choose a reason for hiding this comment

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

It has to be synchronous 🤔

Copy link
Member

Choose a reason for hiding this comment

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

Maybe we can use a wrapper mjs file we can execute synchronously that imports the next.config file and writes the needed config values to stdout which can be parsed here

@padmaia
Copy link
Member Author

padmaia commented Nov 10, 2021

Closing in favor of #31246

@padmaia padmaia closed this Nov 10, 2021
@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.

next/jest should load next configuration
2 participants