mirror of
https://github.com/hanzoai/next.js.git
synced 2026-10-30 14:46:38 +00:00
Jiachi LiuandGitHub
9035f14dda
Edge runtime doesn't have `/404` entry points as not-found, if server hits 404 it's hitting `/_not-found` entry point of edge bundles unlike nodejs server rendering. In app-render it needs the information that when `pathname` (or can call `pagePath`) is `/404` it can render the `not-found.js` components properly Separate the not-found test suite into 2 parts, a basic case testing all urls with `not-found.js` boundary, and another conflict route case with `not-found.js` with `not-found/` route at the same time Fixes #53652 Fixes #53210
12 lines
192 B
JavaScript
12 lines
192 B
JavaScript
export default function NotFound() {
|
|
return (
|
|
<>
|
|
<h1>This Is The Not Found Page</h1>
|
|
|
|
<div id="timestamp">{Date.now()}</div>
|
|
</>
|
|
)
|
|
}
|
|
|
|
NotFound.displayName = 'NotFound'
|