As you can see from the below example, the auto-generated line from Studio in the vendor/autoload.php file seems to produce an incorrect file-path (actually uses a mixture of separators):

require_once __DIR__ . '/../package\vendor\autoload.php';

This results in a fatal error due to the require failing. The fatal error goes away once all the back slashes are changed to forward slashes. I'm using Windows 10.

Studio currently suffers from the same problem that Workbench had: libraries in development with some of the same dependencies of the main project can cause conflicts with autoloading.

This needs to be solved by messing around with the Composer-generated files.

Here's my idea:

• Composer currently generates (I think) three different files based on the different autoloading types (PSR-4 etc.). These can be merged easily.
• After creating the autoloaders for the main project as well as the managed libraries, the type-specific files from the managed libraries should be merged into the respective ones from the main project. This should come down to merging a bunch of arrays.
• For conflicts, the ones from the main project should be preferred.

/cc @kirkbushell

Been using Studio for a while now and it's worked great. I use it to share packages between 3 different, but connected projects. I just updated from 0.9.5 to 0.10.0 and am getting class not found errors when running composer update. Specifically, it's happening in the post-update-cmd event and the classes not found are service providers. Studio is globally installed and they are all Laravel 5 applications. All workbench packages are 2 levels up from the Laravel roots. When I go back to 0.9.5 it all works again. Got any advice?

Not really sure what is happening, but as soon as I upgrade to Composer 1.6.3, all my symlinks are gone and real packages are installed instead.

Downgrading to 1.6.2 fixes the issue.

Tested both master and next branches.

In my use case, I want to workbench a package that is being consumed by a project already. My expectation is that, by loading it via Studio, the PSR-4 classes of the workbenched package will be get loaded instead of those in the composer vendor directory. This isn't what I'm observing, though. Is my expectation wrong here?

The documentation is a bit vague in my opinion. Is the following the correct approach to creating a new package using studio?

1. Create a new package skeleton using studio create <asdf>.
2. Adjust the skeleton, perhaps create baseline content.
3. Go to a Composer-powered project root.
4. Run studio load <asdf>.
5. studio.json is created containing something like

{
    "version": 1,
    "paths": [
        "<asdf>"
    ]
}

This should load the WIP package living in <asdf> to the Composer-powered project, am I correct?

When I run composer update nothing is installed and Nothing to install or update comes up in my terminal.

How I understand it should go:

1. studio create ...
2. studio load ...
3. composer update
4. Dev package created with studio create should appear to vendor or similar, either as a link/copy or as a line in the autoloader.

Currently nothing happens which resembles number 4 on that list.

I tried to create a package for a Wordpress plugin ("type": "wordpress-plugin") and a regular library package too, but both do not work for me. I'm running latest Composer and my environment is Ubuntu 14.04.

I hoped to miss something but somehow I see no way to publish the package public folder like I could do in L4 - php artisan asset:publish --bench.

Nothing be published with php artisan vendor:publish either.

Hi, I know this is more of a support question than an issue, but I'm not aware of any other way to ask. So, by default, Studio creates packages in /root/vendor-name/package-name. Is it possible to have Studio create all the packeges inside, let's say, /root/studio/vendor-name/package-name, but without having the studio segment in the package's namespace, because obviously once I publish the package, the studio segment will not be there.

Composer 2.0 is getting closer to a stable release and plugin authors are asked to test Composer 2 and add support to the plugins.

For more information see: https://github.com/composer/composer/issues/8726

If I've got time I'll take a look into it.

Hi,

Thanks for the awesome job with Studio, it's so cool!

I've tried to use Studio with composer create-project command, without success. Is it the normal or is it a bug? Or maybe I'm doing something wrong? Using Studio allows to create a package easily, to test it almost in "real life", using Composer with require command. I'd like to use it to download a project too... I can use Satis, but it's a bit more complicated: I wish Studio could help :)

I have been asked to leave this issue here, but I'm not sure I'll get the wording correct.

Basically, I attempted to use studio to clone a github library like this:

studio create telegram-bot-sdk --git https://github.com/irazasyed/telegram-bot-sdk

Then I went to my project root and attempted to require the library:

composer require irazasyed/telegram-bot-sdk expecting studio to create a symlink to the local copy. That didn't happen and all I got was the library saved in the vendor folder as normal.

Having spoken with @franzliedke, he suggested to try using the dev-master version for my composer require which I did:

composer require irazasyed/telegram-bot-sdk:dev-master and suddenly everything worked* fine.

I hope this helps someone else.

*Well not actually the first time. There was a problem creating the symlink but that was fixed by running vagrant as admin.

Hello! Actually I'm not about a bug, but this applies to the simultaneous use of the studio and phpstorm. When I create a symlink to an existing package using studio, it contains a vendor folder with its own dependencies, unlike any other non-local package. That a reason why phpstorm spends a lot of time to index that folder and slows down after, because all nested classes now are duplicated in multiple locations.

I tried to mark project/vendor/me/package/vendor directory as excluded in phpstorm, but it doesn't help ever or helps partially. If I use studio to connect more than one package, work becomes hell, because phpstorm stucks every few seconds.

Has anyone encountered a similar problem and how was it solved?

Hi,

