Composer update in a drupal stack will break after composer-installer new version #239
Description
Describe the bug
After https://github.com/PHPCSStandards/composer-installer/releases/tag/v1.1.0 new release, in a drupal stack, with https://github.com/drupal/core-dev, which along its children dependencies has composer-installer, and php_codesniffer, and a composer update when updating PHPCSStandards/composer-installer version from 1.0.0 to 1.1.0 will break with the following error:
[38.1MiB/36.16s] Scaffolding files for drupal/core:
[..snip..]
[38.1MiB/36.16s] - Copy [web-root]/sites/default/default.settings.php from assets/scaffold/files/default.settings.php
[38.2MiB/36.17s] ::error ::The provided cwd "../squizlabs/php_codesniffer" does not exist.
In Process.php line 350:
The provided cwd "../squizlabs/php_codesniffer" does not exist.
update [--with WITH] [--prefer-source] [--prefer-dist] [--prefer-install PREFER-INSTALL] [--dry-run] [--dev] [--no-dev] [--lock] [--no-install] [--no-audit] [--audit-format AUDIT-FORMAT] [--no-autoloader] [--no-suggest] [--no-progress] [-w|--with-dependencies] [-W|--with-all-dependencies] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--apcu-autoloader-prefix APCU-AUTOLOADER-PREFIX] [--ignore-platform-req IGNORE-PLATFORM-REQ] [--ignore-platform-reqs] [--prefer-stable] [--prefer-lowest] [-m|--minimal-changes] [--patch-only] [-i|--interactive] [--root-reqs] [--bump-after-update [BUMP-AFTER-UPDATE]] [--] [<packages>...]
Still with drupal/core-dev in my composer.json, and i enforce composer-installer to the previous version, error is gone.
"dealerdirect/phpcodesniffer-composer-installer": "v1.0.0"
Not sure if this would be a PHPCSStandards/PHP_CodeSniffer issue, or PHPCSStandards/composer-installer.
Please confirm
- I have searched the issue list and am not opening a duplicate issue.
- I have read the Contribution Guidelines and this is not a support question.
- I confirm that this bug is a bug in PHP_CodeSniffer and not in one of the external standards.
- I have verified the issue still exists in the
masterbranch of PHP_CodeSniffer.