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

[BUG] npm client install error installing vscode.d.ts #15

Open
Efratror opened this issue Mar 21, 2022 · 4 comments · May be fixed by #27
Open

[BUG] npm client install error installing vscode.d.ts #15

Efratror opened this issue Mar 21, 2022 · 4 comments · May be fixed by #27

Comments

@Efratror
Copy link

Bug:

The npm client install command crashes due to an error while installing vscode.d.ts. Also the setup was a bit tedious due to missing a few required packages for Ubuntu.

Detected VS Code engine version: ^1.23.0
Error installing vscode.d.ts: Error: Request returned status code: 404
Details: <!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Error</title>
</head>
<body>
<pre>Cannot GET /api/releases/stable</pre>
</body>
</html>

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! processing-lsp-client@0.0.1 postinstall: `vscode-install`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the processing-lsp-client@0.0.1 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

Possible solution

Add a "Linux/Ubuntu" section to Setup.md. And change the package-lock.json from the client. to an update vscode package (1.1.37) which runs fine on my Ubuntu VM

@toshan-luktuke
Copy link

I second this, had the same issue while trying to build it on Ubuntu. Changing

"engines": {
	"vscode": "^1.23.0"
},
"devDependencies": {
	"vscode": "^1.1.34"
}

to

"engines": {
	"vscode": "^1.60.0"
},
"devDependencies": {
	"vscode": "^1.1.37"
}

in client/package.json fixed it for me

@Efratror
Copy link
Author

Sadly it seems development of this repo is has stopped. @SyamSundarKirubakaran is the only contributor and didn't make a change in over a year. This is the most promising LSP for Processing i have seen so fare. So I'm continuing his work over at my fork. Maybe in the future he is willing to pull my fork in to this repo.

@SyamSundarKirubakaran
Copy link
Contributor

Hey @Efratror its true that my efforts towards this project has reduced and unfortunately, I can't mentor for this project for the upcoming GSoC.

But I'll make sure to sync with Processing Foundation's admins to see if there is a possibility of a transfer of ownership for this project.

If you're interested in contributing to this project. I'd recommend you to continue your contributions in your folked repo - I'll review and merge in the future (this might take sometime / can't specify when). I'll also have to spin up LSP and see if everything works as expected - deprecation happens quite often on the js world.

If you're looking to participate in GSoC. I'd recommend you look for alternatives as we have shortage of mentors for this project as of now.

@Efratror
Copy link
Author

Hey @SyamSundarKirubakaran, Had to lookup GSoC, nice initiative. But like i've said this is the most promising vs code extenstion i've seen. Especially with the LSP function. So that's why I was interested. Now i've read the GSoC project i had no idea you guys were updating the java mode classes to a more universal server type.

At the moment i've added windows and multiple "tab" support over at my fork. Sadley i've closed and deleted the branches i had created. Because i've mad the false assumption you've ceased development. Do you know a way to reopen these or make new branches with old commits? Then i can send you the pr's. Since i'm also interested in the extension for vs code do you mind if i send pr's for the client that as well?

@Efratror Efratror linked a pull request Apr 1, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants