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
"Error: Route "/dynamic-root": A component accessed data, headers, params, searchParams, or a short-lived cache without a Suspense boundary nor a "use cache" above it. See more info: https://nextjs.org/docs/messages/next-prerender-missing-suspense
660
-
at c (turbopack:///[project]/app/dynamic-root/indirection.tsx:9:0)
660
+
at c (turbopack:///[project]/app/dynamic-root/indirection.tsx:7:41)
661
661
at main (<anonymous>)
662
662
at body (<anonymous>)
663
663
at html (<anonymous>)
664
-
7 | export function IndirectionTwo({ children }) {
664
+
5 | }
665
+
6 |
666
+
> 7 | export function IndirectionTwo({ children }) {
667
+
| ^
665
668
8 | return children
666
-
> 9 | }
669
+
9 | }
667
670
10 |
668
671
To get a more detailed stack trace and pinpoint the issue, try one of the following:
669
672
- Start the app in development mode by running \`next dev\`, then open "/dynamic-root" in your browser to investigate the error.
"Error: Route "/sync-attribution/guarded-async-unguarded-clientsync" used \`new Date()\` inside a Client Component without a Suspense boundary above it. See more info here: https://nextjs.org/docs/messages/next-prerender-current-time-client
1682
-
at c (turbopack:///[project]/app/sync-attribution/guarded-async-unguarded-clientsync/client.tsx:9:6)
1683
-
7 | return (
1684
-
8 | <main>
1685
-
> 9 | <h1>Sync IO Access</h1>
1686
-
| ^
1687
-
10 | <p suppressHydrationWarning>Current date and time: {data}</p>
1688
-
11 | </main>
1689
-
12 | )
1685
+
at c (turbopack:///[project]/app/sync-attribution/guarded-async-unguarded-clientsync/client.tsx:5:15)
1686
+
3 | export function SyncIO() {
1687
+
4 | // This is a sync IO access that should not cause an error
1688
+
> 5 | const data = new Date().toISOString()
1689
+
| ^
1690
+
6 |
1691
+
7 | return (
1692
+
8 | <main>
1690
1693
To get a more detailed stack trace and pinpoint the issue, try one of the following:
1691
1694
- Start the app in development mode by running \`next dev\`, then open "/sync-attribution/guarded-async-unguarded-clientsync" in your browser to investigate the error.
1692
1695
- Rerun the production build with \`next build --debug-prerender\` to generate better stack traces.
"Error: Route "/sync-attribution/unguarded-async-unguarded-clientsync" used \`new Date()\` inside a Client Component without a Suspense boundary above it. See more info here: https://nextjs.org/docs/messages/next-prerender-current-time-client
1991
-
at c (turbopack:///[project]/app/sync-attribution/unguarded-async-unguarded-clientsync/client.tsx:9:6)
1992
-
7 | return (
1993
-
8 | <main>
1994
-
> 9 | <h1>Sync IO Access</h1>
1995
-
| ^
1996
-
10 | <p suppressHydrationWarning>Current date and time: {data}</p>
1997
-
11 | </main>
1998
-
12 | )
1994
+
at c (turbopack:///[project]/app/sync-attribution/unguarded-async-unguarded-clientsync/client.tsx:5:15)
1995
+
3 | export function SyncIO() {
1996
+
4 | // This is a sync IO access that should not cause an error
1997
+
> 5 | const data = new Date().toISOString()
1998
+
| ^
1999
+
6 |
2000
+
7 | return (
2001
+
8 | <main>
1999
2002
To get a more detailed stack trace and pinpoint the issue, try one of the following:
2000
2003
- Start the app in development mode by running \`next dev\`, then open "/sync-attribution/unguarded-async-unguarded-clientsync" in your browser to investigate the error.
2001
2004
- Rerun the production build with \`next build --debug-prerender\` to generate better stack traces.
"Error: Route "/client" used \`new Date()\` inside a Client Component without a Suspense boundary above it. See more info here: https://nextjs.org/docs/messages/next-prerender-current-time-client
85
-
at c (turbopack:///[project]/app/client/page.tsx:5:0)
85
+
at c (turbopack:///[project]/app/client/page.tsx:4:27)
0 commit comments