Unknown downloader type

[Selion05]

[InvalidArgumentException] Unknown downloader type: . Available types: git, svn, fossil, hg, perforce, zip, rar, tar, gzip, xz, phar, file, path.

Not sure where this error comes from but I often get it if I change something in composer.json...

To get rid of it I have to delete the symlinked folder in vendor

[froemken]

Sometimes it helps to git reset the content of the folders. Sometimes it helps, as you mentioned, to remove the symlinked folders. If you have changed something to your repositories and add some new path to a package which already exists, please be sure to delete the target folder out of vender before.

Would be cool to have a better error message here: Hey, please check/delete/whatever target folder of package x/y before updating.

[berni2288]

I got the same error with 0.14.0-beta1 and private packages. Now after cleaning the vendor directory and running composer update I get the following error:

  [InvalidArgumentException]                                              
  Package xxx/xxx-9999999-dev seems not been installed properly

[mahfuz10]

1. I deleted the vendor directory rm -Rf vendor/ , and
2. I have run composer update Now here is no error. It solved my problem.

[p2made]

I've also had this problem. Like @mahfuz10 deleting the vendor directory fixed it.

[franzliedke]

Can any of you provide reproducible instructions or a repository where this problem can be reliably produced, so that I can investigate a bit more?

[p2made]

I suspect it's a composer issue. The projects where this issue occurs for me don't load franzliedke/studio at all.

[caleeli]

I my case, for testing purposes I've created a symbolic link inside the vendor directory, this caused the error

  [InvalidArgumentException]                                                                                              
  Unknown downloader type: . Available types: git, svn, fossil, hg, perforce, zip, rar, tar, gzip, xz, phar, file, path.  

when I execute the composer install

[matthijskooijman]

I've seen the same error, after installing a package from a local directory (using these instructions: https://barryvanveen.nl/blog/44-package-development-run-a-package-from-a-local-directory) and then trying to remove it again.

[cobhimself]

Any news on a fix for this?