Cannot resolve `@sentry/nextjs` on Cloudflare Workers

[logaretm]

Description

Some users reported errors related to @sentry/nextjs not being resolved correctly in Cloudflare Workers runtime.

✘ [ERROR] Could not resolve "@sentry/nextjs"

    .open-next/server-functions/default/.next/server/app/sentry-example-page/page.js:2:9038:
      2 │ ...ve().then(c.bind(c,70704))},77134:a=>{"use strict";a.exports=require("@sentry/nextjs")},80764:(a,b,c)=>{"use strict";c.r(b),c.d(b,{default:()=>d});let d=...
        ╵                                                                         ~~~~~~~~~~~~~~~~

  The module "./build/cjs/edge/index.js" was not found on the file system:

    .open-next/server-functions/default/node_modules/@sentry/nextjs/package.json:39:19:
      39 │         "require": "./build/cjs/edge/index.js",

Workaround

@dispalt reported that the following workaround fixes it:

const nextConfig = {
  pageExtensions: ['js', 'jsx', 'md', 'mdx', 'ts', 'tsx'],
  outputFileTracingIncludes: {
    "*": ["node_modules/@sentry/nextjs/build/**/*"],
  },
// ...
}

User Reports:

• Support Next.js on Cloudflare Workers (OpenNext) #14931 (comment)
• Support Next.js on Cloudflare Workers (OpenNext) #14931 (comment)
• Support Next.js on Cloudflare Workers (OpenNext) #14931 (comment)

---

I didn't manage to reproduce this at all, but it could be something with NFT or specific configurations.

[linear]

JS-1481

[masinette]

Related to: https://sentry.zendesk.com/agent/tickets/172169

[logaretm]

I could not reproduce this yet, for all my testing and deploying on actual cloudflare workers. Then I tried using other package managers like yarn and it failed to build like the user's suggesting, but for a completely different reason leading back to opentelemetry code.

Error: Dynamic require of "util" is not supported
    at file:///private/var/folders/pp/cjdbvd7s5qgdf3sknws0qc300000gn/T/open-next-tmpuqTrEe/next.config.mjs:11:9
    at node_modules/@opentelemetry/instrumentation-http/node_modules/@opentelemetry/core/build/src/platform/node/environment.js (file:///private/var/folders/pp/cjdbvd7s5qgdf3sknws0qc300000gn/T/open-next-tmpuqTrEe/next.config.mjs:20279:18)

I went back to trying pnpm as a package manager gives out the same error but for fs instead

Error: Dynamic require of "fs" is not supported
    at file:///private/var/folders/pp/cjdbvd7s5qgdf3sknws0qc300000gn/T/open-next-tmpfjLfRt/next.config.mjs:11:9
    at node_modules/.pnpm/@sentry+nextjs@10.36.0_@opentelemetry+context-async-hooks@2.5.0_@opentelemetry+api@1.9._642beec2415f4c4ff5b3cf7d656f1188/node_modules/@sentry/nextjs/build/cjs/config/util.js (file:///private/var/folders/pp/cjdbvd7s5qgdf3sknws0qc300000gn/T/open-next-tmpfjLfRt/next.config.mjs:16154:14)

I think it might be something related to wrangler environment in new projects because I didn't get those errors before and it continues to work on one of my old test projects 🤔

The user errors happen at the next build stage rather than Opennext artifact packaging.

---

EDIT: Setting up a new CF worker app with Next.js works well with all package managers, so this seems like a flake or an incorrect setup. Still no reproduction for the original issue.

[Livijn]

I get this error while using a monorepo with pnpm.

[logaretm]

@Livijn Could you reproduce this in a minimal example repo? This can help us resolve this as we aren't sure what might be causing this.