Closed csyedbilal closed 1 month ago
We could not detect a valid reproduction link. Make sure to follow the bug report template carefully.
To be able to investigate, we need access to a reproduction to identify what triggered the issue. We need a link to a public GitHub repository. Example: (NextAuth.js example repository).
The bug template that you filled out has a section called "Reproduction URL", which is where you should provide the link to the reproduction.
Depending on the reason the issue was closed, you can do the following:
In general, assume that we should not go through a lengthy onboarding process at your company code only to be able to verify an issue.
In most cases, a private repo will not be a sufficient minimal reproduction, as this codebase might contain a lot of unrelated parts that would make our investigation take longer. Please do not make it public. Instead, create a new repository using the templates above, adding the relevant code to reproduce the issue. Common things to look out for:
Anyone experiencing the same issue is welcome to provide a minimal reproduction following the above steps by opening a new issue.
We look into every issue and monitor open issues for new comments.
However, sometimes we might miss a few due to the popularity/high traffic of the repository. We apologize, and kindly ask you to refrain from tagging core maintainers, as that will usually not result in increased priority.
Upvoting issues to show your interest will help us prioritize and address them as quickly as possible. That said, every issue is important to us, and if an issue gets closed by accident, we encourage you to open a new one linking to the old issue and we will look into it.
Provider type
Email
Environment
Reproduction URL
nan
Describe the issue
1 of 1 error Next.js (15.0.0-rc.0) Server Error Error: The edge runtime does not support Node.js 'stream' module. Learn More: https://nextjs.org/docs/messages/node-module-in-edge-runtime
This error happened while generating the page. Any console logs will be displayed in the terminal window. Call Stack Next.js eval node_modules\nodemailer\lib\base64\index.js (56:1) (middleware)/./node_modules/nodemailer/lib/base64/index.js file:///B:/smm-panel/.next/server/src/middleware.js (1079:1) Next.js __webpack_require__ file:///B:/smm-panel/.next/server/edge-runtime-webpack.js (37:33) fn file:///B:/smm-panel/.next/server/edge-runtime-webpack.js (273:21) eval node_modules\nodemailer\lib\mime-funcs\index.js (5:16) (middleware)/./node_modules/nodemailer/lib/mime-funcs/index.js file:///B:/smm-panel/.next/server/src/middleware.js (1200:1) Next.js eval node_modules\nodemailer\lib\mime-node\index.js (11:19)
How to reproduce
import authConfig from "./../auth.config"; import NextAuth from "next-auth";
import { apiAuthPrefix, authRoutes, publicRoutes } from "./../routes";
const { auth } = NextAuth(authConfig);
export default auth((req) => { // const isLoggedIn = !!req.auth;
console.log("Route Path:", req.nextUrl.pathname); // console.log("isLoggedIn", isLoggedIn); });
export const config = { matcher: ["/((?!.+\.[\w]+$|_next).)", "/", "/(api|trpc)(.)"], };
Expected behavior
files stucture is SRC