https://github.com/aspnet/LibraryManager
https://github.com/aspnet/LibraryManager
client-side library-management visual-studio-extension
Last synced: 9 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/aspnet/LibraryManager
- Owner: aspnet
- License: mit
- Created: 2017-03-30T04:46:16.000Z (over 8 years ago)
- Default Branch: main
- Last Pushed: 2025-01-11T00:21:18.000Z (11 months ago)
- Last Synced: 2025-03-10T06:10:26.480Z (9 months ago)
- Topics: client-side, library-management, visual-studio-extension
- Language: C#
- Homepage:
- Size: 4.67 MB
- Stars: 464
- Watchers: 38
- Forks: 83
- Open Issues: 94
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Contributing: .github/CONTRIBUTING.md
- License: LICENSE.txt
- Code of conduct: CODE-OF-CONDUCT.md
- Security: SECURITY.md
Awesome Lists containing this project
- awesome-dotnet-core - LibMan CLI - 安装第三方库的工具. (框架, 库和工具 / 工具)
- fucking-awesome-dotnet-core - LibMan CLI - Client-side content manager for web apps. (Frameworks, Libraries and Tools / Tools)
- awesome-dotnet-core - LibMan CLI - Client-side content manager for web apps. (Frameworks, Libraries and Tools / Tools)
- awesome-dotnet-core - LibMan CLI - Client-side content manager for web apps. (Frameworks, Libraries and Tools / Tools)
README
# Microsoft Library Manager
Install and consume 3rd-party client-side libraries with ease.
[](https://dev.azure.com/azure-public/vswebtools/_build/latest?definitionId=43&branchName=main)
## Reasons to use LibMan
1. For apps not currently using another package manager
2. For projects where you think Bower and npm are overkill
3. For developers that don't want to use Bower/Yarn or npm
4. For developers that value simplicity in their tools
5. For using custom or private packages/files
6. For orchestrating file placement within your project
## Reasons NOT to use LibMan
1. Developer/team likes using tools such Bower, Yarn or npm
2. For apps that uses WebPack or Browserify for module loading/bundling
## Features
- Add any library from [cdnjs.com](https://cdnjs.com/), [jsdelivr.com](https://www.jsdelivr.com/), or [unpkg.com](https://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
## Installation
- Fully integrated into Visual Studio 2017 and newer
- Available as an add-in for Visual Studio for Mac
- From the main menu, open the Extensions Manager dialog.
- Select the Gallery tab.
- Expand IDE extensions.
- Select the Library Manager addin
- Click the Refresh button if the addin is not visible.
- Click Install… to install the addin.
- Restart Visual Studio for Mac.
Please read the [LibMan support in Visual Studio for Mac blog post](https://lastexitcode.com/blog/2019/07/13/LibManSupportInVisualStudioMac8-1/) for more details
- Available as a dotnet global tool - [Microsoft.Web.LibraryManager.Cli](https://www.nuget.org/packages/Microsoft.Web.LibraryManager.Cli/)
## Getting started
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.
## libman.json
### Context menu
Right-click `libman.json` in Solution Explorer to access commands that help managing the libraries.
### Intellisense
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](https://github.com/aspnet/LibraryManager/wiki/libman.json-reference) for more information.
### Light bulbs
Inside libman.json there are light bulbs that show up with helpful commands.
## Telemetry
The Visual Studio experience for Library Manager follows all of the settings for telemetry from Visual Studio.
## Road map and release notes
See the [CHANGELOG](CHANGELOG.md) for road map and release notes
# Feedback
Check out the [contributing](.github/CONTRIBUTING.md) page to see the best places to log issues and start discussions.
# Reporting Security Issues
Please refer to [SECURITY.md](SECURITY.md)
## Trademarks
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.