Option to disable development mode request logging

[mopatches]

Goals

The NextJS dev server automatically prints out every request's method and time. This prints a lot of spam if there are background processes polling the NextJS server.

We should add an option to turn off this default-on logging.

Non-Goals

No response

Background

The change to add this default logging was added recently, in #62946.

Proposal

Gate the logging by a nextConfig flag within the logging subgroup.

Code to gate: https://github.com/vercel/next.js/blob/canary/packages/next/src/server/next-server.ts#L1153

writeStdoutLine(
  `${method} ${loggingUrl} ${color(
    res.statusCode.toString()
   )} in ${reqDuration}ms`
)

Bonus points if the option is a "log the request if it takes longer than N milliseconds", instead of a boolean log or don't log.

[ntatoud]

👍🏼 Would be a great idea, I spent my evening trying to figure out how to turn these off...

[calebjacob]

I definitely agree we need a config option to turn off these development server logs. This is a real pain point for my application. The new logs create so much noise that it makes it very difficult to see important log information when I need it.

[alex-zabyshny]

Completely agree. Spent all evening trying to disable this logging. It is surprising that someone decided that everyone needs it. Many people install their own loggers using pino, winston and so on.

[luskin]

Same here, it's absolutely horrendous when a background service is pinging frequently! Would be great to see route-level logging config (i.e. disabling certain /api routes from logging).

[waltershewmake]

I would love to see this implemented. These logs make it impossible to see actual logs, especially when using tRPC.

[Haswell-s]

I was looking for it too, hope it gets implemented soon.
this feature conflicts with more advanced logging solutions.

[mopatches]

Looks like this is supported in canary. So when Next v15 comes out we'll be able to use the new option. 🎉

• MR: https://github.com/vercel/next.js/pull/67590/files
• Release: https://github.com/vercel/next.js/releases/tag/v15.0.0-canary.77
• Docs: https://nextjs.org/docs/app/api-reference/next-config-js/logging

Thank you @huozhi ❤️

[the-me-0]

I mean don't get me wrong but I feel like this is not enough. It's already something, agreed, and it might help a handfull of devs, but it would be even better if we could (as mentioned by others before me) disable logs for some routes in particular. I got a /api/auth/session in my project that gets spammed and it just makes the logs difficult to read tbh.

Hope it gets implemented soon.

[huksley]

The worst thing is it does logging even if you use custom server (in development)

I am using this hack, it is horrible but works well.

if (process.env.NODE_ENV === "development") {
      // Omit NextJS writing it's log https://github.com/vercel/next.js/discussions/65992
      const __write = process.stdout.write;
      // @ts-ignore
      process.stdout.write = (...args) => {
        if (
          typeof args[0] !== "string" ||
          !(
            args[0].startsWith(" GET /") ||
            args[0].startsWith(" POST /") ||
            args[0].startsWith(" DELETE /") ||
            args[0].startsWith(" PATCH /")
          )
        ) {
          // @ts-ignore
          __write.apply(process.stdout, args);
        }
      };
    }

[huksley]

Same here. I use custom server (even in development) and I do my own request/response logging when needed. So it gets duplicated with NextJS outputting the log after the response.

[mohsen1]

I took a stab at this. Let me know if the configuration options makes sense to you #74349