Incorrect sourceMappingURL added to generated server bundle prevents debugging

Updated my gist with patch to use sourcemap: 'inline'. This solves the issue.

Here’s the gist: https://gist.github.com/kiliman/a9d7c874af03369a1d105a92560d89e9

[connor4312]

By the way, you can also make breakpoints work by doing something like this in your launch.json within VS Code:

    {
      "type": "node-terminal",
      "request": "launch",
      "name": "Launch Server",
      "command": "npm run dev:remix",
      "skipFiles": ["<node_internals>/**"],
      "sourceMapPathOverrides": {
        "route:*": "*" // <-- fix up the paths, so route:<path> just becomes <path>
      },
      "outFiles": ["${workspaceFolder}/build/**/*.js"]
    },

    {
      "name": "Launch Client",
      "request": "launch",
      "type": "msedge",
      "url": "http://localhost:3000",
      "webRoot": "${workspaceFolder}/public/build" // tell the debugger that relative sourcemaps paths should be resolved from here
    }

Aside from having to fix the route: this is fairly ‘idiomatic’, though not easy to discover unless you’re a sourcemapexpert… https://github.com/microsoft/vscode-js-debug/issues/1214

[kiliman]

@heiso Are you on the latest Remix? Sourcemaps should automatically generate in development. You have to opt-in to sourcemaps for production remix build --sourcemap

They removed the sourcemap option in remix.config