Log internal server errors during development by default

Currently, I’m using the following code snippet for Next.js at the api/trpc/[trpc] route:

import * as trpcNext from "@trpc/server/adapters/next";

const __DEV__ = process.env.NODE_ENV !== "production";

export default trpcNext.createNextApiHandler({
  router: appRouter,
  createContext,
  onError: __DEV__
    ? ({ error, type, path, input }) => {
        if (error.code === "INTERNAL_SERVER_ERROR") {
          // eslint-disable-next-line no-console
          console.error("Error:", {
            type,
            path,
            input,
            cause: error.originalError,
          });
        }
      }
    : undefined,
});

I think it would be useful to always log unhandled errors (where error.code === "INTERNAL_SERVER_ERROR") to the server’s console like this during development, even when no onError is specified.

[KATT]

I love that you have so many ideas for improvements, if you need any guidance on how to contribute, let me know!

[kripod]

Why wouldn’t you want to do this in prod?

Maybe a default logger for development would be useful - feel free to make a PR!

The reason why I wouldn’t emit messages to the console is that HTTP responses will already have an error code of 500, which Vercel and other logging services keep track of. The message about the error returned in production already contains enough information to investigate on.

I’ll try creating some PRs soon – work makes me pretty busy nowadays, sorry about that.