![]() Make sure you have the following block in the extra section of your composer.json. Let’s prepare our composer.json for the new scaffold plugin. If you do, run composer remove -dev webflo/drupal-core-require-dev. You may also have webflo/drupal-core-require-dev in your require-dev section. There may be other packages that depend on this (for example, hussainweb/drupal-composer-helper).Īlso, you may have to remove scaffold related commands in your composer.json. Make sure the package is actually removed. Run composer remove drupal-composer/drupal-scaffold. If not, it would be a good idea to first upgrade to Drupal 8.7 and then follow these steps (but not required).įirst, we need to remove the deprecated drupal-scaffold. Second, the process would be a lot more smoother if you are on Drupal 8.7 required. Taking a backup of your project won’t hurt either. Let’s start with the upgradeīefore your begin, make sure your git repository is clean, so that you can easily revert. There are some attempts to automate the upgrade but I’d prefer restructuring your site from scratch. If you see drupal/drupal instead, this won’t work for you. If yes, then the steps below would most likely work for you. A quick way to check this would be to see if you have the drupal/core project listed in your composer.json. ![]() Word of caution before going ahead: This article is about upgrading an existing site’s composer.json to use the new recommended packages IF you are already using webflo’s template or a close enough variant (such as my own fork or something generated with drupal-composer-init). After troubleshooting my way through various errors, I managed to get D10 installed. I have a D9 website that I was trying to update to D10. But I like to keep as close to the official versions as possible so that they are better maintained. Problem/Motivation Ive never submitted a request for help before, but Im at a loss. First of all, I should say you probably don’t need to do this. Here, I’ll talk about updating the existing sites which used webflo’s template to the new recommended style. If you like to be on the bleeding edge of your dependencies, then continue using drupal/core. It locks all Drupal core dependencies to known and tested versions. Note: You don’t have to use the new recommended template, but–like the name says– it is recommended you do. ![]() If you are starting a new project on Drupal today, all you have to do is follow the change record or the updated composer documentation to get started. With Drupal 8.8, the community did amazing work to bring this into core and Drupal’s infrastructure. Still, it seemed unofficial for someone who wouldn’t be into the community conversations. It’s well supported and did its job well. To capture any included database updates, run drush updb -y. To update the core package, run: composer update drupal/core -with-dependencies -v It’s recommended to run the update command with the -with-dependencies flag to update any of Drupal core’s dependencies as well. ![]() Among the many improvements, we’ll talk about the developments in the composer initiative in Drupal.įor years, we have been using webflo’s composer template as the quasi-official template for starting up Drupal projects. First, let’s cover the steps needed to update Drupal 8 core with Composer. With Drush make, this was simple.Drupal 8.8 is out today! This will be the last (minor) release of Drupal 8 (thanks Eli-T) and we are now looking at the release of Drupal 9 soon. What if core releases a security update? I want to be able to conveniently update core and only core quickly. Now, if my site is out in production, I would like an easy way to update core and core's vendor files WITHOUT updating a bunch of contrib modules' libraries which I do not care about. Whether or not I run it -with-dependencies, it will always go into the merge-plugin include paths and update all of those packages as well. Yet, when I run composer update drupal/core -with-dependencies My concern is this: I have some wildcards in my composer.json similar to the ones mentioned in this issue: which tell composer where to find my modules' composer.json files. Don't get me wrong, I still used composer, but not for Drupal core updates, because those are more important and sometimes security releases.īut, in 8.4, Drush 9 is required, and in Drush 9 make files don't work at all. It updates too much or too little, has uninformative error messages,Īnd takes a lot more ram than necessary. I knew that Drush make files were being phased out, but I kept using them, because in my opinion Composer isn't the best package manager in the known universe.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |