Safely edit a third party composer (vendor) package in Laravel & prevent losing customized changes on release of a new version of the package

Question

I want to edit a package I pulled from composer in my Laravel 5 project, however i believe that if I ran composer update and a new version of this package has been released, I will lose all of my changes. How should I go about editing the package? Is there a way to copy package out of the vendor directory so I can use it somewhere else in my project?

Answer 1

The simple, fast and safe method:

1. Create a directory in the Laravel's root directory and name it packages or whatever you like.
2. Move the modified package from vendor directory to your packages directory.
3. Update composer.json to load the package from your packages directory instead of vendor directory.

first remove it from require

"require": {
    "php": ">=5.6.4",
    "laravel/framework": "5.3.*",
    "laravelcollective/html": "^5.3.0", <==== remove this line                           
    "barryvdh/laravel-debugbar": "^2.3",
    "doctrine/dbal": "^2.5"
},

and then add it to autoload

"autoload": {
    "psr-4": {
        "App\\": "app/",
        "Collective\\Html\\": "packages/laravelcollective/html/src", <==== add this line
    },
}

Please do not forget to run

composer dumpauto

Alternative for step 3.

There is also a new alternative if you're using latest version of composer.

Add this to you composer.json

"repositories": [
    {
        "type": "path",
        "url": "./packages/laravelcollective"
    }
]

And then modify the version of package to dev-master

"require": {
    "php": ">=5.6.4",
    "laravel/framework": "5.3.*",
    "laravelcollective/html": "dev-master", <==== this line                           
    "barryvdh/laravel-debugbar": "^2.3",
    "doctrine/dbal": "^2.5"
},

Finally

composer update

Answer 2

It actually isn't safe to edit composer packages, for the very reason you point out.

What I do is extends the classes that I want/need to change.

I have done it here with the Filesystem class. It doesn't ensure that it won't break, but it does let you update without overwriting your changes.

config/app.php

<?php

return [

    'providers' => [

//        'Illuminate\Filesystem\FilesystemServiceProvider',
        'MyApp\Filesystem\FilesystemServiceProvider',
    ],

    'aliases' => [
        ...
    ],

];

MyApp\Filesystem\FilesystemServiceProvider.php

<?php namespace MyApp\Filesystem;

use Config;
use Storage;
use League\Flysystem\Filesystem;
use Dropbox\Client as DropboxClient;
use League\Flysystem\Dropbox\DropboxAdapter;
use Illuminate\Filesystem\FilesystemManager as LaravelFilesystemManager;

class FilesystemManager extends LaravelFilesystemManager{

    public function createDropboxDriver(array $config)
    {
        $client = new DropboxClient($config['token'], $config['app']);

        return $this->adapt(
            new Filesystem(new DropboxAdapter($client))
        );
    }
}

Answer 3

if you want to keep your changes AND update the package from the original repo at the same time, you can fork this package and point composer to pull from your fork, not the original repo.

All you have to do is add your fork as a repository and update the version constraint to point to your custom branch. Your custom branch name must be prefixed with dev-.

update your composer.json file as follows:

{
    "repositories": [
        {
            "type": "vcs",
            "url": "https://github.com/MyGithub/html"
        }
    ],
    "require": {
        "laravelcollective/html": "dev-bugfix"
    }
}

Note that you don't change the require statement except to specify your bugfix branch. You still reference the upstream package (laravelcollective/html), not your personal fork (MyGithub/html).

also, note that dev- is automatically added so branch name is bugfix not dev-bugfix. if you named your branch as dev-bugfix you will require it as dev-dev-bugfix.

Answer 4

If you want to make changes to a class of a package you have to

1. Create a class that extends the package class and make your changes

2. Create a service provider that extends the service provider of the class and change the registerBinding class to bind your extended class

3. Put that new service provider in providersarray in config\app

4. Disable package discovery for this package, you may list the package name in the extra section of your application's composer.json file:

   "extra": {
       "laravel": {
           "dont-discover": [
               "barryvdh/laravel-debugbar"
           ]
       }
   }, 
   

Answer 5

1. use strict version of the vendor package, e.g. instead of "vendor/package": "~1.3", or "vendor/package": "^1.3.2", you may use "vendor/package": "1.3.2",
2. copy the modified source file into public (if open source), or storage/app for private file (eg laravel)
3. simply code this in Controller : File::copy('foldername/filename.php', '../vendor/namevendor/subfolderwhatever/filename.php');
4. make this as deployment routine , shared to deployment colleagues
5. have a coffee, have a life, done