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
I have a typescript webpack project running on WSL serving on the following addresses:
<i> [webpack-dev-server] Project is running at:
<i> [webpack-dev-server] Loopback: http://localhost:8080/
<i> [webpack-dev-server] On Your Network (IPv4): http://172.23.198.163:8080/
I can access both addresses, but debug breakpoints will not bind when accessing the page through the localhost url. When I restart the debug session using the network url, the breakpoints do bind. This is an issue not only for network access reasons, but because certain web APIs cannot be accessed in insecure contexts (e.g. crypto.subtle)
This is only an issue when serving from WSL. When running the project from a normal windows environment both urls work fine.
The Chrome debugger does not have this issue with WSL.
This issue is only with breakpoints in vscode. The browser debugger works fine. Source maps are being loaded.
I have a typescript webpack project running on WSL serving on the following addresses:
I can access both addresses, but debug breakpoints will not bind when accessing the page through the
localhost
url. When I restart the debug session using the network url, the breakpoints do bind. This is an issue not only for network access reasons, but because certain web APIs cannot be accessed in insecure contexts (e.g.crypto.subtle
)This is only an issue when serving from WSL. When running the project from a normal windows environment both urls work fine.
The Chrome debugger does not have this issue with WSL.
This issue is only with breakpoints in vscode. The browser debugger works fine. Source maps are being loaded.
The text was updated successfully, but these errors were encountered: