5831d0c124
Since the static metadata routes should always be static that can be optimized, they should be marked as default runtime (or basically no runtime). This PR change the runtime detection, if it's a static metadata route file, its runtime will be erased. So that it won't be picked up by `edge-app-route-loader` and then by `next-image-loader` which emits the unexpected static file Fixes NEXT-1238
29 lines
946 B
TypeScript
29 lines
946 B
TypeScript
import { createNextDescribe } from 'e2e-utils'
|
|
|
|
createNextDescribe(
|
|
'app-dir edge runtime root layout',
|
|
{
|
|
files: __dirname,
|
|
skipDeployment: true,
|
|
},
|
|
({ next, isNextStart }) => {
|
|
it('should not emit metadata files into bad paths', async () => {
|
|
await next.fetch('/favicon.ico')
|
|
// issue: If metadata files are not filter out properly with image-loader,
|
|
// an incorrect static/media folder will be generated
|
|
|
|
// Check that the static folder is not generated
|
|
const incorrectGeneratedStaticFolder = await next.hasFile('static')
|
|
expect(incorrectGeneratedStaticFolder).toBe(false)
|
|
})
|
|
|
|
if (isNextStart) {
|
|
it('should mark static contain metadata routes as edge functions', async () => {
|
|
const middlewareManifest = await next.readFile(
|
|
'.next/server/middleware-manifest.json'
|
|
)
|
|
expect(middlewareManifest).not.toContain('favicon')
|
|
})
|
|
}
|
|
}
|
|
)
|