-
Notifications
You must be signed in to change notification settings - Fork 160
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
Merge-plugin beating out main composer on composer 2. #216
Comments
Here's my composer file if that helps. The conflict is coming from ckeditor/link. The file I'm including in the merge-plugin for webform also loads ckeditor/link but an older version. I would expect that my composer file would beat anything being merged or is that wrong? { |
wondering if anyone has found a solution? We had to downgrade composer back to get this to work. |
Following up again if anyone has a solution or an alternative to composer merge plugin? |
Grabbed your config and after removing some patches from your list everything installed cleanly without any errors. Couldn't recreate your "higher priority" error. |
So on composer 2. Installing webform doesn't conflict with ckeditor/link? |
This is in reference to the discussion at the end of #184 (comment)
Getting an error
"from package repo (defining 1 package) has higher repository priority. The packages with higher priority do not match your constraint and are therefore not installable."
I tried all the settings but it seems the merge-plugin is beating out my main composer.
So with these Drupal sites we don't have a lot of control over other modules composer files. Ideally the main composer file should beat out the merged stuff
The text was updated successfully, but these errors were encountered: