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
create a nextjs app using the app router and the src folder
configure honeybadger using the nextjs documentation guide
configure env variables on Vercel
What happens?
Locally, with npm run dev all work normally.
After deploying to Vercel, I am getting an error.
What were you expecting to happen?
To not throw an error.
Any logs, error output, etc?
Error: Clerk: auth() was called but Clerk can't detect usage of authMiddleware(). Please ensure the following:
- authMiddleware() is used in your Next.js Middleware.
- Your Middleware matcher is configured to match this route or page.
- If you are using the src directory, make sure the Middleware file is inside of it.
For more details, see https://clerk.com/docs/quickstarts/get-started-with-nextjs.
at /var/task/.next/server/chunks/5961.js:12:47984
at /var/task/.next/server/chunks/5961.js:12:45968
at rx (/var/task/.next/server/chunks/5961.js:14:87)
at d (/var/task/.next/server/app/page.js:1:4354)
at /var/task/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:15:8530
at /var/task/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:15:8659
at async rx (/var/task/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:15:8353)
at async /var/task/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:15:7389
at async Promise.all (index 0)
at async rx (/var/task/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:15:7160)
What are the steps to reproduce this issue?
src
folderWhat happens?
Locally, with
npm run dev
all work normally.After deploying to Vercel, I am getting an error.
What were you expecting to happen?
To not throw an error.
Any logs, error output, etc?
What versions are you using?
Package Name: @honeybadger-io/nextjs
Package Version: 5.8.4
The text was updated successfully, but these errors were encountered: