Install and consume 3rd-party client-side libraries with ease.
- For apps not currently using another package manager
- For projects where you think Bower and npm are overkill
- For developers that don't want to use Bower/Yarn or npm
- For developers that value simplicity in their tools
- For using custom or private packages/files
- For orchestrating file placement within your project
- Developer/team likes using tools such Bower, Yarn or npm
- For apps that uses WebPack or Browserify for module loading/bundling
- Add any library from cdnjs.com, jsdelivr.com, or unpkg.com
- Add any file from file system, network share or remote URL
- Only add the file(s) you need
- Can install any file into any folder in your project/solution
- Very fast
- IDE integration pre-installed with Visual Studio 2017 and newer
- Available as a dotnet global tool - Microsoft.Web.LibraryManager.Cli
- MSBuild integration as a NuGet package - Microsoft.Web.LibraryManager.Build
In Visual Studio, right-click any web project in Solution Explorer and hit Manage Client-side Libraries....
This will create a libman.json file in the root of the project.
Or with the CLI tool, run libman init to create a libman.json in the current folder.
Right-click libman.json in Solution Explorer to access commands that help managing the libraries.
Edit the libman.json file to install libraries. Every time the file is saved, Visual Studio will install/restore the packages.
See libman.json reference for more information.
Inside libman.json there are light bulbs that show up with helpful commands.
The Visual Studio experience for Library Manager follows all of the settings for telemetry from Visual Studio.
See the CHANGELOG for road map and release notes
Check out the contributing page to see the best places to log issues and start discussions.
Please refer to SECURITY.md
This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.