Home
Library Manager (“LibMan” for short) is Visual Studio’s client-side library acquisition tool. It provides a lightweight, simple mechanism that helps users find and fetch common library files from external sources (such as CDNJS or UnPkg).
- If your project does not require additional tools (like Node, npm, Gulp, Grunt, WebPack, etc) and you simply want to acquire a couple of files, then LibMan might be for you.
- LibMan lets you specify exactly where the files should be placed inside your project. (No additional build tasks or manual file copying required!)
- LibMan provides the benefit of a much smaller footprint in your web project as it only downloads the files you need. To learn more about the benefits of LibMan, check out this clip of Mads Kristensen talking about the initial prototype in his talk at Microsoft Build 2017.
LibMan is not a package management system. If you’re happily using npm/yarn/(or something else), we encourage you to continue doing so. LibMan was not developed as a replacement for these tools.
LibMan tooling comes as part of the Web Development workload in Visual Studio 2017.
Download Visual Studio 2017 and choose the "Web Development" workload during installation (or modify an existing instance of Visual Studio 2017).
The LibMan Command Line Interface (DotNet CLI tool) can be used separately and can be downloaded from NuGet.
See the following pages for information on how to use LibMan in the various supported scenarios.
- Using LibMan in Visual Studio
- Using LibMan from the Command Line (LibMan CLI)
- Using LibMan in a CI build
- What are providers? How to choose?
- Cdnjs
- UnPkg
- File system