The popper.js library could not be resolved

[vitaaaly]

Functional impact

I can't restore popper.js today.

Minimal repro steps

I try to restore libraries with this config:

{
  "version": "1.0",
  "defaultProvider": "cdnjs",
  "libraries": [
    {
      "library": "[email protected]",
      "destination": "wwwroot/lib/popper"
    }
  ]
}

Actual result

libman.json : error LIB002: The "[email protected]" library could not be resolved by the "cdnjs" provider

Further technical details

Also I try to use unpkg and another version of popper.js, but I have the same error.

Microsoft Visual Studio Enterprise 2019
Version 16.6.2

[maxd]

I have a lot of similar errors during last month too i.e.:

libman.json : error LIB002: The "[email protected]" library could not be resolved by the "cdnjs" provider

The two big problems here:

1. libman don't write detail information about such error even when verbose logs is enabled. So, there are no standard ways to investigate the reason of this problem on our side.
2. Looks like libman doesn't make several retries to download libraries because when I make several tries I can download all libraries without such errors.

[vitaaaly]

I tried again - library restored!

But @maxd comments seem reasonable.

[RobJohnston]

I like the second point. I get intermittent errors with jsdelivr quite frequently, but trying again often resolves the issue. Maybe implement the "retry" policy using Poly?

[RobJohnston]

I think this is essentially a duplicate of #370, "Providers are unreliable".

[jimmylewis]

Closing as a duplicate.