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
Supposing you are using Next.js' dynamic routes feature, how would you go about serving the payload admin if you are shipping the project as a monorepo? The dynamic route seems to take precedence over the payload's defined path. The result is that rather than rendering /admin as payload's admin, the catch all route will grab it and render based on the logic in app/[page]/page.tsx
Normally, you just create a /admin page, or whatever other page you want to opt out of the catch all, but obviously that's not possible in this situation.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Supposing you are using Next.js' dynamic routes feature, how would you go about serving the payload admin if you are shipping the project as a monorepo? The dynamic route seems to take precedence over the payload's defined path. The result is that rather than rendering /admin as payload's admin, the catch all route will grab it and render based on the logic in app/[page]/page.tsx
Normally, you just create a /admin page, or whatever other page you want to opt out of the catch all, but obviously that's not possible in this situation.
Ay ideas?
Beta Was this translation helpful? Give feedback.
All reactions