Contents
How to update a module in Drupal using composer?
For a minor-version update to a given Drupal module/project, simply use the following: To preview the update, and show you what would happen, without actually changing anything, add — dry – run. For a major-version upgrade (such as 1.x to 2.x), update alone isn’t enough: you must first require the new major version explicitly.
How to update Drupal core with all dependencies?
Run the following Composer command: If you are using drupal/core-recommended: composer update drupal/core ‘drupal/core-*’ –with-all-dependencies; Otherwise run: composer update drupal/core –with-dependencies; If you’d like to update to an unstable release, use one of these instead:
What to do when Drupal doesn’t update?
If there is no line starting with drupal / core, Composer isn’t aware of any update. If there is an update, continue with the commands below Note: zsh handles asterisks differently, so asterisk package wildcards need to be quoted. To simulate the update, and show you what would happen, without actually changing anything, add — dry – run.
When to run Composer install no Dev instead of composer update?
If you have separate dev/staging and production servers, ensure the updated composer.json and composer.lock files are on production and always run composer install — no – dev on production, rather than composer update. The — no – dev switch skips the installation of packages not intended for use on production sites.
Where do I find Drupal core composer scaffold?
If you’re unsure look for an entries like “drupal/core-recommended”: “^8.8”, and “drupal/core-composer-scaffold”: “^8.8” in your composer.json file. This is a good indication that you’re using the current recommend approach. You can learn more about making these changes in Update Drupal from Versions Prior to 8.8.x using Composer.
Do you have to use composer for updating modules?
People who are used to upgrading module with Drush should notice that in Drush 9 and Drush 10 (the current version) all the up commands pm – update, pm – updatecode and pm – updatestatus are deprecated. You have to use the corresponding Composer commands instead.
Do you need to update a module to 2.x?
For a major-version upgrade (such as 1.x to 2.x), update alone isn’t enough: you must first require the new major version explicitly. Since major versions often introduce major changes, this would be an excellent time to visit the module/project to inspect its documentation and issue queue.