GraphQL Responsive Image module throws error on install

I'm not familiar with that or related modules, but there are problems installing that module from the command line (on D10). The module declares "graphql:graphql_core" as a dependency but the composer error message references "drupal/graphql_core".

I have the same experience as #2 and this is also the current experience in the browser too.

But the issue is describing a situation where composer can't resolve the dependencies and it is failing ungracefully. Do we have a way to reproduce this?

The module declares "graphql:graphql_core" as a dependency but the composer error message references "drupal/graphql_core"

This seems normal to me; graphql:graphql_core is a Drupal-specific syntax for dependencies, but drupal/graphql_core is what that name will resolve to when Composer looks for it.

The error in the issue summary looks legitimate, as far as I can tell. Composer's error output has always been shoot-me-in-the-eye awful to pick through, but from what I'm seeing there, it looks like Composer is only "seeing" GraphQL 3.0-alpha1 to 3.0, which (from what I can see on the list of GraphQL releases) didn't have compatibility with Drupal 9 or later.

I guess the question, then, is why it would only be looking at those old-ass releases of GraphQL. Usually it's because something else you have installed, is not compatible with them.

The thing to do is probably to go to your command line and run this from your project root: composer prohibits drupal/graphql:>3.0.0. If you ran that, what was the output? (If Composer don't have a prohibits command, try composer why-not instead.)

Recategorizing this as a support request, at least for now, because it's not clear that this was actually caused by any real problem in Project Browser or Package Manager.

But the issue is describing a situation where composer can't resolve the dependencies and it is failing ungracefully. Do we have a way to reproduce this with a different module?

@sime – Yes. On a clean install of Drupal with Gitpod, I had an ungraceful failure with the installation of Config Pages:
StageEventException: Problem detected in lock file during stage operations. There appear to be no pending Composer operations because the active lock file (/var/www/html/composer.lock) and the staged lock file (/tmp/.package_manager9d13a6a4-2b13-4d12-a842-06aa7b39c4a8/pF8CYYRk6EtjiRw3UCKJSTXcbtrAJwZX/composer.lock) are identical.

Although, this probably constitutes a separate issue ^^, it's an example of a failure that a non-developer would likely not be able to resolve.

@kdomenick, that error is coming from Package Manager and I'm surprised you got it; it means that the lock file didn't change, which would suggest that no packages were installed or updated in the installation sandbox. (Which is weird -- if you're adding a module to the sandbox, you'd absolutely expect it to change.)

Is Config Pages physically present in the code base before you tried installing it?

On the GraphQL module… I worked with GraphQL 3.x on both Drupal 9 and 10. It is compatible with those core versions; however, I think the issue here may be that GraphQL 3.x has a different project architecture than GraphQL 4.x.

3.x has a sub module called “GraphQL Core” that does not exist in the 4.x version. (In 3.x, the sub module shows up separately in the Extend UI and in core.extension.yml.)

If you’re running GraphQL 4.x and try to install the GraphQL Responsive Image module (which relies on 3.x), it makes sense that it fails, because it can’t find that GraphQL Core sub module.

@jonycp - Are you running GraphQL 4.x?

@phenaproxima – I don't see Config Page in the sandbox codebase, either in the modules/contrib directory or in composer.json. Weird one.