Using the latest version still results in errors

[ZRR641182473]

Using the latest version still results in errors

Error: Cannot find module '@jridgewell/sourcemap-codec' at webpackEmptyContext (main.js:363158:10) at eval (main.js:362903:30) at eval (main.js:362813:13) at ./node_modules/@jridgewell/gen-mapping/dist/gen-mapping.umd.js (main.js:362815:3)

[jridgewell]

What version of node? What are the versions of the packages in node_modules/@jridgewell/*?

[ZRR641182473]

node -v: 22.14.0,

[thucpn]

I got the same issue with Babel

../../../../../@jridgewell+trace-mapping@0.3.27/node_modules/@jridgewell/trace-mapping/dist/trace-mapping.umd.js
Critical dependency: require function is used in a way in which dependencies cannot be statically extracted


Import trace for requested module:
../../../../../@jridgewell+trace-mapping@0.3.27/node_modules/@jridgewell/trace-mapping/dist/trace-mapping.umd.js
../../../../../@babel+generator@7.27.5/node_modules/@babel/generator/lib/source-map.js
../../../../../@babel+generator@7.27.5/node_modules/@babel/generator/lib/index.js
../../../../../@babel+traverse@7.27.7/node_modules/@babel/traverse/lib/path/index.js
../../../../../@babel+traverse@7.27.7/node_modules/@babel/traverse/lib/index.js

[guoyunhe]

Same here with vite...

setupDocs.ts:1 foobar
chunk-Y2RXA2XT.js?v=550cbfcf:11 Uncaught Error: Dynamic require of "@jridgewell/sourcemap-codec" is not supported
    at chunk-Y2RXA2XT.js?v=550cbfcf:11:9
    at gen-mapping.ts:6:8
    at index.js:77:3
    at node_modules/@jridgewell/gen-mapping/dist/gen-mapping.umd.js (index.js:77:3)
    at __require2 (chunk-Y2RXA2XT.js?v=550cbfcf:17:50)
    at computeSourceMap.js:1:57
（匿名） @ chunk-Y2RXA2XT.js?v=550cbfcf:11
（匿名） @ gen-mapping.ts:6
（匿名） @ index.js:77
node_modules/@jridgewell/gen-mapping/dist/gen-mapping.umd.js @ index.js:77
__require2 @ chunk-Y2RXA2XT.js?v=550cbfcf:17
（匿名） @ computeSourceMap.js:1
css-generic.js:236 uBOL: Generic cosmetic filtering stopped because no more DOM changes

[jamesalphanome]

Same here with Sucrase...

node -- v22.16.0

[xiaoboost]

In my webpack configuration, I set resolve.mainFields = ["module", "main"], but I noticed the final bundled code still uses the UMD version.
I've temporarily resolved this by forcing aliases to point to the ESM versions:

resolve.alias["@jridgewell/gen-mapping"] = path.resolve(__dirname, "../node_modules", "@jridgewell/gen-mapping/dist/gen-mapping.mjs");
resolve.alias["@jridgewell/sourcemap-codec"] = path.resolve(__dirname, "../node_modules", "@jridgewell/sourcemap-codec/dist/sourcemap-codec.mjs");
resolve.alias["@jridgewell/trace-mapping"] = path.resolve(__dirname, "../node_modules", "@jridgewell/trace-mapping/dist/trace-mapping.mjs");

---

After examining several libraries' package.json files, I discovered what appears to be an error in their exports configuration:

{
  "exports": {
    ".": [
      {
        "browser": {
          "types": "./types/source-map.d.cts",
          "default": "./dist/source-map.umd.js"
        },
        "require": {
          "types": "./types/source-map.d.cts",
          "default": "./dist/source-map.umd.js"
        },
        "import": {
          "types": "./types/source-map.d.mts",
          "default": "./dist/source-map.mjs"
        }
      },
      "./dist/source-map.umd.js"
    ],
    "./package.json": "./package.json"
  }
}

I recall that in Node.js conditional exports, when using the array format, the values of item object must be strings.

Might be caused by this commit:
a924ed3

so, i think the array should be removed.
The correct configuration should be:

{
  "exports": {
    ".": {
      "browser": {
        "types": "./types/source-map.d.cts",
        "default": "./dist/source-map.umd.js"
      },
      "require": {
        "types": "./types/source-map.d.cts",
        "default": "./dist/source-map.umd.js"
      },
      "import": {
        "types": "./types/source-map.d.mts",
        "default": "./dist/source-map.mjs"
      },
      "default": "./dist/source-map.umd.js"
    },
    "./package.json": "./package.json"
  }
}

[stefanpejcic]

same error here with docusaurus on nodejs20, noticed my vercel deployments started erroring today

[F-jianchao]

Hello, has the issue been fixed now? It still reports an error in Vite

[gabrielmfern]

Also seeing this issue when trying to use babel inside a Next.js app. What change has caused this exactly?

[jridgewell]

I'm working on the fix now. Webpack apparently doesn't like my UMD wrapper. In the meantime, you can pin old versions:

// package.json
"dependencies": {
    "@jridgewell/gen-mapping": "0.3.8",
},
"overrides": {
    "@jridgewell/gen-mapping": "0.3.8"
}