here are a couple of cases where install fails with Composer 2, while install Composer 1 works fine (doesn't matter if Studio symlinks the repo or not). To test, you can use this repo as a reproducer:

https://github.com/emodric/studio-composer2

To get it up and running:

git clone https://github.com/emodric/studio-composer2
cd studio-composer2
mv case1/repos/polyfill/..git case1/repos/polyfill/.git
mv case2/repos/polyfill/..git case2/repos/polyfill/.git
mv case3/repos/polyfill/..git case3/repos/polyfill/.git

Case 1: Version in composer.json (~1.20.0) and local version (1.21.0) missmatch. Composer 1 would just install 1.20.0 from Packagist and be done with it. Composer 2 fails the install.

~/www/studio/case1 $ composer install

[Studio] Loading path repos/*
Loading composer repositories with package information
Updating dependencies (including require-dev)
Package operations: 9 installs, 0 updates, 0 removals
  - Installing symfony/polyfill (v1.20.0): Downloading (100%)         
  - Installing symfony/process (v5.2.1): Loading from cache
  - Installing symfony/filesystem (v5.2.1): Loading from cache
  - Installing symfony/string (v5.2.1): Loading from cache
  - Installing psr/container (1.0.0): Loading from cache
  - Installing symfony/service-contracts (v2.2.0): Loading from cache
  - Installing symfony/console (v5.2.1): Loading from cache
  - Installing franzl/studio (0.15.0): Loading from cache
  - Installing symfony/intl (v5.2.1): Loading from cache
Writing lock file
Generating autoload files
8 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
Symfony recipes are disabled: "symfony/flex" not found in the root composer.json

~/www/studio/case1 $ composer2 install

No lock file found. Updating dependencies instead of installing from lock file. Use composer update over composer install if you do not have a lock file.
[Studio] Loading path repos/*
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires symfony/polyfill ~1.20.0, it is satisfiable by symfony/polyfill[v1.20.0] from composer repo (https://repo.packagist.org) but symfony/polyfill[dev-main, 1.21.x-dev (alias of dev-main)] from path repo (repos/*) has higher repository priority. The packages with higher priority do not match your constraint and are therefore not installable. See https://getcomposer.org/repoprio for details and assistance.

Case 2: Version in composer.json (~1.21.0) and local version (1.21.0) match. This is using a stable requirement. Composer 1 would just install 1.21.0 from Packagist and be done with it. Composer 2 fails the install.

~/www/studio/case2 $ composer install

[Studio] Loading path repos/*
Loading composer repositories with package information
Updating dependencies (including require-dev)
Package operations: 8 installs, 0 updates, 0 removals
  - Installing symfony/polyfill (v1.21.0): Downloading (100%)         
  - Installing symfony/process (v5.2.1): Loading from cache
  - Installing symfony/filesystem (v5.2.1): Loading from cache
  - Installing symfony/string (v5.2.1): Loading from cache
  - Installing psr/container (1.0.0): Loading from cache
  - Installing symfony/service-contracts (v2.2.0): Loading from cache
  - Installing symfony/console (v5.2.1): Loading from cache
  - Installing franzl/studio (0.15.0): Loading from cache
Writing lock file
Generating autoload files
7 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
Symfony recipes are disabled: "symfony/flex" not found in the root composer.json

~/www/studio/case2 $ composer2 install

No lock file found. Updating dependencies instead of installing from lock file. Use composer update over composer install if you do not have a lock file.
[Studio] Loading path repos/*
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires symfony/polyfill ~1.21.0, it is satisfiable by symfony/polyfill[v1.21.0] from composer repo (https://repo.packagist.org) but symfony/polyfill[dev-main, 1.21.x-dev (alias of dev-main)] from path repo (repos/*) has higher repository priority. The packages with higher priority do not match your minimum-stability and are therefore not installable. See https://getcomposer.org/repoprio for details and assistance.

Case 3: Version in composer.json (~1.21.0@dev) and local version (1.21.0) match. This is using a dev requirement. Composer 1 and Composer 2 work OK and symlink the package, so no need for example output.

Amazing project,

I was putting together some new packages, and when using studio, if I run

`studio load /path/to/packages/*' it returns an error with this output

Too many arguments, expected arguments "command" "path".


load <path>

Also, I've noticed in some projects when I create a new project, and then use the following:

studio load path/to/project/project-a this works fine, but if I try something like

composer require roni-estein/package-a I throws this error:

[InvalidArgumentException]
  Could not find a matching version of package roni-estein/laravel-commands. Check the package spelling, your version constraint and that the package is 
available in a stability which matches your minimum-stability (dev).

However, if I add the package to composer.json, and composer update everything works.

Is that an expected behavior? If so, can I contribute a PR to make the README more specific.

Thanks.

Hi,

I'm trying to write a command that runs composer require and use Studio. Currently, Studio is only loaded on update and install commands.

After trying many different events, I found out that it's possible to use the PluginEvents::PRE_COMMAND_RUN event. Since it's very generic, the command name should be check beforehand, using PreCommandRunEvent::getCommand(). This event could be used for all commands: install, require and update.

By the way, this would allow us to use Studio with create-project command, without using --repository option :grin:

I can provide a PR.

Hi,

First thanks for this great package. I love it!

I'm using Laravel Mix to merge a package manifest file into the main application's manifest file. The way I'm achieving this is by setting the public path with a relative path:

mix.setPublicPath('./../../../../../public').mergeManifest();

This doesn't work because of the symlink. If I were to give an absolute path or remove the symlink (and treat the package as a real composer package) it works.

Any ideas on how I could use relative paths with the symlink in play? (Sorry in advance if this is an issue with my own ignorance instead of an issue with your package)

Thanks! Cheers.

Edit: Digging up more info to come up with a solution. I noticed the symlink is on the package name, not the package namespace. So there's what the structure looks like for the vendor folder:

- vendor
--- packagenamespace (folder)
------- packagename (symlink) --> ../../../my-custom-path/packagenamespace/packagename/

Here's my studio.json file in case it's relevant:

{
    "version": 2,
    "paths": [
        "/var/www/composer-local/*"
    ]
}