mirror of
https://github.com/hanzoai/next.js.git
synced 2026-10-30 14:46:38 +00:00
Sebastian "Sebbie" SilbermannandGitHub
7c458922ea
The test was implicitly relying on `preloadEntriesOnStart` to load the module in our prod tests. Fixes https://github.com/vercel/next.js/actions/runs/15774186781/job/44464850249?pr=80710#step:34:282 and [other flakes](https://app.datadoghq.com/ci/test/runs?query=test_level%3Atest%20%40test.source.file%3A%22test%2Fe2e%2Fapp-dir%2Finstrumentation-order%2Finstrumentation-order.test.ts%22%20%40test.status%3Afail&agg_m=count&agg_m_source=base&agg_t=count¤tTab=overview&eventStack=&fromUser=true&index=citest&start=1749804083936&end=1750408883936&paused=true) Now we always trigger the page for the first time in the test and wait for the logs to come in instead of hardcoding a timeout.
11 lines
154 B
JavaScript
11 lines
154 B
JavaScript
/**
|
|
* @type {import('next').NextConfig}
|
|
*/
|
|
const nextConfig = {
|
|
experimental: {
|
|
preloadEntriesOnStart: false,
|
|
},
|
|
}
|
|
|
|
module.exports = nextConfig
|