Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

expo export: "Chunk containing module not found" for react-native-css components (dual import/require .cjs variants)

Ouverte
  • Quelque chose ne va pas ?
#364 2 commentaires 0 réactions 1 personne assignée Voir sur GitHub

Les mainteneurs répondent en général sous 3 jours

@danstepanov y travaille déjà.

Depuis le 15/7/2026.

Évaluation

Cette issue n'a pas encore été évaluée.

Description

auto-triaged needs-deep-triage v5 stability
Summary

npx expo export (production bundling) fails in Expo's async-chunk serializer with:

AssertionError [ERR_ASSERTION]: Chunk containing module not found:
  node_modules/react-native-css/dist/commonjs/components/index.cjs
    at .../@expo/metro-config/build/serializer/serializeChunks.js:211:42
    at Chunk.getComputedPathsForAsyncDependencies (.../serializeChunks.js:207:19)
    at Chunk.serializeToCode (.../serializeChunks.js:266:44)
    at Chunk.serializeToAssetsAsync (.../serializeChunks.js:290:29)
    ...
    at exportAppAsync (.../@expo/cli/build/src/export/exportApp.js:193:13)

The Metro dev server (expo start) bundles fine. Only expo export (and therefore production / EAS builds) fails.

Repro

It reproduces with a minimal config, so it is not caused by a custom resolver/transformer:

// metro.config.js
const { getDefaultConfig } = require("expo/metro-config");
const { withNativewind } = require("nativewind/metro");
module.exports = withNativewind(getDefaultConfig(__dirname));

npx expo export --platform android

Full repo (it also covers a separate nativewind issue, but the export failure repros directly):
https://github.com/danstepanov/nw-1824-repro → cd apps/mobile && npx expo export -p android

Likely cause

The ./components subpath exports map points the import and require conditions at two different files that share the same basename:

"./components": {
  "source":  "./src/components/index.cts",
  "import":  { "default": "./dist/module/components/index.cjs",   ... },
  "require": { "default": "./dist/commonjs/components/index.cjs", ... }
}

So the same logical module resolves to two distinct absolute paths depending on the active condition (dist/module/components/index.cjs vs dist/commonjs/components/index.cjs). Expo's getComputedPathsForAsyncDependencies looks up the chunk for the commonjs variant but the chunk was built around the module variant, so the assertion fires. (components/index.cjs itself is a set of lazy require() getters; the only importer in the graph is nativewind/dist/.../test-utils.)

A couple of things worth checking:

  • why the ESM (import) condition points to a .cjs file under dist/module/, and whether collapsing both conditions to a single canonical path resolves the chunk lookup;
  • whether test-utils should be reachable from a production graph at all.
Environment
  • expo 56.0.12, react-native 0.85.3, react 19.2.3
  • nativewind 5.0.0-preview.4, react-native-css 3.0.7 (latest stable)
  • @expo/metro-config 56.0.14
  • pnpm 10.8.1 monorepo, nodeLinker: hoisted (also note: minimal config, so not resolver-specific)
Langage dominant
TypeScript
Étoiles
166
Forks
45
Merge moyen
13 j 14 h
PR mergées (30 j)
1

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de nativewind/react-native-css

Toutes les issues de nativewind/react-native-css

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.