-
Notifications
You must be signed in to change notification settings - Fork 3
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
Error during activation of LSP-intelephense on Windows 11 in ST4 #93
Comments
When you got the issue have you tried just restarting ST and seeing if it works then? I don't quite see from the log why it would fail. The log shows that
indicating that |
How did you install |
Found the issue: sublimelsp/lsp_utils#111 |
Yes. Didn't help.
There was some hint by a very nice gentleman which helped me to find this solution. Let me check... |
I cannot reproduce this on Windows. Recently After this recent update, Do you see the "Download Node.js" button in the popup and have you pressed it? |
Yes, that popped up every time after a new install of the LSP-intelephense package. I was able to reduce the issue multiple times yesterday with my Sublime Text installation on the Win11 VM. ST4 and the PHP stuff was originally installed on this VM on October 14th. So this predated that recent update you mentioned. This morning I uninstalled ST4 and removed everything I was able to find related to ST4. Afterwards I reinstalled Sublime Text, LSP and LSP-intelephense and had no issue. So you might be right that this update fixed the issue also. I'll try to update ST packages on my work machine on Monday. That was where I encountered the issue originally. At home I use Linux so never had the issue. |
I can install the package without a problem in Sublime Text 4, but when it gets activated, it fails due to not being able to find the node executable. See attached error log. This seems to be a Windows specific problem, at least I had no issue on Linux so far.
I was able to solve this by installing lsp_utils before installing LSP-intelephense. This should either be fixed or prominently documented.
2023-10-27T19_23_35_264Z-debug-0.log
The text was updated successfully, but these errors were encountered: