Running composer install shows Warning: The lock file is not up to date with the latest changes in composer.json. You may be getting outdated dependencies. It is recommended that you run `composer
![Developer Quick Tips: Updating Modules Using "composer update" vs "composer require" | Hook 42 SF Bay Area Drupal Experts and WordPress Experts Developer Quick Tips: Updating Modules Using "composer update" vs "composer require" | Hook 42 SF Bay Area Drupal Experts and WordPress Experts](https://www.hook42.com/sites/default/files/styles/project_main_hero_image_700_w_/public/2019-07/composer-sample.png?itok=GT77Uo9G)
Developer Quick Tips: Updating Modules Using "composer update" vs "composer require" | Hook 42 SF Bay Area Drupal Experts and WordPress Experts
![Installation failed, reverting ./composer.json and ./composer.lock to their original content. laravel project - Stack Overflow Installation failed, reverting ./composer.json and ./composer.lock to their original content. laravel project - Stack Overflow](https://i.stack.imgur.com/4WQ89.png)
Installation failed, reverting ./composer.json and ./composer.lock to their original content. laravel project - Stack Overflow
![composer update --lock also SEEMS to update dev packages, but doesn't really · Issue #9812 · composer/composer · GitHub composer update --lock also SEEMS to update dev packages, but doesn't really · Issue #9812 · composer/composer · GitHub](https://user-images.githubusercontent.com/85479/114006548-d0a9bf80-9860-11eb-9205-379d3e8151d4.png)