You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The sandbox contains a /no-issue which includes a page that throws an error and an error boundary that renders correctly. According to the docs the same pattern should work for a slot.
Provide environment information
Operating System:
Platform: linux
Arch: x64
Version: #1 SMP PREEMPT_DYNAMIC Sun Aug 6 20:05:33 UTC 2023
Binaries:
Node: 20.9.0
npm: 9.8.1
Yarn: 1.22.19
pnpm: 8.10.2
Relevant Packages:
next: 14.1.2
eslint-config-next: N/A
react: 18.2.0
react-dom: 18.2.0
typescript: 5.1.3
Next.js Config:
output: N/A
(this is from the sandbox)
Which area(s) are affected? (Select all that apply)
App Router
Which stage(s) are affected? (Select all that apply)
next dev (local)
Additional context
I have a slot on my application that is dynamic and depends on query params. The slot should throw an error when the Params don't make sense, so that an error boundary is shown. I tried doing a simialr implementation using notFound and I have the same problem. it also does not work.
The text was updated successfully, but these errors were encountered:
This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.
Link to the code that reproduces this issue
https://codesandbox.io/p/devbox/sweet-satoshi-pfvnzh?file=%2Fapp%2Flayout.tsx
To Reproduce
error.tsx
the parallel routepage.tsx
On the sandbox the error can be reproduced when visiting
/issue
Current vs. Expected behavior
Relevant Docs.
The sandbox contains a
/no-issue
which includes a page that throws an error and an error boundary that renders correctly. According to the docs the same pattern should work for a slot.Provide environment information
Operating System: Platform: linux Arch: x64 Version: #1 SMP PREEMPT_DYNAMIC Sun Aug 6 20:05:33 UTC 2023 Binaries: Node: 20.9.0 npm: 9.8.1 Yarn: 1.22.19 pnpm: 8.10.2 Relevant Packages: next: 14.1.2 eslint-config-next: N/A react: 18.2.0 react-dom: 18.2.0 typescript: 5.1.3 Next.js Config: output: N/A (this is from the sandbox)
Which area(s) are affected? (Select all that apply)
App Router
Which stage(s) are affected? (Select all that apply)
next dev (local)
Additional context
I have a slot on my application that is dynamic and depends on query params. The slot should throw an error when the Params don't make sense, so that an error boundary is shown. I tried doing a simialr implementation using
notFound
and I have the same problem. it also does not work.The text was updated successfully, but these errors were encountered: