Composer update error - update dependencies? about super_closure HOT 9 CLOSED

I have the same problem. Solved it with: composer update --prefer-dist until I investigate further.

from super_closure.

Just did:

$ cat composer.json 
{
    "require": {
        "jeremeamia/superclosure": "~1.0.0"
    }
}
$ composer.phar install
Loading composer repositories with package information
Installing dependencies (including require-dev)
  - Installing nikic/php-parser (v0.9.4)
    Downloading: 100%         

  - Installing jeremeamia/superclosure (1.0.1)
    Downloading: 100%         

Writing lock file
Generating autoload files

This works just fine for me. Try self-updating composer maybe?

from super_closure.

Same here, works smoothly. Some other dependency is probably excluding nikic/php-parser:0.9.* - this is not an issue of super_closure imo

from super_closure.

I'm also suddenly having this issue, also with Laravel.

Problem 1
    - Installation request for jeremeamia/superclosure 1.0.1 -> satisfiable by jeremeamia/SuperClosure[1.0.1].
    - jeremeamia/SuperClosure 1.0.1 requires nikic/php-parser ~0.9 -> no matching package found.
Problem 2
    - jeremeamia/SuperClosure 1.0.1 requires nikic/php-parser ~0.9 -> no matching package found.
    - laravel/framework 4.1.x-dev requires jeremeamia/superclosure 1.0.* -> satisfiable by jeremeamia/SuperClosure[1.0.1].
    - Installation request for laravel/framework 4.1.x-dev -> satisfiable by laravel/framework[4.1.x-dev].

from super_closure.

Fixed it by removing the vendor dir and composer.lock and just do a fresh install. So maybe some Composer caching issue?

from super_closure.

Thanks for the help everyone. Of all the suggested solutions, the only one I tried was barryvdh's (remove the vendor dir and composer.lock, do a fresh install). It worked! I'm closing this because it looks like it has more to do with Composer than with Super Closure.

from super_closure.

It's mainly due to reason nikic/PHP-Parser@0ac054a commit. When you run update composer still assume dev-master is aliased to 0.9 which cause this issue. And I seen this issue on almost all project that swap dev-master alias.

So removing composer.lock is the best solution right now.

from super_closure.

Ah, interesting. Do I or @nikic need to fix anything? How can these types of things be avoided in the future.

from super_closure.

@jeremeamia it's a composer issue.

composer/composer#1105
composer/composer#1137

There seem to be a WIP PR: composer/composer#1352

from super_closure.