You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In ububtu 18.04 64 bit system, when opening a Laravel 8 project in PHP 8.0, the PHP language server is getting crashed and the whole system is getting hanged.
To reproduce the issue, you need to check in ubuntu 18.04 system. Install PHP 8.0 and enable it. Setup a Laravel 8 project. And open it. Open the terminal in VS code. You may not get the time to open it. But if you hurry then you can open the terminal. In the PROBLEMS tab there it is showing 4k+ issues. Then in OUTPUT tag it is showing some message, somethig is exited. Then you can't do anything.
It should work like normal. The extension is working perfect in PHP 7.4 but when u enabling PHP 8.0 then you are doomed.
Platform and version
OS: ubuntu 18.04
PHP: 8.0
Laravel: 8
Intelephense version: v1.7.1
The text was updated successfully, but these errors were encountered:
If you are lucky and your PHP isn't new enough (like not 8.1 that doesn't work) you can go to the plugin folder in ~/.vscode/extensions and run compose update that should make it work with 8.0.
In ububtu 18.04 64 bit system, when opening a Laravel 8 project in PHP 8.0, the PHP language server is getting crashed and the whole system is getting hanged.
To reproduce the issue, you need to check in ubuntu 18.04 system. Install PHP 8.0 and enable it. Setup a Laravel 8 project. And open it. Open the terminal in VS code. You may not get the time to open it. But if you hurry then you can open the terminal. In the PROBLEMS tab there it is showing 4k+ issues. Then in OUTPUT tag it is showing some message, somethig is exited. Then you can't do anything.
It should work like normal. The extension is working perfect in PHP 7.4 but when u enabling PHP 8.0 then you are doomed.
Platform and version
OS: ubuntu 18.04
PHP: 8.0
Laravel: 8
Intelephense version: v1.7.1
The text was updated successfully, but these errors were encountered: