[NEXT-1100] unhandledRejection: Error [TypeError]: trace.getSpan is not a function

[dossy]

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
      Platform: darwin
      Arch: x64
      Version: Darwin Kernel Version 20.6.0: Sun Nov  6 23:17:00 PST 2022; root:xnu-7195.141.46~1/RELEASE_X86_64
    Binaries:
      Node: 18.12.1
      npm: 9.3.1
      Yarn: 1.22.19
      pnpm: N/A
    Relevant packages:
      next: 13.3.1-canary.2
      eslint-config-next: 13.3.0
      react: 18.2.0
      react-dom: 18.2.0

Which area(s) of Next.js are affected? (leave empty if unsure)

CLI (create-next-app)

Link to the code that reproduces this issue

https://github.com/dossy/nextjs-trace-getSpan-is-not-a-function

To Reproduce

Provided by #48118 (comment)

reproduce with a yarn workspaces monorepo.

Check this one out here: jamesopti/next-tracespan-error-reproduction

The packages/server has "@opentelemetry/api": "^0.18.1"

The packages/client is a brand new create next app.

Describe the Bug

Trying to access the app results in an unhandledRejection: Error [TypeError]: trace.getSpan is not a function error:

$ yarn dev
yarn run v1.22.19
$ next dev
warn  - Port 3000 is in use, trying 3001 instead.
ready - started server on 0.0.0.0:3001, url: http://localhost:3001
(node:53803) ExperimentalWarning: The Fetch API is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
event - compiled client and server successfully in 1821 ms (170 modules)
wait  - compiling / (client and server)...
event - compiled client and server successfully in 467 ms (217 modules)
error - unhandledRejection: Error [TypeError]: trace.getSpan is not a function
    at NextTracerImpl.getActiveScopeSpan ([REDACTED]/create-next-app-sample/node_modules/next/dist/server/lib/trace/tracer.js:50:22)
    at NextTracerImpl.trace ([REDACTED]/create-next-app-sample/node_modules/next/dist/server/lib/trace/tracer.js:69:103)
    at DevServer.handleRequest ([REDACTED]/create-next-app-sample/node_modules/next/dist/server/base-server.js:166:41)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async DevServer.handleRequest ([REDACTED]/create-next-app-sample/node_modules/next/dist/server/dev/next-dev-server.js:839:16) {
  digest: undefined
}

Expected Behavior

The home page should render in the browser.

Which browser are you using? (if relevant)

Chrome Version 111.0.5563.146 (Official Build) (x86_64)

How are you deploying your application? (if relevant)

locally

_{From SyncLinear.com | NEXT-1100}

[dossy]

#46632

[ndpa]

This also worked for me to resolve this issue as per #46632 / yarn add @opentelemetry/api @opentelemetry/resources @opentelemetry/semantic-conventions @opentelemetry/sdk-trace-node @opentelemetry/instrumentation

But, it seems very odd to me that I would need to do this. Please let me know if a better solution appears.

[pgsandstrom]

I am running into this problem when upgrading my next-apps from 12 to 13. It only happens in production. In development mode, everything works perfectly.

[jamesopti]

Trying to upgrade to the latest 13.4 and getting this error.

Any response from the next team? Seems odd that consumers would need to install opentelemetry themselves 🤔

[jamesopti]

It appears that @opentelemetry/api is a peerDependency now, but the docs dont indicate as much: https://github.com/vercel/next.js/blob/v13.4.1/packages/next/package.json#L95

[huozhi]

@jamesopti There's a built-in version of opentelementry by default, it should work even you didn't install it.

I can't repro the error with latest version 13.4.1 with origin reproduction post in the issue description. Could you post another reproduction for this if you're still seeing the error?

[jamesopti]

We're using a monorepo where the client package is nextjs. Our server package requires @opentelemetry/api. Is it possible this is causing a conflict?

Additionally, why is @opentelemetry/api listed as a peer dependency? That sure seems like what is causing the problem here.

➜  client git:(main) yarn why @opentelemetry/api
├─ @opentelemetry/instrumentation-express@npm:0.16.0
│  └─ @opentelemetry/api@npm:1.0.0-rc.3 (via npm:^1.0.0-rc.0)
│
└─ server@workspace:packages/server
   └─ @opentelemetry/api@npm:0.18.1 (via npm:^0.18.1)

[jamesopti]

FWIW, this issue was introduced in 13.4.0

13.3.4 does not have this problem.

EDIT: 13.1 does not have this issue, but 13.3.4 does

[huozhi]

The different version could be possible reason, could you try add resolution in package.json to lock its version to one, we'll investigate the issue at the same time