mirror of
https://github.com/hanzoai/next.js.git
synced 2026-09-24 17:00:51 +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
17 lines
318 B
JavaScript
17 lines
318 B
JavaScript
export default function Layout({ children }) {
|
|
return (
|
|
<html>
|
|
<head />
|
|
<body>
|
|
<header>
|
|
<nav id="layout-nav">Navbar</nav>
|
|
</header>
|
|
<main>{children}</main>
|
|
<footer>
|
|
<p id="layout-footer">Footer</p>
|
|
</footer>
|
|
</body>
|
|
</html>
|
|
)
|
|
}
|