enyo/dropzone composer update fails, 5.7.2 does not match the constraint

Just added this module (with Drupal 10) exactly as suggested in the module page (the composer way #1), and while everything seems fine at first, when you run composer update you will get the error:

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires enyo/dropzone ^5.9, 5.7.2, found enyo/dropzone[5.7.2] but it does not match the constraint.

Is there any progress on this ? or any new advice? The install instructions remain the same and I have fallen into the same trap as @kopeboy

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires enyo/dropzone ^5.9, 5.7.2, found enyo/dropzone[5.7.2] but it does not match the constraint.

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

The install instructions were improved and now support the latest versions of both 5 and 6. If you get that error then composer probably got confused between the official versions and the locked version from the repository, update that per documentation.

Following the exact instructions on the home page (for version 5). I put this in my composer.json libraries section:

        {
            "type": "package",
            "package": {
                "name": "enyo/dropzone",
                "version": "5.9.3",
                "type": "drupal-library",
                "dist": {
                    "url": "https://github.com/dropzone/dropzone/releases/download/v5.9.3/dist.zip",
                    "type": "zip"
                }
            }
        }

I run `composer require drupal/dropzonejs enyo/dropzone` and I get the exact output mentioned by @kopeboy in #4.

My previous installation had `^5.7` as the enyo/dropzone constraint. I also tried requiring "enyo/dropzone:^5.9" and the same response came out: "Root composer.json requires enyo/dropzone ^5.9, 5.7.2, found enyo/dropzone[5.7.2] but it does not match the constraint"

In the end, while I can update drupal/dropzonejs to latest, I am unable to update enyo/dropzone to 5.9.3 and am stuck on 5.7.2. This is not breaking the site, but obviously it is less than ideal. What is interesting is that dependabot keeps trying to update enyo/dropzone to 5.9.3 and I get pull requests for an updated composer.lock with the new 5.9.3 path in it, but my builds fail of course when my CI tries to build the dependabot PRs.

Seems like there is a hangup somewhere that I certainly cannot identify. --with-all-dependencies does not fix this, nor does a relaxation of minimum stability.

Try defining it as dropzone/dropzone and requiring that. Are you certain that you have no other existing repository definition with the different version?