Discussion: Extensibility - Who wants to extend LibMan?

[justcla]

Would you like to extend LibMan for your own purposes? If so, what are your needs?

Do you want to create a new provider for serving library files? If so:

• Which provider/s are you looking to create?
• What kind of properties would your provider need?

More generally, what are you looking for in an extensibility model?

[xzegga]

In my case, I am interested in the ability to add git repository as a provider. There are several useful libraries that are not available on cdnjs but in GitHub repository.

[RobJohnston]

I echo what @xzegga suggested about a git repo provider. However, there is a work-around for this via jsdelivr. See https://www.jsdelivr.com/features#gh

For example, WET-BOEW is not available on any provider:

{
  "version": "1.0",
  "defaultProvider": "jsdelivr",
  "libraries": [
    {
      "library": "wet-boew/[email protected]",
      "destination": "wwwroot/lib/wet-boew/dist/themes-gc-intranet"
    },
    {
      "library": "wet-boew/[email protected]",
      "destination": "wwwroot/lib/wet-boew/dist/wet-boew/"
    }
  ]
}

I think the same format, but replacing "jsdelivr" with "github", could be the way to go.

EDIT: Reference https://github.com/aspnet/LibraryManager/issues/67#issuecomment-387953524

[pabrams]

How can wet-boew not be available on any provider? How do they expect us to use it, then? I can testify that it's not available via jsdelivr (not consistently, anyway).