Problem/Motivation

When starting with a new/clean composer managed Drupal 10 project, Mercury Editor only installs up to alpha4.

composer require

When trying to force latest alpha release, you get composer error:

composer

error

Steps to reproduce

Create a new Drupal 10 project through composer and add ME and Style Options to project: (as well as paragraphs, LP, etc.)
- composer create-project drupal/recommended-project my_site_name
- change composer minimum-stability to dev
- composer require 'drupal/mercury_editor:^2.1@alpha'
- composer require 'drupal/style_options:^1.0@alpha'

Proposed resolution

I believe changing ME composer dependency off of Style Options dev to alpha.

- "drupal/style_options": "1.0.x-dev@dev" => "drupal/style_options:^1.0@alpha"

CommentFileSizeAuthor
Screenshot 2024-02-26 at 4.37.23 PM.png113.51 KBesch
Screenshot 2024-02-26 at 4.36.49 PM.png192.43 KBesch
Screenshot 2024-02-26 at 4.27.21 PM.png145.62 KBesch

Issue fork mercury_editor-3423937

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

esch created an issue. See original summary.

esch opened merge request !45

esch’s picture

esch commented

I would also recommend adding composer "require-dev" to support development requirements.

chaz.chumley’s picture

chaz.chumley commented

I am experiencing this issue as well. Any suggestions on how to resolve.

chaz.chumley’s picture

chaz.chumley commented

Still waiting on a fix so we can use latest version.

pixelwhip made their first commit to this issue’s fork.

mortona2k’s picture

mortona2k commented

Hey @chaz.chumley I have a reliable workaround for this kind of problem, where there are no compatible releases of a module that should otherwise work.

I download modules with composer conflicts to modules/pinned, and make changes like in the info.yml and composer files. I usually push those changes to an issue fork, or if there's already a fix, apply the patch manually within the module dir. Regular composer patches don't work to fix dependency conflicts because they're checked before the patch is applied.

If there are other composer dependencies that are needed to install the module, you can copy them into your root composer.json, or configure a custom path repository pointing to the pinned directory. https://getcomposer.org/doc/05-repositories.md#path

pixelwhip closed merge request !45

pixelwhip reopened merge request !45

pixelwhip’s picture

pixelwhip commented

Closed and reopened the MR in an attempt to trigger tugboat and tests

  • pixelwhip committed 4ba50e19 on 2.1.x authored by esch 
    Issue #3423937 by esch, pixelwhip: Composer managed Drupal only installs...
pixelwhip’s picture

pixelwhip commented
Status: Active » Fixed

This fix has been released as part of 2.1.x-alpha16

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.