Build fails to compile - module not found: can't resolve "child_process" 12.1.6

[wadehammes]

Verify canary release

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

Provide environment information

Operating System:
Platform: linux
Arch: x64
Version: #1 SMP Wed Mar 2 00:30:59 UTC 2022
Binaries:
Node: 14.18.1
npm: 6.14.15
Yarn: 1.22.18
pnpm: N/A
Relevant packages:
next: 12.1.6
react: 18.1.0
react-dom: 18.1.0

What browser are you using? (if relevant)

Firefox

How are you deploying your application? (if relevant)

Vercel

Describe the Bug

In the latest 12.1.6, I can't get my site to compile on Vercel. Everything works fine in previous release. See log below. I am not sure if this is a Sentry issue or an issue with next.

Expected Behavior

Site compiles like in 12.1.5

To Reproduce

Have a next site set up with Sentry initiated at webpack level.

[balazsorban44]

Related: #36486, #36434

Note that you should not use Node-specific APIs in your Middleware as it uses the Edge Runtime. (See the docs: https://nextjs.org/docs/api-reference/edge-runtime#unsupported-apis).

Sentry does not seem to be compatible at the moment.

Maybe related #36237 (comment)

Could you add a small reproduction to verify?

[wadehammes]

Sentry works fine in middleware in 12.1.5 @balazsorban44 wondering what changed?

[wadehammes]

These nextRuntime does not work for me in #36237

[sergeyshaykhullin]

It also break axios usage inside _middleware

experimental: {
  runtime: 'nodejs'
},

Doesn't help ;\

error - ./node_modules/axios/lib/helpers/toFormData.js:26:0
Module not found: Can't resolve 'buffer'

Import trace for requested module:
./node_modules/axios/lib/axios.js
./node_modules/axios/index.js
./src/api/index.ts
./src/pages/_middleware.ts

https://nextjs.org/docs/messages/module-not-found

You're using a Node.js module (buffer) which is not supported in the Edge Runtime.
Learn more: https://nextjs.org/docs/api-reference/edge-runtime

[liamross]

Seems to be breaking Prisma, Upstash, etc within Middleware files, not sure if this is a new "stricter" middleware setup or if the version is broken.

[balazsorban44]

Sentry works fine in middleware in 12.1.5 @balazsorban44 wondering what changed?

So up until recently, we have polyfilled a few Node.js APIs even for the Edge Runtime. This has been changed in #36190 as it was the original intention as documented: https://nextjs.org/docs/api-reference/edge-runtime#unsupported-apis

Any library relying on that did so by mistake.

[balazsorban44]

@sergeyshaykhullin the switchable runtime does not concern Middleware, we added a note about this in the docs to make it more clear: #36862

Also in the Middleware docs there is this:

Middleware uses a strict runtime

So this should explain your situation. I'm closing this as the result is expected. A final word on Sentry, they don't have official Middleware support yet: getsentry/sentry-javascript#4206