Is there a way to set dependencies or order of execution?

Start by reproducing the failure with the provided libman.json configuration, especially after clearing the downloaded files. Then trace how the unpkg and filesystem providers are executed and determine how ordering or dependency declarations should be represented. Done means a clean restore reliably processes the external library before the filesystem copies, including on CI.

Functional impact

I have a project where I download libraries i.e. bootstrap and then want to use the filesystem provider to move files around. Problem is because the files haven't downloaded before the filesystem provider triggers I get an error

Minimal repro steps

Create a new project and use the following configuration for libman.json

{
  "version": "1.0",
  "defaultProvider": "cdnjs",
  "libraries": [
    {
      "provider": "unpkg",
      "library": "bootstrap@4.3.1",
      "destination": "Resources/Libraries/bootstrap"
    },
    {
      "provider": "filesystem",
      "library": "Resources/Libraries/bootstrap/dist/css",
      "destination": "content/lib/bootstrap/css",
      "files": [
        "bootstrap.min.css",
        "bootstrap.min.css.map"
      ]
    },
    {
      "provider": "filesystem",
      "library": "Resources/Libraries/bootstrap/dist/js",
      "destination": "content/lib/bootstrap/js",
      "files": [
        "bootstrap.min.js",
        "bootstrap.min.js.map"
      ]
    }
  ]
}

If the files don't already exist it will fail.

Expected result

Ideally I'd like there to be an order for providers, i.e. External (web) providers trigger first then local filesystem providers.

Or a way to add a dependency based on other libraries before executing i.e.
"depends": [ "unpkg:bootstrap" ]

Actual result

Depending on if the package has already restored it will either succeed or fail.
Notice this issue because it broke when I compiled on the CI server