aws-sam-webpack-plugin Debugging is broken with VS Code 1.60.0

It looks like VS Code 1.60.0 has made changes that have broken debugging. This needs to be fixed.

Sep 10 '21 10:09 buggy

It looks like VS Code 1.60.0 has problems. Debugging and source maps seem to be broken in general. I found an issue suggesting they might do a 1.60.1 release to fix this. Once that's done I'll look into debugging again.

Sep 10 '21 13:09 buggy

Hi @buggy, is there any chance you were able to look into the problem? Could you share the ticket you found?

Oct 25 '21 13:10 xdsl34

I think this was perhaps the issue previously referred to? https://github.com/microsoft/vscode/issues/133310

Dec 18 '21 01:12 AndrewZelaya

If anyone else comes across this issue this post https://blog.many-monkeys.com/debugging-lambdas-in-vscode/ helped me solve the issue for any vsCode versions above 1.60

The key is modifying your output block in webpack.config as such

output: {
    devtoolModuleFilenameTemplate: '[absolute-resource-path]',
}

Sep 23 '22 05:09 lee-wilkins

If anyone else comes across this issue this post https://blog.many-monkeys.com/debugging-lambdas-in-vscode/ helped me solve the issue for any vsCode versions above 1.60

The key is modifying your output block in webpack.config as such
output: {
    devtoolModuleFilenameTemplate: '[absolute-resource-path]',
}

I tried it with Vscode 1.88.1 and it worked fine. Thank you very much.

Apr 28 '24 02:04 akycop