Next.js Middleware does not work with "node-appwrite" because of using the edge runtime
- 0
- Auth
- Web
I use the "node-appwrite" in the Middleware to verify the user session in SSR, in local it works, but when i deploy the project to Vercel, the deployment fail because the Next.js Middleware works in the Edge Runtime, and it does not work with Node.js API, then is not compatible with "node-appwrite".
Any solution to this problem?
The Middleware Code:
export default async function middleware(req: NextRequest) {
const session = await verifySession();
if (!session) return NextResponse.redirect(new URL("/sign-in", req.url));
return NextResponse.next();
}
The Error in the Vercel Console:
Import trace for requested module:
./node_modules/node-appwrite/dist/client.mjs
./node_modules/node-appwrite/dist/index.mjs
A Node.js API is used (process.version at line: 33) which is not supported in the Edge Runtime.
Also, I found the library "react-appwrite", it says that support the Next.js Middleware, this is a proprietary library of AppWrite? or is it created by the community?
Recommended threads
- Project Inactivity Clarification
I'm on appwrite free plan with my account (om.thakkar@ivcventure.com). Even though throughout the week we use the project atleast once to upload dynamic content...
- [ENHANCEMENT] Use the custom Next.js dep...
Deployment adapters on Next.js are now stable! This means that we don't have to stick to the limitations of sniffing out build outputs and manually moving or mo...
- NextJS builds sudden runtime_timeout
My builds suddenly stopped working. Activating old prebuilt snapshots work, but redeploying that same code produces builds that throw runtime_timeout FRA region