This is slightly different from how Composer 1 behaves and can produce different results. If a package is found in a repository, Composer will not look for that package in any other repositories further down the line. Easy!Ĭomposer 2 also provides a command to check the platform requirements that also checks plugins: composer check-platform-reqsĪlso, it is interesting to note a change in how Composer 2 deals with repositories. With Composer v2, Composer will look for packages in all repositories configured in the composer.json file in the order they are set.
Docker4drupal update#
Because Docker4Drupal already provides images with Composer 2, we only had to update the Docker images. For the development environment, we use a custom boilerplate that provides a complete working Drupal site: Docker containers ready to run drupal (thanks to Docker4Drupal), MkDocs to document the project, Behat ready to be used, automatic code checking and some other tools. However, the Drupal Community provides a documentation page for the transition to Composer 2 where you can see all the plugins that need to be updated to work with Composer 2, the plugins that are not needed anymore (like the previously essential Prestissimo plugin) and the plugins they need work to be compatible with Composer 2. As said before, Composer plugins can be an issue. The task was completed even before Composer 2 was officially released (the change record is dated almost two weeks before Composer 2).īut, what is the actual experience using Composer 2 on real projects? Pretty good, actually. The main task was to update the required Composer plugins so they work with Composer 2. That's why some smart people were working to make sure Drupal works seamlessly with Composer 2. Drupal and Composer 2ĭrupal loves Composer. Luckily, the time has passed and many plugins have been updated to work with Composer 2. Because Composer has changed internally a little bit, previous plugins may fail when used with Composer 2. Honestly, there's a point where issues may arise: the Composer plugins. Did something go wrong? Downgrade to Composer 1: composer selfupdate -1 Is everything ok? Amazing! Continue using Composer 2. Once done, you can try Composer 2 with one of your projects: composer update -dry-run
Docker4drupal how to#
What about new syntax? New commands, removed commands? Good question, but no worries: most commands and arguments are exactly the same.įor a detailed description of all the changes of Composer 2, I recommend this article from PHP.Watch: " Composer 2: What's new and changed"Īnd how to start using Composer 2? It depends on how you installed Composer, but if the Composer executable is under your control (aka you have the permissions to modify it) you only have to run: composer selfupdate -2Ĭomposer will replace its version with the new shiny Composer 2 release. You can try Composer 2 and if anything goes wrong just roll back to Composer 1, your composer.json won't' be hurt during the process. This means you can use the same composer.json with Composer 1 and Composer 2.
composer.lock files are interoperable between versions. As stated in the release post, Composer 2.0 still supports PHP 5.3 and above, like Composer 1. While this is true on many occasions, it seems this time is not.
Docker4drupal software#
But software upgrades are never free, there's always some pain waiting to jump over you.
0 kommentar(er)
