-
-
Notifications
You must be signed in to change notification settings - Fork 509
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
Hard-coded dependency on composer.json blocks different composer environments #10592
Comments
Out of curiosity, what's your use case for different |
Developing new addons (we have 40+ custom), basically. We build them into the Devs need to use their dev copy of a package/addon when running Composer, and production must only use the code they produce which has had its tests/stability tagged. |
When I've ever needed to do that in the past, I've achieved it by adding the repositories to my global {
"repositories": [
{
"type": "path",
"url": "~/Code/path-to-addon-one"
},
{
"type": "path",
"url": "~/Code/path-to-addon-two"
},
]
} |
Bug description
We use
composer.local.json
andcomposer.production.json
which are decided on with the env varCOMPOSER=${ENV}
.This works fine within Laravel as it uses Composer's env vars. Statamic has hard-coded links to
composer.json
which error hard duringpackage:discover
and other commands.Example:
Statamic\Console\Composer\Json
How to reproduce
Logs
No response
Environment
Installation
Fresh statamic/statamic site via CLI
Additional details
No response
The text was updated successfully, but these errors were encountered: