Route "/" used crypto.randomUUID() outside of "use cache" and without explicitly calling await connection() beforehand.

[TheCukitoDev]

Link to the code that reproduces this issue

https://github.com/TheCukitoDev/blog

To Reproduce

1. Fill the env variables
2. Run pnpm run dev:turbo
3. Open localhost:3000

Current vs. Expected behavior

I think this shouldn't happen because i don't use any crypto.randomUUID() in my project or at least in my code i don't know if it happens in the node_modules but i think yes.

It should work well. I only get some Cosmos DB data...

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
  Available memory (MB): 16088
  Available CPU cores: 16
Binaries:
  Node: 20.15.1
  npm: 10.7.0
  Yarn: N/A
  pnpm: 9.12.3
Relevant Packages:
  next: 15.0.4-canary.14 // There is a newer canary version (15.0.4-canary.15) available, please upgrade!
  eslint-config-next: 15.0.3
  react: 19.0.0-rc-380f5d67-20241113
  react-dom: 19.0.0-rc-380f5d67-20241113
  typescript: 5.6.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Turbopack, Webpack

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

I tested it in Next.js 15.0.4-canary.14 (Turbopack) ,Next.js 15.0.4-canary.14 (Webpack) ,Next.js 15.0.4-canary.15 (Turbopack) and Next.js 15.0.4-canary.15 (Webpack) and it is the same error in the turbopack ones and the same one in the webpack ones but different between the turbopack ones and the webpack ones. I think the error comes from sentry because i don't receive the errors in sentry but it worked before so I don't know what happened