Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
After upgrading stytch-node to 6.0, a Next.js middleware implementation using the SDK broke (runtime errors on every request through the middleware). The 6.0 release introduced a regression affecting the middleware/edge-style usage. Downgrading was the only immediate option.
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
Fixed in stytch-node v6.0.1, released the same week; the reporter confirmed 6.0.1 resolved the middleware breakage. Upgrade to stytch-node 6.0.1 or newer. If you are pinned to 6.0.0 and cannot move, the only workaround is downgrading to the 5.x line until you can take the patch. Source: https://github.com/stytchauth/stytch-node/issues/191
Source: https://github.com/stytchauth/stytch-node/issues/191
Shows how to fix stytch-node 6.0 breaks Next.js middleware. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Shows how to fix aI SDK on the Next.js Edge runtime: what changes and what breaks. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
The v4 SDK rewrote the Next.js integration: auth0.middleware in middleware.ts, auth0.getSession in server components, and env vars that must all be set.