Just the other day, any composer update or install with this module and library setup in composer is failing.

Firstly, I am 100% correctly setup with the correct composer setup, this module and library has been in 30+ websites for years now, this error only just started.

It seems like the connection for the bower-asset is suddenly broken.

Is anyone else seeing this? Is there a solution to keep this in composer? Or should the library just be manually added to the libraries folder for a temp fix?

Thanks!

composer update
Gathering patches for root package.
> DrupalComposerManaged\ComposerScripts::preUpdate
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires bower-asset/lazysizes ^5.3, found bower-asset/lazysizes[5.3.1] in the lock file but not in remote repositories, make sure you avoid updating this package to keep the one from the lock file.

I also tried npm-asset which did not work

composer require npm-asset/lazysizes:^5.3 -W
./composer.json has been updated
Running composer update npm-asset/lazysizes --with-all-dependencies
Gathering patches for root package.
> DrupalComposerManaged\ComposerScripts::preUpdate
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires npm-asset/lazysizes, it could not be found in any version, there may be a typo in the package name.

Potential causes:
 - A typo in the package name
 - The package is not available in a stable-enough version according to your minimum-stability setting
   see <https://getcomposer.org/doc/04-schema.md#minimum-stability> for more details.
 - It's a private package and you forgot to add a custom repository to find it

Read <https://getcomposer.org/doc/articles/troubleshooting.md> for further common problems.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.

Comments

lindsay.wils created an issue.

rpayanm’s picture

rpayanm
he/him
Primary language Spanish
commented

I have the same error.

This could be related to issues with GitHub servers.
https://www.githubstatus.com/

lindsay.wils’s picture

lindsay.wils commented

OK, that very well could be the issue. Thanks for the response, good to know I'm not the only one :)

carlitus’s picture

carlitus commented

We have the same problem with packages from npm-asset:

Your requirements could not be resolved to an installable set of packages.
  Problem 1
    - Root composer.json requires npm-asset/nouislider ^15.5, found npm-asset/nouislider[15.8.1] in the lock file but not in remote repositories, make sure you avoid updating this package to keep the one from the lock file.

The root of the problem seems the same, but github status it's all green now.