Does node.js support sectioned source maps? (Chrome Inspector supports it)

[kdy1]

I'm working on vercel/turborepo#7284 and I found some problems with the --enable-source-maps of node.js

The exception stack trace looks like

Error: boom
    at fn2 (/Users/kdy1/projects/nextpack/next.js/test/development/app-render-error-log/.next/server/chunks/[project]__0e0766._.js:174:11)
    at beforeExport (/Users/kdy1/projects/nextpack/next.js/test/development/app-render-error-log/.next/server/chunks/[project]__0e0766._.js:177:5)
    at afterExport (/Users/kdy1/projects/nextpack/next.js/test/development/app-render-error-log/.next/server/chunks/[project]__0e0766._.js:183:5)
    at Module.fn1 (/Users/kdy1/projects/nextpack/next.js/test/development/app-render-error-log/.next/server/chunks/[project]__0e0766._.js:180:5)
    at Page (/Users/kdy1/projects/nextpack/next.js/test/development/app-render-error-log/.next/server/chunks/[project]__0e0766._.js:197:173)
    at attemptResolveElement (webpack://next/dist/compiled/react-server-dom-turbopack/cjs/react-server-dom-turbopack-server.edge.development.js:1704:18)
    at resolveModelToJSON (webpack://next/dist/compiled/react-server-dom-turbopack/cjs/react-server-dom-turbopack-server.edge.development.js:2051:21)
    at Array.toJSON (webpack://next/dist/compiled/react-server-dom-turbopack/cjs/react-server-dom-turbopack-server.edge.development.js:2278:1)
    at stringify (<anonymous>)
    at emitModelChunk (webpack://next/dist/compiled/react-server-dom-turbopack/cjs/react-server-dom-turbopack-server.edge.development.js:2393:14)
    at retryTask (webpack://next/dist/compiled/react-server-dom-turbopack/cjs/react-server-dom-turbopack-server.edge.development.js:2397:1)
    at performWork (webpack://next/dist/compiled/react-server-dom-turbopack/cjs/react-server-dom-turbopack-server.edge.development.js:2484:7)
    at Timeout._onTimeout (webpack://next/dist/compiled/react-server-dom-turbopack/cjs/react-server-dom-turbopack-server.edge.development.js:1775:14)
    at listOnTimeout (node:internal/timers:569:17)
    at process.processTimers (node:internal/timers:512:7)

and it means the source map file is not applied.

But we have relevant source map entry.

// .sections of /Users/kdy1/projects/nextpack/next.js/test/development/app-render-error-log/.next/server/chunks/[project]__0e0766._.js.map:

{
      "offset": {
        "line": 169,
        "column": 0
      },
      "map": {
        "version": 3,
        "sources": [
          "/turbopack/[project]/test/development/app-render-error-log/app/fn.ts"
        ],
        "sourcesContent": [
          "function fn2() {\n  throw new Error('boom')\n}\n\nfunction beforeExport() {\n  fn2()\n}\n\nexport function fn1() {\n  afterExport()\n}\n\nfunction afterExport() {\n  beforeExport()\n}\n"
        ],
        "names": [],
        "mappings": ";;;AAAA,SAAS;IACP,MAAM,IAAI,MAAM;AAClB;AAEA,SAAS;IACP;AACF;AAEO,SAAS;IACd;AACF;AAEA,SAAS;IACP;AACF"
      }
    },

I tried using Chrome Inspector, and I found that it's using source maps correctly.

If I throw an exception from the stopped line using the console, I get the correct stack trace on the debugger and the wrong stack trace on the terminal.