Vercel / Deployment

Vercel deploy MIDDLEWARE_INVOCATION_FAILED + Cannot find module @swc/helpers — Next.js 16.2.x + proxy.ts middleware regression

Fix HTTP 500 MIDDLEWARE_INVOCATION_FAILED on Vercel production deployment caused by @swc/helpers module resolution failure when using Next.js 16.2.x App Router with proxy.ts middleware convention and Sentry installed Includes evidence for Vercel troubleshooting demand.

Source-backed Last updated May 17, 2026 2 sources Needs local verification

Category: Deployment
Error signature: MIDDLEWARE_INVOCATION_FAILED: Cannot find module '/var/task/node_modules/@swc/helpers/esm/_interop_require_default.js' — next@16.2.x + proxy.ts + @sentry/nextjs
Quick fix: Check the build output, project root, and deployment platform configuration before redeploying.
Updated: May 17, 2026
Verification status: Source-backed
Evidence: 2 public source URLs

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for Vercel, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

MIDDLEWARE_INVOCATION_FAILED: Cannot find module '/var/task/node_modules/@swc/helpers/esm/_interop_require_default.js' — next@16.2.x + proxy.ts + @sentry/nextjs is a Vercel failure pattern reported for developers trying to fix http 500 middleware_invocation_failed on vercel production deployment caused by @swc/helpers module resolution failure when using next.js 16.2.x app router with proxy.ts middleware convention and sentry installed. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub vercel/next.js issues #93852 (#93850) reported May 2026 with minimal repro. Local build succeeds but Vercel deploy fails with HTTP 500. Blocking production deployments for teams using Next.js 16.2.x + sentry. Not in covered-errors (only generic 'Vercel build failed' exists, this is a specific deployment/runtime error). Category: Deployment.

Common causes

GitHub vercel/next.js issues #93852 (#93850) reported May 2026 with minimal repro. Local build succeeds but Vercel deploy fails with HTTP 500. Blocking production deployments for teams using Next.js 16.2.x + sentry. Not in covered-errors (only generic 'Vercel build failed' exists, this is a specific deployment/runtime error). Category: Deployment.

Quick fixes

Confirm the exact error signature matches MIDDLEWARE_INVOCATION_FAILED: Cannot find module '/var/task/node_modules/@swc/helpers/esm/_interop_require_default.js' — next@16.2.x + proxy.ts + @sentry/nextjs.
Check the Vercel account, local tool state, and provider configuration involved in the failing workflow.
Check the build output, project root, and deployment platform configuration before redeploying.

Platform/tool-specific checks

Verify the command, editor, extension, or API client that produced the error.
Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
Keep the working fix documented for the team or deployment environment.

How to prevent it

Keep provider/tool configuration documented.
Record non-secret diagnostics such as tool version, provider name, model name, and command path.
Add a lightweight check before CI or production workflows depend on the tool.

Diagnostic flow for this page

Match MIDDLEWARE_INVOCATION_FAILED: Cannot find module '/var/task/node_modules/@swc/helpers/esm/_interop_require_default.js' — next@16.2.x + proxy.ts + @sentry/nextjs exactly before applying the quick fix.
Compare the failing environment with Vercel versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does MIDDLEWARE_INVOCATION_FAILED: Cannot find module '/var/task/node_modules/@swc/helpers/esm/_interop_require_default.js' — next@16.2.x + proxy.ts + @sentry/nextjs mean in Vercel?

MIDDLEWARE_INVOCATION_FAILED: Cannot find module '/var/task/node_modules/@swc/helpers/esm/_interop_require_default.js' — next@16.2.x + proxy.ts + @sentry/nextjs indicates the workflow described by "Vercel deploy MIDDLEWARE_INVOCATION_FAILED + Cannot find module @swc/helpers — Next.js 16.2.x + proxy.ts middleware regression" failed in a Deployment context. Start by confirming the exact signature and the component that emitted it.

What should I check first for MIDDLEWARE_INVOCATION_FAILED: Cannot find module '/var/task/node_modules/@swc/helpers/esm/_interop_require_default.js' — next@16.2.x + proxy.ts + @sentry/nextjs?

Check whether this cause matches your environment: GitHub vercel/next.js issues #93852 (#93850) reported May 2026 with minimal repro. Local build succeeds but Vercel deploy fails with HTTP 500. Blocking production deployments for teams using Next.js 16.2.x + sentry. Not in covered-errors (only generic 'Vercel build failed' exists, this is a specific deployment/runtime error). Category: Deployment.

Is the MIDDLEWARE_INVOCATION_FAILED: Cannot find module '/var/task/node_modules/@swc/helpers/esm/_interop_require_default.js' — next@16.2.x + proxy.ts + @sentry/nextjs guidance source-backed?

The "Vercel deploy MIDDLEWARE_INVOCATION_FAILED + Cannot find module @swc/helpers — Next.js 16.2.x + proxy.ts middleware regression" page is labeled source-backed. It has 2 public source URLs from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for MIDDLEWARE_INVOCATION_FAILED: Cannot find module '/var/task/node_modules/@swc/helpers/esm/_interop_require_default.js' — next@16.2.x + proxy.ts + @sentry/nextjs?

For "Vercel deploy MIDDLEWARE_INVOCATION_FAILED + Cannot find module @swc/helpers — Next.js 16.2.x + proxy.ts middleware regression", avoid applying "Check the build output, project root, and deployment platform configuration before redeploying." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging MIDDLEWARE_INVOCATION_FAILED: Cannot find module '/var/task/node_modules/@swc/helpers/esm/_interop_require_default.js' — next@16.2.x + proxy.ts + @sentry/nextjs?

For "Vercel deploy MIDDLEWARE_INVOCATION_FAILED + Cannot find module @swc/helpers — Next.js 16.2.x + proxy.ts middleware regression", collect the failing Vercel command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.