Workbench package dependencies installing in workbench directory...

posted 11 years ago

I'm developing a package in the workbench, and when I require a few dependencies in the package's composer.json, then run composer update on my main application composer, the requirements specified are installed in /workbench/hokeo/vessel/vendor, instead of /vendor, like normal packages.

I have this is my main composer.json (application):

"psr-0": {
	"Hokeo\\Vessel\\": "workbench/hokeo/vessel/src/"
}

And this in my package composer.json:

"require": {
    "php": ">=5.3.0",

    "illuminate/support": "4.1.*",
    "zizaco/entrust": "1.1.*",
    "league/flysystem": "0.2.*",
    etc...
},
"autoload": {
    "classmap": [
        "src/commands",
        "src/controllers",
        "src/models",
        "src/library",
        "src/migrations",
        "src/seeds",
        "src/formatters"
    ],
    "psr-0": {
        "Hokeo\\Vessel\\": "src/"
    }
},

Last updated 2 years ago.

chrisrm

replied 11 years ago

That's the way it should work. And you don't need to map your package namespace in your "main" composer.json. You should read more about what composer packages are, how they work and how to use laravel's workbench.

Last updated 2 years ago.

andrewsuzuki

replied 11 years ago

Ok, I see. Well, when I include dependencies in my package's composer.json it gives me a blank page for some reason. It happens when laravel includes my package's vendor/autoload.php file. No errors with composer installation from the package directory --- what gives?

Last updated 2 years ago.

Moderators