You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A well-maintained project will specify the proper version of PHP in composer.json:
"require": {
"php": "~8.3"
}
There's many reasons for this, including: If you run composer install with different PHP versions
you'll get different packages (some versions of packages require a minimum version of PHP due to using new language concepts).
you can get completely different .lock, autoload, etc. files. Which increases the number of "works for me" issues that you'll run into.
If you run composer install on a project and you're running the wrong version of PHP, you'll get a cryptic error. Something about how your php version does not satisfy requirements.
e.g.
Problem 1
- ezyang/htmlpurifier is locked to version v4.16.0 and an update of this package was not requested.
- ezyang/htmlpurifier v4.16.0 requires php ~5.6.0 || ~7.0.0 || ~7.1.0 || ~7.2.0 || ~7.3.0 || ~7.4.0 || ~8.0.0 || ~8.1.0 || ~8.2.0 -> your php version (8.3.7) does not satisfy that requirement.
Problem 2
- laminas/laminas-text is locked to version 2.10.0 and an update of this package was not requested.
- laminas/laminas-text 2.10.0 requires php ~8.0.0 || ~8.1.0 || ~8.2.0 -> your php version (8.3.7) does not satisfy that requirement.
Problem 3
- lcobucci/clock is locked to version 3.0.0 and an update of this package was not requested.
- lcobucci/clock 3.0.0 requires php ~8.1.0 || ~8.2.0 -> your php version (8.3.7) does not satisfy that requirement.
Problem 4
- mathieuviossat/arraytotexttable is locked to version v1.0.10 and an update of this package was not requested.
- mathieuviossat/arraytotexttable v1.0.10 requires php ~8.0.0 || ~8.1.0 || ~8.2.0 -> your php version (8.3.7) does not satisfy that requirement.
Problem 5
- ezyang/htmlpurifier v4.16.0 requires php ~5.6.0 || ~7.0.0 || ~7.1.0 || ~7.2.0 || ~7.3.0 || ~7.4.0 || ~8.0.0 || ~8.1.0 || ~8.2.0 -> your php version (8.3.7) does not satisfy that requirement.
- caxy/php-htmldiff v0.1.14 requires ezyang/htmlpurifier ^4.7 -> satisfiable by ezyang/htmlpurifier[v4.16.0].
- caxy/php-htmldiff is locked to version v0.1.14 and an update of this package was not requested.
git clone <something>
cd <directory>
lando start # Replace with the equivalent ddev command if that's what you prefer.
lando composer install # Same.
fire setup
I'm not sure what the workaround for this is. Should FIRE Launcher be able to run fire setup on its own???
The text was updated successfully, but these errors were encountered:
dalin-
added
bug
Something isn't working
critical
Prevents using fire. Must revert to the commands in the underlying tools to circumvent the bug.
labels
Sep 16, 2024
A well-maintained project will specify the proper version of PHP in
composer.json
:There's many reasons for this, including: If you run
composer install
with different PHP versionsIf you run
composer install
on a project and you're running the wrong version of PHP, you'll get a cryptic error. Something about how your php version does not satisfy requirements.e.g.
Meaning that our current install instructions won't work if you don't already have the correct version of PHP.
Instead you need to do something like
I'm not sure what the workaround for this is. Should FIRE Launcher be able to run
fire setup
on its own???The text was updated successfully, but these errors were encountered: