8d4f4fcd38
### What? Using `revalidateTag` or `revalidatePath` in a route handler will not currently opt the handler into dynamic behavior. This means that if you use these APIs and don't opt into dynamic behavior by some other means, the revalidation call won't do anything as the route handler will be served statically. ### Why? During static generation, we do not currently indicate that usage of these APIs should opt into dynamic usage. ### How? This updates `revalidateTag` to throw a `DynamicUsageError` (similar to our other scenarios, such as search params bailout, headers/cookies, or fetch + revalidate/no-store) Closes NEXT-1712
36 lines
1.1 KiB
TypeScript
36 lines
1.1 KiB
TypeScript
import { createNextDescribe } from '../../../lib/e2e-utils'
|
|
|
|
createNextDescribe(
|
|
'app-dir revalidate-dynamic',
|
|
{
|
|
files: __dirname,
|
|
},
|
|
({ next, isNextStart }) => {
|
|
if (isNextStart) {
|
|
it('should correctly mark a route handler that uses revalidateTag as dynamic', async () => {
|
|
expect(next.cliOutput).toContain('λ /api/revalidate-path')
|
|
expect(next.cliOutput).toContain('λ /api/revalidate-tag')
|
|
})
|
|
}
|
|
|
|
it.each(['/api/revalidate-path', '/api/revalidate-tag'])(
|
|
`should revalidate the data with %s`,
|
|
async (path) => {
|
|
const browser = await next.browser('/')
|
|
const randomNumber = await browser.elementById('data-value').text()
|
|
await browser.refresh()
|
|
const randomNumber2 = await browser.elementById('data-value').text()
|
|
|
|
expect(randomNumber).toEqual(randomNumber2)
|
|
|
|
const revalidateRes = await next.fetch(path)
|
|
expect((await revalidateRes.json()).revalidated).toBe(true)
|
|
|
|
await browser.refresh()
|
|
|
|
const randomNumber3 = await browser.elementById('data-value').text()
|
|
expect(randomNumber).not.toEqual(randomNumber3)
|
|
}
|
|
)
|
|
}
|
|
)
|