Discussion
Loading...
Post
@ramsey yes, it does. we are using this in #shopwarehttps://github.com/shopware/shopware/blob/trunk/composer.json#L218
I'm asking because I'm running into multiple variations of this error when I try running `composer update` or `composer require any/package`:
found another/package[0.0.1] in the lock file but not in remote repositories
All the packages that show that error are in the "path" repository and also in the lock file, and I can't figure out how to resolve this error so that I can require additional (external) packages.
@ramsey found that using this repo method, setting a `version` key in the composer.json files of the fake projects you’re including is a quick solve for resolution pain points. I know they there’s root version env var and maybe other things also…
@dpi Thanks for the pointer. Unfortunately, all our “fake” packages already have version specified in their composer.json files.
@dpi Another member of our team resolved it. I’m still not clear on what caused it, though. We have some global package I needed to install that has a plugin I needed to allow, so clearly we’re doing something magical and strange that isn’t how Composer normally works.
bonfire.cafe
A space for Bonfire maintainers and contributors to communicate
Automatic federation enabled