-
-
Notifications
You must be signed in to change notification settings - Fork 36
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
phpcs: Exit Code: 127 (Command not found) on every Composer command #48
Comments
Hi! Thank you for taking the time to report this. This behaviour seems to be caused by the fact that the plugin functionality is called when it should not be. In other words, the plugin is triggered for an event it is not registered for. The root cause is that the (public) A potential solution would be simply move the That way init is only called when the plugin is about to be used, rather than on any composer command. |
Looks like PR #51 addresses this issue. |
This is indeed addressed by #51, which has been merged in and will be part of the next release. |
Problem/Motivation
After installed
"dealerdirect/phpcodesniffer-composer-installer": "^0.4.3"
, my Composer getting error aboutphpcs
command not being found.This happens, when I am working with multiple bin-dir folders. Normally I've got
COMPOSER_BIN_DIR
pointed to/usr/local/bin
, but in some shell instances, I don't have. After installing this package, now everycomposer
is producing the error.Expected behaviour
The processing should be ignored when the binary can't be found.
Actual behaviour
Steps to reproduce
Proposed changes
The plugin should be less invasive.
The text was updated successfully, but these errors were encountered: