mirror of
https://github.com/hanzoai/next.js.git
synced 2026-09-24 17:00:51 +00:00
Hendrik LiebauandGitHub
542b2b029c
The test was calling `createNext` inside each `it.each` test body, which meant deployment setup time counted against the 60-second per-test timeout introduced in #89929. In deploy mode, `createNext` deploys to Vercel which can exceed 60 seconds. When the test timed out, the `next` local variable was never assigned (the `await createNext(...)` hadn't resolved), so the `afterEach` hook would throw a `TypeError` on `next.destroy()`. This left the module-level `nextInstance` variable pointing at the stale, half-initialized deploy instance. When the next test case started, `createNext` saw the leftover `nextInstance` and threw `"createNext called without destroying previous instance"`. The test now uses `nextTestSetup`, which runs `createNext` in `beforeAll` where it has the longer 120-second `setupTimeout`. Both API route variants (`/api/single` and `/api/multiple`) are real fixture files served from a single instance, so deployment only happens once.
25 lines
736 B
JavaScript
25 lines
736 B
JavaScript
export const config = { runtime: 'edge' }
|
|
// eslint-disable-next-line no-undef
|
|
const topStorage = new AsyncLocalStorage()
|
|
|
|
export default async function handler(request) {
|
|
const id = request.headers.get('req-id')
|
|
return topStorage.run({ id }, async () => {
|
|
const nested = await getSomeData(id)
|
|
return Response.json({ ...nested, ...topStorage.getStore() })
|
|
})
|
|
}
|
|
|
|
async function getSomeData(id) {
|
|
// eslint-disable-next-line no-undef
|
|
const nestedStorage = new AsyncLocalStorage()
|
|
return nestedStorage.run('nested-' + id, async () => {
|
|
try {
|
|
const response = await fetch('https://example.vercel.sh')
|
|
await response.text()
|
|
} finally {
|
|
return { nestedId: nestedStorage.getStore() }
|
|
}
|
|
})
|
|
}
|