Jimmy Lewis

The `Microsoft.Web.LibraryManager.Build` package is for any MSBuild based build, it isn't `dotnet` specific.

@nickalbrecht I see. After a re-read, I think I better understand the feedback now: the LibMan restore process should hook the project's Restore, not the Build.

I played around with this a little bit, adding some details to the thread in case I don't have time to come back to a fix soon. For my testing...

Revisiting this after #538 and #541. With the original repro (using [email protected]) from a clean directory and clean cache now took me 38 seconds. When the cache is populated it...

We do have (and use) a local cache, but we don't cache library *metadata* for the Unpkg/JSDelivr providers yet. Basically, what happens is: 1. We try to resolve the package...

@BPA8 which version of the package are you using for restore? Libman does have a local cache, but that doesn't help if you're on a fresh build agent. Recent packages...

This issue is still open for a reason 😉 I too would like something in the VS Code space to better support the libman user experience. While I doubt we'd...

This is using cdnjs, right? It looks like they believe there is a version 9000 of that package: https://cdnjs.com/libraries/prism/9000.0.1. Can you try following up with them directly on https://github.com/cdnjs/cdnjs/issues to...

Just quickly jumping in here to say: I'm working on the code change for LibMan, but the rollout will require servicing each version of Visual Studio that includes it (2017,...

Alright, for folks using the [CLI tool](https://www.nuget.org/packages/Microsoft.Web.LibraryManager.Cli) or [MSBuild task](https://www.nuget.org/packages/Microsoft.Web.LibraryManager.Build) could you please update to the latest version (2.1.174) and see if you have any issues with that? From a...