-
Notifications
You must be signed in to change notification settings - Fork 185
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
Difficulty installing and configuring on macOS 10.15.7 #805
Comments
Same for me Composer 2.0.13 Removed http.php and standard_8.php - worked for me. I think this is somehow related to php8? |
same to me, Removed http.php and standard_8.php - worked for me. |
For anyone finding this same issue, here's the source: it's the result of using using the This project might be abandoned (don't see any activity in diffs for the last few years), so it's not likely that it'll get patched. To unblock yourself, you can just remove that file + it should complete building. (Though you might see other errors of the same type; continue ignoring those files.) |
I agree the project seems to be abandoned; from what I can tell, folks have settled on Intelephense (and we've been recommending it). |
I'm working on an LSP client and would like to add preconfigured support for this language server. In the process I'm trying to develop end-user installation instructions.
Reading
README.md
, the instructions say:When I attempt this, I get the following:
After much thrashing around, including rolling my installed PHP back to 7.4.15, I was able to do the following, which appears to have succeeded:
This may be worth a note in the README.
I then went to the next step in the instructions:
This failed, because
vendor/felixfbecker/language-server
does not exist. The correct invocation appears to be:(Using Composer 2.0.11 and PHP 7.4.15)
I'm not sure if that's a documentation issue or a Composer issue.
Finally, and here is where I am blocked:
At this point I am unable to proceed further, and would appreciate any recommendations you may have.
The text was updated successfully, but these errors were encountered: