-
Notifications
You must be signed in to change notification settings - Fork 758
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
process: replace json-rpc2 with vscode-jsonrpc #113
Comments
We depend on json-rpc2 for the debugging feature that is provided by this extension which in turn depends on v3 of lodash resulting in the above warnings. Unfortunately, json-rpc2 has not had a release in years. One option would be to fork the package and update the dependency ourselves. We could try and see if the vscode-jsonrpc can be a good replacement here cc @quoctruong |
Change https://golang.org/cl/241557 mentions this issue: |
This was part of https://go-review.googlesource.com/c/vscode-go/+/241041 but we are submitting it as a separate cl. Fixes issues reported by security issues reported by npm audit. npm install --save json-rpc2 npm update lodash --depth 3 json-rpc2@2.0.0 was released recently, so instead of switching to vscode-jsonrpc, we are updating to the newest version. Also updated the extension version 0.16.0-dev to reflect the current dev cycle. Updates #113 Change-Id: I6a4aae5293fd505ca1ad9c39e485c3adf41c2dec Reviewed-on: https://go-review.googlesource.com/c/vscode-go/+/241557 Reviewed-by: Rebecca Stambler <rstambler@golang.org>
The vulnerability issue was resolved with the latest I looked into this issue over the last week and found Delve's json-rpc is not a JSON RPC over HTTP as clearly stated in https://github.com/go-delve/delve/tree/master/Documentation/api/json-rpc#json-rpc-interface. On the other hand I couldn't find any other convincing, mature alternative javascript library, and Delve DAP implementation that uses compatible framing (https://github.com/google/go-dap/blob/master/io.go ) is around the corner. So I will just close this. |
Sounds good, did not realize that |
From microsoft/vscode-go#2861 by @OneOfOne:
The text was updated successfully, but these errors were encountered: