I've been working on a Laravel project. While I'm trying to install some package. I got warned
Package phpoffice/phpexcel is abandoned, you should avoid using it.
Use phpoffice/phpspreadsheet instead.
Therefore, I executed the command
composer remove phpoffice/phpexcel
The phpoffice/phpexcel has been remove from composer.json successfully.
Then install the package,
composer require phpoffice/phpspreadsheet
I still got warned by the same warning,
Package phpoffice/phpexcel is abandoned, you should avoid using it.
Use phpoffice/phpspreadsheet instead.
I always got warned by this sentence from every composer command even the phpoffice/phpexcel has been removed from composer.json.
Pls help I really have no idea to remove this warning.
Maybe the package phpoffice/phpexcel is used by another package in your composer.json. To see if that's the case you can use the following command to find out which other packages may need phpoffice/phpexcel:
composer why phpoffice/phpexcel
Does that give you a list of packages or an error?
To avoid this error you can run the following commands --
composer remove phpoffice/phpexcel
Then -
composer require phpoffice/phpspreadsheet
Then -
composer dump-autoload
composer update
Suppose that for stability reasons, I've constrained the version of a particular package in composer.json:
"require": {
"foo/bar": "~3.2.6",
}
I am now ready to upgrade foo/bar to version 4.
What is the correct workflow to do this?
Should I edit the composer.json file by hand and run one of composer install or update? Or should I do composer require foo/bar 4?
composer require vendor/package:version
like :
composer require foo/bar:^4.0.0
Is it possible to remove a package and it's dependencies from composer's lockfile before install?
Things I've tried that don't work:
composer remove package --no-update # Only updates composer.json
composer remove package # Removes only this package, installs all its dependancies
I installed composer globally on my Debian server
~$ which composer
/usr/local/bin/composer
It works, gets updated and I used it for three different (Symfony) sites.
~$ composer self-update
You are already using composer version 1.3.3 (stable channel).
However, when I am in the directory of one of the sites, and try to update all dependencies, I get an error (before, this just worked and updated the vendors etc).
~/website-path$ ls composer.*
composer.json composer.lock
~/website-path$ composer update
[ErrorException]
Illegal string offset 'version'
~/website-path$ composer
[ErrorException]
Illegal string offset 'version'
When I rename composer.json, this Error disappears (but the lack of .json file makes this quite useless)
What went wrong here and how can I fix this?
The problem magically went away overnight by upgrading to 1.4.0
~$ composer -V
Composer version 1.4.0 2017-03-08 17:51:24
~/website-path$ composer update
Loading composer repositories with package information
Updating dependencies (including require-dev)
Nothing to install or update
[...]
I'm using Composer to install multiple packages using the following syntax:
{
"require": {
"aws/aws-sdk-php": "2.*",
"vimeo/vimeo-api": "1.1.*",
"phpoffice/phpexcel": "dev-master"
}
}
The above works just fine, but now I'd like to add tcpdf via composer. I found this code here but am not sure how to integrate with my current requires. One thing that I tried was to just add it to the end, but I fear that it started deleting my current packages.
{
"name": "tecnick.com/tcpdf",
"version": "6.2.11",
"homepage": "http://www.tcpdf.org/",
"type": "library",
"description": "TCPDF is a PHP class for generating PDF documents and barcodes.",
"keywords": [
"PDF",
"tcpdf",
"PDFD32000-2008",
"qrcode",
"datamatrix",
"pdf417",
"barcodes"
],
"license": "LGPLv3",
"authors": [
{
"name": "Nicola Asuni",
"email": "info#tecnick.com",
"homepage": "http://nicolaasuni.tecnick.com"
}
],
"require": {
"php": ">=5.3.0"
},
"autoload": {
"classmap": [
"fonts",
"config",
"include",
"tcpdf.php",
"tcpdf_parser.php",
"tcpdf_import.php",
"tcpdf_barcodes_1d.php",
"tcpdf_barcodes_2d.php",
"include/tcpdf_colors.php",
"include/tcpdf_filters.php",
"include/tcpdf_font_data.php",
"include/tcpdf_fonts.php",
"include/tcpdf_images.php",
"include/tcpdf_static.php",
"include/barcodes/datamatrix.php",
"include/barcodes/pdf417.php",
"include/barcodes/qrcode.php"
]
}
You can require many packages from the command line, for example:
composer require barryvdh/laravel-debugbar barryvdh/laravel-snappy fideloper/proxy
And all the packages will be required according to your composer specifications.
As a matter of fact, you can list all the packages separated by space, like so:
composer require aws/aws-sdk-php vimeo/vimeo-api phpoffice/phpexcel
Quote:
If you do not want to choose requirements interactively, you can pass
them to the command
From Composer documentation
Also consider --update-with-all-dependencies to update the dependencies of all newly installed packages.
If anyone else comes here and wants to know how to add "multiple" packages, simply use the Composer require command and run multiple CLI commands by terminating them with a semi-colon, e.g.
composer require drupal/pathauto;
composer require 'drupal/google_analytics:^3.0';
composer require 'doctrine/doctrine-bundle:2.*';
composer require 'monolog/monolog:~2.0.0';
Alternatively run with the --no-update flag to disable automatic update of dependencies and run all the updates together — composer will resolve dependencies in one hit:
composer require drupal/pathauto --no-update;
composer require 'drupal/google_analytics:^3.0' --no-update;
composer require 'doctrine/doctrine-bundle:2.*' --no-update;
composer require 'monolog/monolog:~2.0.0' --no-update;
composer update;
If you don't specify a version then composer will automatically pull the latest release. It's worth reading up on Composer versions and constraints, especially when it comes to updating packages. Check the Composer require command for more useful flags.
It can be useful to keep package requirements on separate lines as above, e.g. if you have a reference document of regularly installed packages, or if the commands are being generated by a build tool.
Alternatively you can run them all on one line:
composer require drupal/pathauto 'drupal/google_analytics:^3.0' 'doctrine/doctrine-bundle:2.*' 'monolog/monolog:~2.0.0';
N.B. Terminating commands with a semi-colon is a general solution for running multiple CLI commands, and not just composer specific, e.g.
composer self-update;
composer require 'drupal/google_analytics:^3.0';
cd app/build;
yarn run build;
To add "tecnick.com/tcpdf" to an existing composer.json file, on the commandline inside the directory containing it run:
composer require tecnick.com/tcpdf
You shouldn't have to manually edit the composer.json file for such things.
If you want to add handful of packages without having to wait tediously for composer to update after each and every one, but you prefer not to:
change a long series of modules together in a single line (poor readability, less convenient to reuse)
use a semi-colon delimited list of commands (featherbelly's answer - easy to insert a typo or accidentally paste a carriage return and screw it up midway through)
…then use the --no-update switch to have composer modify the composer.json file ONLY, without searching for packages.
You can run as few or as many as you want, use the CLI to do something else midway through, and when you're ready, just do composer-update by itself.
Here's an example of adding some Drupal modules for a new project:
composer require 'drupal/field_permissions:^1.0' --no-update
composer require 'drupal/coffee:^1.0' --no-update
composer require 'drupal/token:^1.5' --no-update
composer require 'drupal/field_tools:^1.0' --no-update
composer require 'drupal/required_by_role:^1.0' --no-update
composer require 'drupal/devel:^2.1' --no-update
composer require 'drupal/config_ignore:^2.1' --no-update
composer require 'drupal/ga_login:^1.0' --no-update
composer require 'drupal/tfa:^1.0' --no-update
composer require 'drupal/spambot:^1.0' --no-update
composer require 'drupal/pathauto:^1.4' --no-update
composer require 'drupal/flag:^4.0' --no-update
composer require 'drupal/stringoverrides:1.x-dev' --no-update
composer require 'drupal/structure_sync:^1.16' --no-update
composer require 'drupal/masquerade:^2.0' --no-update
composer require 'drupal/metatag:^1.8' --no-update
composer require 'drupal/unique_field_ajax:^1.2' --no-update
composer require 'drupal/config_override_warn:^1.2' --no-update
composer require 'drupal/environment_indicator:^3.6' --no-update
composer require 'drupal/role_delegation:^1.0' --no-update
composer require 'drupal/seo_checklist:^4.1' --no-update
composer update
NB: If you know what the modules you need and are typing your list manually anyway, just edit composer.json by hand - there's no point manually typing "composer require" over and over again.
However, the above method is handy for sites like Drupal where you're copying and pasting pre-written commands that contain complex version syntax for branches, individual commits etc.