Error installing package using composer
See original GitHub issueComposer gives the following error while installing:
[UnexpectedValueException]
Could not parse version constraint >=~2: Invalid version string "~2"
I used the following commands in an empty folder:
composer clearcache
composer require bower-asset/fullcalendar
That produces the “Cold not parse version constraint” message.
My composer version is: Composer version 1.3.2 2017-01-27 18:23:41
Issue Analytics
- State:
- Created 7 years ago
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Troubleshooting - Composer
Try clearing Composer's cache by running composer clear-cache . Ensure you're installing vendors straight from your composer.
Read more >Error in Install Package using composer in laravel
Error in Install Package using composer in laravel - Stack Overflow. Stack Overflow for Teams – Start collaborating and sharing organizational ...
Read more >Error while installing a package through composer - Laracasts
I have some problems with installing a package, that I would like to share with you. Here is the command. Copy Code composer...
Read more >Troubleshooting PyPI package installation | Cloud Composer
The most common problem with PyPI packages that you might encounter in Cloud ... When a package installation fails, pip reports the detailed...
Read more >Error installing using Composer on Extension talk:Bootstrap
Problem 1 - The requested package mediawiki/bootstrap could not be found in any version, there may be a typo in the package name....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@arshaw I confirm that it’s a bug of my plugin.
There is also a corresponding issue at the
composer-asset-plugin
project: https://github.com/fxpio/composer-asset-plugin/issues/270