-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Your requirements could not be resolved to an installable set of packages. #20
Comments
Synj24, Did you ever figure this out? I'm having the same issue. |
You must Install PHP extension mbstring. sudo apt-get install php-mbstring |
Hi, i am trying to add burdamagazinorg/thunder to the project, because i removed it from the composer.json for update the drupal code and modules. ` Installation failed, reverting ./composer.json to its original content. |
Trying to install thunder after Drupal 8.7.3 Problem 1 How I can solve this?? |
The issue
I'm having issues trying to create a project.
When i run:
composer create-project burdamagazinorg/thunder-project thunder
I get this response:
And when i run
php --ini
it gives me these:Attempted solution
I've tried installing alchemy/zippy with
composer require alchemy/zippy
in my project directory returning:I'm confused as to why when i try to install the package it is complaining about it complains about not having the package i'm trying to install...
I'm probably missing something obvious this is my first time using drupal/thunder/composer.
I found this issue on the drupal-console repo and have tried clearing the cache and installing globally to no avail.
I've searched around and found similar problems for other composer packages but i am unsure of how to resolve these conflicts.
is this an issue with the composer.json file or something to do with the drupal/console package?
System infomation
I'm on an aws instance running ami linux using:
PHP version 7.0.21
Composer version 1.5.2
Node version 4.4.5
Sorry for the massive wall of text, Thanks for your time! 🙇♂️
The text was updated successfully, but these errors were encountered: