- Issue created by @esch
- πΊπΈUnited States esch
I would also recommend adding composer "require-dev" to support development requirements.
- πΊπΈUnited States chaz.chumley Washington, D.C.
I am experiencing this issue as well. Any suggestions on how to resolve.
- πΊπΈUnited States chaz.chumley Washington, D.C.
Still waiting on a fix so we can use latest version.
- First commit to issue fork.
- πΊπΈUnited States mortona2k Seattle
Hey @chaz.chumley I have a reliable workaround for this kind of problem, where there are no compatible releases of a module that should otherwise work.
I download modules with composer conflicts to modules/pinned, and make changes like in the info.yml and composer files. I usually push those changes to an issue fork, or if there's already a fix, apply the patch manually within the module dir. Regular composer patches don't work to fix dependency conflicts because they're checked before the patch is applied.
If there are other composer dependencies that are needed to install the module, you can copy them into your root composer.json, or configure a custom path repository pointing to the pinned directory. https://getcomposer.org/doc/05-repositories.md#path
- πΊπΈUnited States pixelwhip
Closed and reopened the MR in an attempt to trigger tugboat and tests
-
pixelwhip β
committed 4ba50e19 on 2.1.x authored by
esch β
Issue #3423937 by esch, pixelwhip: Composer managed Drupal only installs...
-
pixelwhip β
committed 4ba50e19 on 2.1.x authored by
esch β
- Status changed to Fixed
9 months ago 11:47pm 14 March 2024 - πΊπΈUnited States pixelwhip
This fix has been released as part of 2.1.x-alpha16
Automatically closed - issue fixed for 2 weeks with no activity.