You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Sourcemaps for Amplify packages refer to invalid paths that existed at build time but don't exist when packages are installed from npm. This in turn breaks debugging in VSCode and other IDEs.
To Reproduce
Steps to reproduce the behavior:
npm i aws-amplify
open ./node_modules/aws-amplify/dist/aws-amplify.js.map
Excerpt the first few lines, adding line-breaks and indenting for clarity.
Expected behavior
According to https://github.com/Microsoft/vscode-chrome-debug#sourcemaps, for VSCode to resolve these paths, they should either be relative to the current folder or should be absolute project-relative paths (starting with webpack:///./node_modules/). Like this:
Describe the bug
Sourcemaps for Amplify packages refer to invalid paths that existed at build time but don't exist when packages are installed from npm. This in turn breaks debugging in VSCode and other IDEs.
To Reproduce
Steps to reproduce the behavior:
npm i aws-amplify
./node_modules/aws-amplify/dist/aws-amplify.js.map
Expected behavior
According to https://github.com/Microsoft/vscode-chrome-debug#sourcemaps, for VSCode to resolve these paths, they should either be relative to the current folder or should be absolute project-relative paths (starting with
webpack:///./node_modules/
). Like this:Actual behavior
Paths cannot be resolved by VSCode debugger because they don't exist after install from npm.
I'm working on a PR to fix this.
The text was updated successfully, but these errors were encountered: