e029ace5ed
x-ref: https://github.com/vercel/next.js/issues/30424#issuecomment-955615781 This fix the custom 404 is not rendering properly and can’t be built in web runtime when `concurrentFeatures` is enabled. We force 404 page to be rendered outside of middleware ssr. Then it could be the real fallback 404 page in next-server when any routes is not macthed. Will check 500 related after #31057 is landed. ## Bug - [x] Related to #30989 - [x] Integration tests added |
||
---|---|---|
.. | ||
terser-webpack-plugin | ||
wellknown-errors-plugin | ||
build-manifest-plugin.ts | ||
copy-file-plugin.ts | ||
css-minimizer-plugin.ts | ||
flight-manifest-plugin.ts | ||
font-stylesheet-gathering-plugin.ts | ||
jsconfig-paths-plugin.ts | ||
middleware-plugin.ts | ||
mini-css-extract-plugin.ts | ||
next-drop-client-page-plugin.ts | ||
next-trace-entrypoints-plugin.ts | ||
nextjs-require-cache-hot-reloader.ts | ||
nextjs-ssr-import.ts | ||
pages-manifest-plugin.ts | ||
profiling-plugin.ts | ||
react-loadable-plugin.ts | ||
serverless-plugin.ts | ||
telemetry-plugin.ts |