Turbopack error on edge runtime(middleware): Error [TypeError]: _react.default.createContext is not a function

[chungweileong94]

Link to the code that reproduces this issue

https://github.com/chungweileong94/turbopack-edge-error-bug

To Reproduce

1. Start the app
2. Open the app in the browser

Current vs. Expected behavior

Expected:

• Turbopack should be able to build the code without any issue

Current:

• Turbopack throw Error [TypeError]: _react.default.createContext is not a function

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.5.0: Wed May  1 20:16:51 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T8103
  Available memory (MB): 16384
  Available CPU cores: 8
Binaries:
  Node: 20.11.1
  npm: 10.2.4
  Yarn: 1.22.21
  pnpm: 8.15.7
Relevant Packages:
  next: 14.3.0-canary.80 // Latest available version is detected (14.3.0-canary.80).
  eslint-config-next: N/A
  react: 19.0.0-beta-04b058868c-20240508
  react-dom: 19.0.0-beta-04b058868c-20240508
  typescript: 5.1.3
Next.js Config:
  output: N/A

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

Turbopack

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

next dev (local)

Additional context

I'm not exactly sure which part of the codebase is causing the issue. However, I either removed the middleware, or removed everything related to next-auth from the middleware, and everything works fine again.

Note that the code works fine without Turbopack, and it used to work with Turbopack in the previous nextjs version.

[fernandojbf]

In my project, the issue appears with Webpack using next-intl

[fernandojbf]

@timneutkens using webpack, i continue to see the same issue:

[OlegLustenko]

the same issue

[timneutkens]

Please open a new issue with a reproduction. It's expected that createContext is not available in middleware / route handlers, they're bundled in the same way as server components nowadays to ensure that things like client-only / server-only work correctly.

[jeslenbucci]

This just began happening to me as well after upgrading to next@15 RC and adding middleware. I am not creating a context within the middleware. My context is in a client component with 'use client' at the top of the file. Everything was working fine, and still does, unless I add middleware.ts to the root of my src/ directory.

[jeslenbucci]

For me, it appears this is an issue with AuthJS v5. If I remove authJS and throw in the middleware example found in the next docs (see below), the createContext is not a function log no longer appears.

My middleware without AuthJS (no error)

import { NextResponse } from 'next/server'
import type { NextRequest } from 'next/server'

// This function can be marked `async` if using `await` inside
export function middleware(request: NextRequest) {
  return NextResponse.redirect(new URL('/sign-in', request.url))
}

// See "Matching Paths" below to learn more
export const config = {
  matcher: [
    '/dashboard/',
    '/account/:path*',
    '/dashboard/:path*',
    '/memberships/:path*',
    '/api/v2/:path*',
  ],
}

My middlewar with AuthJS (error)

export { auth as middleware } from '~/server/auth'

// See "Matching Paths" below to learn more
export const config = {
  matcher: [
    '/dashboard/',
    '/account/:path*',
    '/dashboard/:path*',
    '/memberships/:path*',
    '/api/v2/:path*',
  ],
}

[fernandojbf]

Please open a new issue with a reproduction. It's expected that createContext is not available in middleware / route handlers, they're bundled in the same way as server components nowadays to ensure that things like client-only / server-only work correctly.

I can observe that i was using a dependency on the middleware that was using react context. removing that dependency made it working again Thanks

[liuhuapiaoyuan]

How to solve it in the end?

[kyb3r]

my issue is with authjs v5 as well, any workaround?

[chungweileong94]

@liuhuapiaoyuan @kyb3r The latest canary version should resolved this. Fixed in https://github.com/vercel/next.js/releases/tag/v14.3.0-canary.81 to be specific.

[timneutkens]

As said above: please open a new issue with a reproduction.

Then we can have a look 🙂