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
Explain that Blitz Routes don't work in app directory. Explain how to use the experimental types route feature of NextJS App Router and how to use this with as Route whenever a param has to be added.
See also https://discord.com/channels/802917734999523368/1161595039043047445
TODO: How to work around that next/head is not available in App directory and Metatags are only available in server components which did not work for me (yet). We are considering moving back to ReactHelmet…
I wanted to keep track on changes, so I will list the things I see missing in the current guide at https://blitzjs.com/docs/usage-next-13#app-directory
Blocker
BlitzProvider
as client component #847/src/app
folder #845Routes
don't work in app directory. Explain how to use the experimental types route feature of NextJS App Router and how to use this withas Route
whenever a param has to be added.See also https://discord.com/channels/802917734999523368/1161595039043047445
useParams
,useRouter
,useSearchParams
, see also https://discord.com/channels/802917734999523368/1161571344459239495next/head
is not available in App directory andMetatags
are only available in server components which did not work for me (yet). We are considering moving back to ReactHelmet…authConfig
#844FooPage.authenticate = true
need to be replaces withuseAuthenticatedBlitzContext
. But first there is App Router:useAuthenticatedBlitzContext
withredirectAuthenticatedTo
results in infinite loop blitz#4246 to be resolved.Improvements
loading.tsx
files #846/src/app
folder #845Minor
authConfig
#844The text was updated successfully, but these errors were encountered: