Repository navigation
Replies: 4 comments 1 reply
|
I believe this is not a bug - when you wrap a component tree in |
0 replies
|
Thanks for jumping in @abhi12299
|
0 replies
|
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment


Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Link to the code that reproduces this issue
https://github.com/aronwoost/nextjs-suspense-notfound-issue
To Reproduce
npm installnpm run devCurrent vs. Expected behavior
Current: "not found" page opens with status code 200
Expected: "not found" page opens with status code 404
Provide environment information
Operating System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 23.5.0: Wed May 1 20:19:05 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T8112 Available memory (MB): 16384 Available CPU cores: 8 Binaries: Node: 18.19.1 npm: 10.2.4 Yarn: N/A pnpm: N/A Relevant Packages: next: 14.2.13 // Latest available version is detected (14.2.13). eslint-config-next: 14.2.13 react: 18.3.1 react-dom: 18.3.1 typescript: 5.6.2 Next.js Config: output: N/AWhich area(s) are affected? (Select all that apply)
Not sure
Which stage(s) are affected? (Select all that apply)
next dev (local), next build (local), next start (local), Vercel (Deployed), Other (Deployed)
Additional context
Find more details in the
READMEhere: https://github.com/aronwoost/nextjs-suspense-notfound-issueAll reactions