In Development mode for next.js (npm run dev), errors within getServerSideProps, which are supposed to occur solely in the node.js runtime, are inaccurately reported by Sentry as originating from the Browser. This means that any changes made to the server-side scope are not reflected in the trace.

This anomaly might stem from a Next.js feature that catches and displays server-side errors and stack-traces in the browser to assist development. It seems Next.js intercepts the error before Sentry has a chance to detect it.

However, when the application is built and executed in Production mode (npm run start), these same errors are accurately attributed to the node.js environment.