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
Evaluating web pack bundles like dcp-client makes for horrifyingly bad stack traces if we don't have external source map support.
This can be avoided in dcp-client by building a debug bundle which uses internal source maps, but that's not the common case with code found in the wild.
I believe I added an options argument to pm.eval. I suggest adding an option which is the path to the sourcemap file.
Code example
No response
The text was updated successfully, but these errors were encountered:
External source map support seems limited to passing a URL through from JS::Compile to the script object, where in firefox it is extracted JS debugger, and parsed in userland (I think)
Describe your feature request here.
Evaluating web pack bundles like dcp-client makes for horrifyingly bad stack traces if we don't have external source map support.
This can be avoided in dcp-client by building a debug bundle which uses internal source maps, but that's not the common case with code found in the wild.
I believe I added an options argument to
pm.eval
. I suggest adding an option which is the path to the sourcemap file.Code example
No response
The text was updated successfully, but these errors were encountered: