Skip to content
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

Building the package locally to use agda-mode input globally #137

Open
inexxt opened this issue Mar 23, 2023 · 1 comment
Open

Building the package locally to use agda-mode input globally #137

inexxt opened this issue Mar 23, 2023 · 1 comment
Labels
question Further information is requested

Comments

@inexxt
Copy link

inexxt commented Mar 23, 2023

I'd like to be able to use agda-mode input globally. To do so, I wanted to modify the package.json and disable the condition on

{
  "command": "agda-mode.input-symbol[Activate]",
  "key": "\\",
  "when": "editorLangId == agda"
}

I have modified it in ~/.vscode/extensions/banacorn.agda-mode-0.3.11/package.json, but it didn't have any effect. One advice I got is that I'd have to rebuild the package for the change to work.

However, the build process described in CONTRIBUTING.md does not work. After cloing the repo, I get the following error message:

jacek:agda-mode-vscode/ (master) $ yarn install                                            [21:31:42]
➤ YN0000: ┌ Resolution step
➤ YN0013: │ reason-nodejs@https://github.com/banacorn/reason-nodejs.git#commit=266080d84b820fc88319dd6
➤ YN0013: │ language-server-mule@https://github.com/banacorn/language-server-mule.git#commit=2caa86191
➤ YN0013: │ @glennsl/bs-json@https://github.com/banacorn/bs-json.git#commit=0c900d3ad5c06eb2e6513a6770
➤ YN0013: │ rescript-vscode@https://github.com/banacorn/rescript-vscode.git#commit=316ce927cd34f8a3ad7
➤ YN0061: │ vscode-codicons@npm:0.0.7 is deprecated: This package is deprecated, please use @vscode/codicons https://www.npmjs.com/package/@vscode/codicons
➤ YN0061: │ vscode-test@npm:1.6.1 is deprecated: This package has been renamed to @vscode/test-electron, please update to the new name
➤ YN0061: │ mkdirp@npm:0.5.4 is deprecated: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
➤ YN0061: │ debug@npm:3.2.6 is deprecated: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
➤ YN0032: │ fsevents@npm:2.1.3: Implicit dependencies on node-gyp are discouraged
➤ YN0061: │ fsevents@npm:2.1.3 is deprecated: "Please update to latest v2.3 or v2.2"
➤ YN0061: │ @npmcli/move-file@npm:1.1.2 is deprecated: This functionality has been moved to @npmcli/fs
➤ YN0061: │ @npmcli/move-file@npm:2.0.1 is deprecated: This functionality has been moved to @npmcli/fs
➤ YN0001: │ Error: @glennsl/bs-json@github:banacorn/bs-json#0c900d3: Couldn't resolve "0c900d3" as either a commit, a tag, or a head - if a commit, use the 40-characters commit hash
    at a (/home/jacek/.cache/node/corepack/yarn/3.5.0/yarn.js:593:6577)
    at gO (/home/jacek/.cache/node/corepack/yarn/3.5.0/yarn.js:593:6906)
    at async FQ.getCandidates (/home/jacek/.cache/node/corepack/yarn/3.5.0/yarn.js:593:11834)
    at async xf.getCandidates (/home/jacek/.cache/node/corepack/yarn/3.5.0/yarn.js:391:1224)
    at async xf.getCandidates (/home/jacek/.cache/node/corepack/yarn/3.5.0/yarn.js:391:1224)
    at async /home/jacek/.cache/node/corepack/yarn/3.5.0/yarn.js:439:7685
    at async ff (/home/jacek/.cache/node/corepack/yarn/3.5.0/yarn.js:390:11064)
    at async ge (/home/jacek/.cache/node/corepack/yarn/3.5.0/yarn.js:439:7667)
    at async Promise.allSettled (index 0)
    at async to (/home/jacek/.cache/node/corepack/yarn/3.5.0/yarn.js:390:10398)
➤ YN0000: └ Completed in 3s 992ms
➤ YN0000: Failed with errors in 4s

I have tried modifying the appropriate dependency in package.json (including the whole commit hash, pointing to master), but to no effect. I don't know whether it's a caching problem, or if it's actually pulling the contents of package.json from the remote.

My system details (in case it matters):

jacek:agda-mode-vscode/ (master) $ yarn --version                                          
3.5.0
jacek:agda-mode-vscode/ (master) $ npm --version                                          
9.5.1
jacek:agda-mode-vscode/ (master) $ corepack --version                                  
0.17.0
@L-TChen L-TChen added the question Further information is requested label Sep 23, 2023
@banacorn
Copy link
Owner

I've updated some of the dependencies, please run npm install again and see if the same error still pops up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants