Skip to content

Cannot override vendor's composer.json autoload in project's composer.json #1100

jonathaningram opened this Issue Sep 12, 2012 · 3 comments

3 participants


I was using the autoload section of composer.json to allow a dev copy of my acme/library repository to be loaded before the copy in the vendor folder. This means that in development I can edit the library files locally and they will be loaded before the version installed in vendor. In production, it doesn't matter because only the vendor/acme/library version exists.

The composer.json section is like this:

    "autoload": {
        "psr-0": {
            "": "src/",
            "Acme": "acme-library/src/"

In that file, acme-library is a symlink that exists at the root of the project.

Prior to the fix in #1051, my generated autoload file would look like this:


return array(
    'Acme' => array($baseDir . '/acme-library/src/', $vendorDir . '/acme/library/src/'),

Now, the values in that array are reversed which means that $vendorDir . '/acme/library/src/' is loaded first and thus my locally changed library files do not get included.

Refs #1051, refs #1017


This was addressed at least once awhile back in #204. It had a test and a fixture that have since been removed. I have no idea what happened in #1051 that broke this but I depend on the original behavior of root package PSR-0 autoload taking precedence over dependencies PSR-0 autoload as well.


@Seldaek is appears this was fixed since a week or two. Was this on purpose or a by-product of something else? Either way, it may need a test case to prove.

Composer member
Seldaek commented Oct 23, 2012

Oh right yes it was fixed by @hason's PR linked above, and it included new tests which I think cover this case.

@Seldaek Seldaek closed this Oct 23, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.