Debugging Grunge Stack

[gnllucena]

Hey, guys!

I'm trying to debug grunge-stack loader and action functions within vscode, I've successfully debug blues-stack and indie-stack just using an plain launch.json settings:

{
  "version": "0.2.0",
  "configurations": [
    {
      "command": "npm run dev",
      "name": "Run npm run dev",
      "request": "launch",
      "type": "node-terminal",
      "cwd": "${workspaceFolder}"
    },
  ]
}

I've seen that @tbeseda (remix-run/grunge-stack#25 (comment)) gives a good explanation to why this happens, but it seems to me that choosing a stack that isn't debuggable nowadays is not a good decision.

Do you guys know any workaround this behavior? Is there anything I can do to debug grunge-stack?

[coanjos]

I was having the same behavior here. Watching this issue for any future answers.

[quantuminformation]

Same issue here, I tried

      "command": "npm run dev",
      "name": "Run npm run dev",
      "request": "launch",
      "type": "node-terminal",
      "cwd": "${workspaceFolder}"
      ```
its prob something special about the lambda mocking, so prob not really a remix issue - what did the lambda docs say about debugging?