I have an extremely simple Node script that I need to run when I hit an API route, but it errors out when I do; running the same code with node script.ts works perfectly.

I'm using Next 14 on the app router. The simplest repro code as a Next API Route for this is:

import { SourceMapConsumer } from "source-map";


export async function GET() {
  const sourceMap = {...} // json object representing a sourcemap.
  const consumer = await new SourceMapConsumer(sourceMap); // this line fails.
  return new NextResponse(
    JSON.stringify({ message: "Success" }),
    {
      status: 200,
      headers: {
        "Content-Type": "application/json",
      },
    }
  );
}

Hitting this endpoint throws a "mappings.wasm" not found error; this error is only expected in a Browser environment!:

 ⨯ [Error: ENOENT: no such file or directory, open '/Users/.../my_app/.next/server/vendor-chunks/mappings.wasm'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/Users/.../my_app/.next/server/vendor-chunks/mappings.wasm'
}

This same code, when copy pasted into a separate file and I run node script.ts works perfectly.

I think this is because NextJS is not running this code as classic node or something like that. In a browser environment SourceMapConsumer needs to be called with an argument for the wasm file; and explicitly not in a Node environment. (https://github.com/mozilla/source-map?tab=readme-ov-file#new-sourcemapconsumerrawsourcemap)

Please help!