In your composer.json you can put:
{ "require": { "vendor/package": "version" } }
then run composer install or composer update from the directory containing composer.json . Sometimes, for me, composer is deceiving, so I'll start with composer clear-cache; rm -rf vendor; rm composer.lock composer clear-cache; rm -rf vendor; rm composer.lock composer clear-cache; rm -rf vendor; rm composer.lock composer clear-cache; rm -rf vendor; rm composer.lock composer clear-cache; rm -rf vendor; rm composer.lock composer clear-cache; rm -rf vendor; rm composer.lock composer clear-cache; rm -rf vendor; rm composer.lock composer clear-cache; rm -rf vendor; rm composer.lock composer clear-cache; rm -rf vendor; rm composer.lock before composer install to make sure it gets fresh stuff.
Of course, as the other answers show, you can run the following from the terminal:
composer require vendor/package:version
And according to the version:
- Composer of the official version of the article
- Ecosia Search
Reed Jun 28 '19 at 17:21 2019-06-28 17:21
source share