-
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
Crash on node_modules when using NPM 2 #113
Comments
The file paths are too long. Try upgrading to NPM 3 |
Ok, i'll try right now. Wait a moment. |
Right... I upgrade my 2.x version to 4.0.1. I need to executed any command in the project root? |
Please post the new stack trace |
Here:
|
You need to delete your |
Ok, wait a moment. |
Same error :(
|
Because you left the old |
oh dear anyway now, everything works great :) |
Windows has a hard limit on file path lengths. It was one of the biggest problems with NPM 2, that was solved with NPM 3. The LS searches for PHP files recursively in your project which causes the error. |
Hi, I have tried the suggestions in this tread, but that didn't solve the problem. I did the following:
The site loads If I visit my site withouth the debugger enabled. But if I start the debugger it just keeps loading, as shown on the image. How can I see the stack trace? |
@nonameolsson this repository has nothing to do with the debugger. You previous screenshot showed the exact error of this issue here - if the debugger doesn't work that has nothing to do with the language server, please see https://github.com/felixfbecker/vscode-php-debug#troubleshooting |
I'm trying for the first time using that extension in VS Code, but every time I open any project I get this error:
Connection to server got closed. Server will restart.
VS Code version: 1.6.1
Windows: 10 x64 PRO updated
How can I solve that?
The text was updated successfully, but these errors were encountered: