How to remove a package from Laravel using composer?

Question

What is the correct way to remove a package from Laravel using composer? So far I've tried:

Remove declaration from composer.json (in "require" section)
Remove any Class Aliases from app.php
Remove any references to the package from my code :-)
Run composer update
Run composer dump-autoload

None of these options are working! What am I missing?

steadweb · Accepted Answer · 2020-10-26T09:08:54.003

778

Composer 1.x and 2.x

Running the following command will remove the package from vendor (or wherever you install packages), composer.json and composer.lock. Change vendor/package appropriately.

composer remove vendor/package

Obviously you'll need to remove references to that package within your app.

I'm currently running the following version of composer:

Composer version 1.0-dev (7b13507dd4d3b93578af7d83fbf8be0ca686f4b5) 2014-12-11 21:52:29

Documentation

https://getcomposer.org/doc/03-cli.md#remove

Updates

26/10/2020 - Updated answer to assert command works for v1.x and v2.x of Composer

edited Oct 26 '20 at 09:08

answered Dec 12 '14 at 09:09

steadweb

10,522
2
21
34

14

@ZeshanKhattak composer update will update all dependencies. It way leave the project in unstable state. Don't use composer update unless you want to update dependencies – zarax Apr 26 '17 at 14:05
12

`composer remove packagename` , It updates removing package from composer.json and removes package folder from vendor... laravel - 5.4.24, composer - 1.4.2. – Jun 09 '17 at 11:18
It seems like composer is automatically installing missing packages after running `composer remove `. Anyway to avoid that? Using version 1.7.2. – Olle Härstedt Aug 31 '18 at 12:50
it should be: composer remove package_name instead: composer remove vendor/package there is no need of vendor as laravel automatically check in vendor directory for packages. – prashant Sep 13 '19 at 10:01
If you don't want your packages to be updated after removing a module you can run `composer install` instead of `composer update` – Gezzasa Jul 13 '20 at 10:15
@prashant `vendor` here is also a variable. For example, if you were removing Carbon, you would run `composer remove nesbot/carbon`. In this example, `nesbot` is the name of the vendor. – Charles Wood Mar 09 '21 at 19:17

score 185 · Answer 2 · edited Jul 29 '20 at 02:43

185

Got it working... The steps to remove a package from Laravel are:

Remove declaration from composer.json (in "require" section)
Remove Service Provider from config/app.php (reference in "providers" array)
Remove any Class Aliases from config/app.php
Remove any references to the package from your code :-)
Run composer update vendor/package-name. This will remove the package folder from the vendor folder and will rebuild the composer autoloading map.
Manually delete the published files (read the comment by zwacky)

It will remove the package folder from Vendor folder

edited Jul 29 '20 at 02:43

Mostafa Norzade

1,059
2
17
35

answered Apr 17 '14 at 07:17

igaster

10,005
4
21
25

2

although unpublishing assets/configs isn't really an automated thing. i usually delete manually the vendor/package folders in config/ or public/. – Simon Wicki Apr 17 '14 at 07:28
7

now laravel should come up with something like "remove package " to make it easier. – Chandan Gupta Oct 08 '14 at 14:08
21

A problem with this solution is that it will update all other packages, which may not be what you want. – tremby Nov 19 '15 at 21:53
3

(1) and (5) can be replaced with running `composer remove vendor/package`, I think. – JCarlosR Sep 06 '17 at 19:31
Thank you, this instructions was useful to remove not working Igaster/laravel-theme package – Jjsg08 Nov 16 '18 at 15:21

score 66 · Answer 3 · edited Jul 04 '19 at 13:43

66

Running the following command

composer remove Vendor/Package Name

That's all. No need composer update. Vendor/Package Name is just directory as installed before

edited Jul 04 '19 at 13:43

Saularis

389
4
13

answered Aug 29 '17 at 11:24

Riaj Ferdous

733
6
5

1

I did this and it says that its no longer required in composer.json so 'ignoring' – Sweet Chilly Philly Jan 05 '19 at 21:01
1

```composer remove ``` I think this one is perfect for removing any packages. Forget about ```Vendor``` :) For example, ```composer remove laravel/tinker``` – Shamsul Huda Feb 10 '20 at 15:00
laravel is the vendor and tinker is the package name. you can't just remove a package by calling `composer remove tinker`. – Lajos Mészáros Mar 22 '21 at 13:46

Yevgeniy Afanasyev · Answer 4 · 2018-09-23T21:56:50.833

47

Normally composer remove used like this is enough:

$ composer remove vendor/package

but if composer package is removed and config cache is not cleaned you cannot clean it, when you try like so

php artisan config:clear

you can get an error In ProviderRepository.php line 208:

Class 'Laracasts\Flash\FlashServiceProvider' not found

this is a dead end, unless you go deleting files

$rm bootstrap/cache/config.php

And this is Laravel 5.6 I'm talking about, not some kind of very old stuff.

It happens usually on automated deployment, when you copy files of a new release on top of old cache. Even if you cleared cache before copying. You end up with old cache and a new composer.json.

edited Sep 23 '18 at 21:56

answered Sep 16 '18 at 23:23

Yevgeniy Afanasyev

27,544
16
134
147

2

I think it is fixed in 5.7 – Yevgeniy Afanasyev Jan 15 '19 at 04:19
1

With 5.6, my bootstrap/cache was empty. I forgot that I'd changed the cache path (config/cache.php)! Deleting the files in the new cache folder fixed the problem! – Aine Jan 29 '19 at 14:13
2

@YevgeniyAfanasyev This is not fixed Even in 5.7 – Shreyansh Panchal Mar 02 '19 at 10:50
2

I almost spent 3 hours pulling my hairs out over this. I thought `config:clear` would fix this. – Shreyansh Panchal Apr 02 '19 at 13:28

Shahrukh Anwar · Answer 5 · 2018-08-13T08:18:54.947

35

you can remove any package just by typing follwing command in terminal, and just remove the providers and alias you provided at the time of installing the package, if any and update the composer,

composer remove vendor/your_package_name
composer update

edited Aug 13 '18 at 08:18

answered Mar 15 '18 at 11:02

Shahrukh Anwar

2,004
1
18
20

1

Sometimes to update the new dependancies, you have to update the composer. I think there is no harm in running that. – Shahrukh Anwar Jul 16 '18 at 07:33

score 20 · Answer 6 · edited Jan 31 '18 at 17:20

20

Before removing a package from composer.json declaration, please remove cache

php artisan cache:clear  
php artisan config:clear

If you forget to remove cache and you get class not found error then please reinstall the package and clear cache and remove again.

edited Jan 31 '18 at 17:20

Raj

1,596
1
18
38

answered Jan 31 '18 at 14:24

Rayees Pk

1,347
18
16

gecko · Answer 7 · 2019-07-26T19:25:02.020

19

Simpliest and Easiest way

Syntax:

composer remove <package>

Example:

composer remove laravel/tinker

edited Jul 26 '19 at 19:25

answered Feb 19 '19 at 11:34

gecko

1,081
2
9
25

score 18 · Answer 8 · answered Jan 06 '18 at 09:41

You can do any one of the below two methods:

Running the below command (most recommended way to remove your package without updating your other packages)

$ composer remove vendor/package
Go to your composer.json file and then run command like below it will remove your package (but it will also update your other packages)

$ composer update

score 15 · Answer 9 · edited Oct 06 '17 at 09:47

15

If you are still getting the error after you have done with all above steps, go to your projects bootstrap->cache->config.php remove the provider & aliases entries from the cached array manually.

edited Oct 06 '17 at 09:47

Bugs

4,356
9
30
39

answered Oct 06 '17 at 07:40

Ramjith Ap

193
2
5

This helped me. – Peter Griffin Jun 01 '18 at 07:57
1

Some package vendor does not meet all requirements to create a package. For that reason, these vendors `composer remove vendor/package` unable to remove the cache entries properly. So, @Ramjith Ap is absolutely correct here. – Samrat Khan Nov 12 '18 at 19:18

SUNNETmedia · Answer 10 · 2019-03-06T07:40:08.230

12

**

use "composer remove vendor/package"

** This is Example: Install / Add Pakage

composer require firebear/importexportfree

Uninsall / Remove

composer remove firebear/importexportfree

Finaly after removing:

php -f bin/magento setup:upgrade

php bin/magento setup:static-content:deploy –f

php bin/magento indexer:reindex 

php -f bin/magento cache:clean

edited Mar 06 '19 at 07:40

answered Feb 20 '19 at 06:47

SUNNETmedia

311
3
5

score 10 · Answer 11 · edited Sep 07 '19 at 13:14

10

You can remove any package by typing following command in terminal, and just remove the providers and alias you provided at the time of installing the package and update the composer

composer remove <package_name>
composer update

edited Sep 07 '19 at 13:14

Angel F Syrus

1,607
7
18
36

answered Sep 07 '19 at 11:15

Maneesha

101
1
2

If you are using `composer update` to remove package folder, it is not necessary as package source directory is deleted during the removal process. – Gucu112 Aug 06 '20 at 05:45

score 9 · Answer 12 · answered Feb 08 '19 at 08:55

To remove a package using composer command

composer remove <package>

To install a package using composer command

composer require <package>

To install all packages which are mentioned in composer.json

composer install

To update packages

composer update

I used these for Laravel project

score 8 · Answer 13 · answered Jun 10 '18 at 15:22

8

In case the given answers still don't help you remove that, try this:

Manually delete the line in require from composer.json
Run composer update

answered Jun 10 '18 at 15:22

DonJoe

1,195
1
8
22

Abdellah Ramadan · Answer 14 · 2020-04-19T11:44:38.347

4

Remove the package with

composer remove vendorname/packagename

you can check remove package from composer.json - docs

Or you can remove the package name from composer.json file and run composer update from within your project directory. I hope it helps.

edited Apr 19 '20 at 11:44

answered Feb 02 '20 at 07:25

Abdellah Ramadan

325
2
13

score 3 · Answer 15 · answered Feb 03 '20 at 21:33

We have come with a great solution. This solution is practically done in Laravel 6. If you want to remove any package from your Laravel Project then you can easily remove the package by following below steps:

Step 1: You must know the package name which you want to remove. If you don't know complete package name then you can open your project folder and go to composer.json file and check name in require an array

"require": {
        "php": "^7.2",
        "fideloper/proxy": "^4.0",
        "laravel/framework": "^6.2",
        "laravel/passport": "^8.3",
        "laravel/tinker": "^2.0"
    },

Suppose, here I am going to remove "fideloper/proxy" package.

Step 2: Open command prompt with your project root folder directory Step 3: First of all clear all cache by following commands. Run commands one by one.

php artisan cache:clear  
php artisan config:clear

Step 4: Now write the following command to remove the package. Here you need to change your package name instead of my example package.

composer remove fideloper/proxy

Now, wait for a few seconds your package is removing.

or `composer remove laravel/telescope --dev` if it is dev package — vinsa, Mar 23 '20 at 14:03

score 2 · Answer 16 · answered Jan 24 '21 at 22:20

2

On laravel 8.* I following steps work for me :

Run command composer remove package-name on terminal
Remove Provider and aliases from Config/app.php
Remove related file from Config folder.

Remove from your code where you used .

answered Jan 24 '21 at 22:20

infomasud

448
3
7

Ahkmy990 · Answer 17 · 2021-03-15T20:18:18.897

2

Remove package folder from vendor folder (Manual delete)
remove it from 'composer.json' & 'composer.lock' files (use ctrl+f5 to search )
remove it from 'config/app.php' & 'bootstrap/cache/config.php' files
run this commads:
- composer remove your-package-name
- php artisan cache:clear & php artisan config:clear

edited Mar 15 '21 at 20:18

answered Jan 27 '21 at 13:14

Ahkmy990

31
4

score 0 · Answer 18 · answered Aug 20 '20 at 18:52

0

There are quite a few steps here:

Go to composer.json and look for the package and how it is written over there.

for example

{ "require": { "twig/twig": "^3.0" } }

I wish to remove twig 3.0

Now open cmd and run composer remove vendor/your_package_name as composer remove twig/twig this will remove the package.
As a final step run composer update this will surely give you a massage of nothing to install or update but this is important in case your packages have inter-dependencies.

answered Aug 20 '20 at 18:52

Chandraarnav

21
1
10

When adding an answer to six year old question with an accepted answer and fifteen existing answers it is important to point out what new aspect of the question your answer addresses. – Jason Aller Aug 20 '20 at 23:24
The most important thing I faced is point No.3, which we often ignore as we usually get "nothing to install or update", I was unfortunate while uninstalling certain illuminate component as I had sentinel which uses illuminate capsule. however thankfully update composer command helped here. the answers above misses on the inter-dependencies part, in case you feel its not important juss reply back I will remove my answer. – Chandraarnav Aug 21 '20 at 05:19

score 0 · Answer 19 · answered May 24 '21 at 19:12

0

To add the packages command be like:

composer require spatie/laravel-permission

To remove the packages command be like:

composer remove spatie/laravel-permission

answered May 24 '21 at 19:12

Aman Mehra

11
4

How to remove a package from Laravel using composer?

19 Answers19

Composer 1.x and 2.x

Documentation

Updates

Simpliest and Easiest way

Linked