nextjs - ✅(Solved) Fix [Turbopack] Import statements are not resolved in the order specified in the resolve extensions config [2 pull requests, 4 comments, 4 participants]

nextjs2026-03-09 21:00:32

ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

GitHub issue URL

Helpful · Quick feedback

GitHub stats

vercel/next.js#91117•Fetched 2026-04-08 00:18:55

View on GitHub

Comments

Participants

Timeline

Reactions

Author

Participants

Timeline (top)

commented ×4referenced ×4cross-referenced ×2subscribed ×2

Error Message

Using Turbopack, the app throws an error while compiling the page because it tries to import React Native code. I assume this happens because it's not resolving the modules using the order specified in the resolve extensions config. The extension web.js should be evaluated before .js since that's the usual way third-party React Native libraries allow for React Native for Web usage.

Root Cause

Fix Action

Fixed

Fixed by PR: test: add e2e test for resolve extensions order in Turbopack (https://github.com/vercel/next.js/pull/91145)
Fixed by PR: fix(turbopack): preserve resolveExtensions priority in read_matches fast path (https://github.com/vercel/next.js/pull/91856)

PR fix notes

PR #91145: test: add e2e test for resolve extensions order in Turbopack

Repository: vercel/next.js
Author: timneutkens
State: open | merged: False
Link: https://github.com/vercel/next.js/pull/91145

Description (problem / solution / changelog)

Fixing a bug

Related issues linked using fixes #number
Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs

What?

Adds an e2e test to verify that Turbopack respects the order specified in the resolveExtensions configuration when resolving import statements.

Why?

Currently, Turbopack does not resolve import statements in the order specified in the resolveExtensions config. When multiple files exist with different extensions (e.g., greeting.js and greeting.web.js), Turbopack should prioritize the extension that appears first in the resolveExtensions array, but it currently doesn't follow this behavior consistently with webpack.

How?

The test creates a scenario where:

Two versions of the same module exist: greeting.js and greeting.web.js
The next.config.js specifies .web.js should be resolved before .js in the resolveExtensions array
Both server-side and client-side components import the module without an extension
The test verifies that the .web.js variant is loaded in both cases

The test includes:

Server component that imports ./greeting (should resolve to greeting.web.js)
Client component that imports ./client-greeting (should resolve to client-greeting.web.js)
Next.js config with Turbopack resolveExtensions putting .web.js before .js
E2e test that checks both server-side rendering and client-side hydration

Fixes #91117

Changed files

test/e2e/app-dir/resolve-extensions-order/app/client-component.tsx (added, +7/-0)
test/e2e/app-dir/resolve-extensions-order/app/client-greeting.js (added, +4/-0)
test/e2e/app-dir/resolve-extensions-order/app/client-greeting.web.js (added, +4/-0)
test/e2e/app-dir/resolve-extensions-order/app/greeting.js (added, +6/-0)
test/e2e/app-dir/resolve-extensions-order/app/greeting.web.js (added, +5/-0)
test/e2e/app-dir/resolve-extensions-order/app/layout.tsx (added, +7/-0)
test/e2e/app-dir/resolve-extensions-order/app/page.tsx (added, +11/-0)
test/e2e/app-dir/resolve-extensions-order/next.config.js (added, +31/-0)
test/e2e/app-dir/resolve-extensions-order/resolve-extensions-order.test.ts (added, +27/-0)

Code Example

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 25.2.0: Tue Nov 18 21:07:05 PST 2025; root:xnu-12377.61.12~1/RELEASE_ARM64_T6020
  Available memory (MB): 16384
  Available CPU cores: 10
Binaries:
  Node: 24.11.1
  npm: 11.6.2
  Yarn: 1.22.22
  pnpm: 10.26.2
Relevant Packages:
  next: 16.2.0-canary.85 // Latest available version is detected (16.2.0-canary.85).
  eslint-config-next: N/A
  react: 19.2.4
  react-dom: 19.2.4
  typescript: 5.9.3
Next.js Config:
  output: N/A

---

const nextConfig: NextConfig = {
  turbopack: {
    resolveAlias: {
      "react-native": "react-native-web",
    },
    resolveExtensions: [
      ".web.js",
      ".web.jsx",
      ".web.ts",
      ".web.tsx",
      ".mdx",
      ".tsx",
      ".ts",
      ".jsx",
      ".js",
      ".mjs",
      ".json",
    ],
    root: __dirname,
  },

  webpack: (config) => {
    config.resolve.alias = {
      ...(config.resolve.alias || {}),
      // Transform all direct `react-native` imports to `react-native-web`
      "react-native$": "react-native-web",
    };
    config.resolve.extensions = [
      ".web.js",
      ".web.jsx",
      ".web.ts",
      ".web.tsx",
      ...config.resolve.extensions,
    ];
    return config;
  },
};

RAW_BUFFERClick to expand / collapse

Link to the code that reproduces this issue

https://github.com/gabrieltrompiz/turbopack-rn-reproduction-app

To Reproduce

Start the application in dev mode (pnpm dev, yarn dev or npm run dev)
Go to localhost:3000 (or whatever port Next is using)

Current vs. Expected behavior

If Webpack is used (with --webpack flag), then the application compiles successfully. I would expect the resolve extensions from Turbopack to work similarly to how Webpack resolve extensions option works.

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 25.2.0: Tue Nov 18 21:07:05 PST 2025; root:xnu-12377.61.12~1/RELEASE_ARM64_T6020
  Available memory (MB): 16384
  Available CPU cores: 10
Binaries:
  Node: 24.11.1
  npm: 11.6.2
  Yarn: 1.22.22
  pnpm: 10.26.2
Relevant Packages:
  next: 16.2.0-canary.85 // Latest available version is detected (16.2.0-canary.85).
  eslint-config-next: N/A
  react: 19.2.4
  react-dom: 19.2.4
  typescript: 5.9.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), next build (local), next start (local)

Additional context

Next config being used:

const nextConfig: NextConfig = {
  turbopack: {
    resolveAlias: {
      "react-native": "react-native-web",
    },
    resolveExtensions: [
      ".web.js",
      ".web.jsx",
      ".web.ts",
      ".web.tsx",
      ".mdx",
      ".tsx",
      ".ts",
      ".jsx",
      ".js",
      ".mjs",
      ".json",
    ],
    root: __dirname,
  },

  webpack: (config) => {
    config.resolve.alias = {
      ...(config.resolve.alias || {}),
      // Transform all direct `react-native` imports to `react-native-web`
      "react-native$": "react-native-web",
    };
    config.resolve.extensions = [
      ".web.js",
      ".web.jsx",
      ".web.ts",
      ".web.tsx",
      ...config.resolve.extensions,
    ];
    return config;
  },
};

extent analysis

Fix: Correct Turbopack resolve configuration

Turbopack does not read the keys resolveAlias / resolveExtensions that Webpack uses.
Instead it expects a nested resolve object (alias + extensions). Because the config was using the wrong shape, Turbopack fell back to its default order (.js before .web.js) and pulled the native RN entry‑points.

1️⃣ Update `next.config.js`

/** @type {import('next').NextConfig} */
const nextConfig = {
  // -----------------------------------------------------------------
  // Turbopack specific options (only used when running with --turbo)
  // -----------------------------------------------------------------
  turbopack: {
    // NOTE:

Vote matrix · Quick signals

Works

Did the solution work? Tap to confirm.

Easy Fix

Was it a quick fix?

Time Saver

Did it save you time?

Blocking

Was it severely blocking?

Common Issue

Are others likely hitting this too?

Flaky / Intermittent

Is it intermittent?

Verified / Reproducible

Can you reproduce it reliably?

#api #ssr #installation #tensor shape #autograd error #API routing #API middleware #SSR setup #ISR setup #authentication setup

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Data

Security

Network

Code

UI/UX

Text

System

Multimedia

Protocol

API

Engineering

nextjs - ✅(Solved) Fix [Turbopack] Import statements are not resolved in the order specified in the resolve extensions config [2 pull requests, 4 comments, 4 participants]

Recommended Tools

GitHub issue graph ai analysis

Error Message

Root Cause

Fix Action

Fixed

PR fix notes

PR #91145: test: add e2e test for resolve extensions order in Turbopack

Description (problem / solution / changelog)

Fixing a bug

What?

Why?

How?

Changed files

Code Example

Link to the code that reproduces this issue

To Reproduce

Current vs. Expected behavior

Provide environment information

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

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

Additional context

extent analysis

Fix: Correct Turbopack resolve configuration

1️⃣ Update `next.config.js`

Still need to ship something?

TRENDING

nextjs - ✅(Solved) Fix [Turbopack] Import statements are not resolved in the order specified in the resolve extensions config [2 pull requests, 4 comments, 4 participants]

Recommended Tools

GitHub issue graph ai analysis

Error Message

Root Cause

Fix Action

Fixed

PR fix notes

PR #91145: test: add e2e test for resolve extensions order in Turbopack

Description (problem / solution / changelog)

Fixing a bug

What?

Why?

How?

Changed files

Code Example

Link to the code that reproduces this issue

To Reproduce

Current vs. Expected behavior

Provide environment information

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

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

Additional context

extent analysis

Fix: Correct Turbopack resolve configuration

1️⃣ Update next.config.js

Still need to ship something?

RELATED_DISCOVERY

TRENDING

1️⃣ Update `next.config.js`