Support locally installed phpstan

[neufena]

Currently, the extension only seems to work with phpstan installed globally, please support installed locally too. This could be as simple as allowing to specify the path to the phpstan executable

[breeze2]

The version 1.0.6 can automatically find the local phpstan executable in the current working directory. Please upgrade and try.

[neufena]

Thanks, that looks like it'll work perfectly for vendor in the standard place. Annoyingly the main project I work on has the path application/vendor/bin/phpstan. I wonder if there's a to get the vendor path from composer instead of hardcoding it?

[breeze2]

Sorry, I am not very clear about your situation🤔️.

• Do you want to use the /PROJECT_PATH/application/vendor/bin/phpstan to analyse the /PROJECT_PATH/dir/a.php?
• Isn't the /PROJECT_PATH/application/vendor created by composer?
• If I provide a config parameter for the path of phpstan executable, Can it solve your problem?

[Silic0nS0ldier]

Structure described here is reminisent of CodeIgniter 3, where its a common practise to have composer.json (and by extension the vendor folder) inside the application folder as the project fully resides in the web root (web server rules block access to application code).

Given this quirk, the intent would be to use /PROJECT_PATH/application/vendor/bin/phpstan against /PROJECT_PATH/**/*.php (or more likely /PROJECT_PATH/application/**/*.php since user code resides here by convention).

Providing a configuration option to specify the phpstan executable would be the best option to cover these non-standard scenarios.

[mindplay-dk]

On a related note, a global installation of phpstan did not work for me - it doesn't find it. I confirmed that phpstan in the Composer global bin folder was in path, and had no trouble manually launching it from the console. Even after restarting vscode, it couldn't find it. I finally installed it locally, which works fine.

Maybe consider updating the README? It specifically suggests using a global installation.

The official docs suggest using a local install - which is good practice anyhow, since that's the only way to ensure individual contributors to a project are using the same version and getting the same results, or if you're running it in CI.

I also have a project where the vendor dir (and thus local phpstan) is not in project root but in another directory, like app/vendor/bin/phpstan.

Providing configuration option for phpstan executable would solve the issue.