Microsoft Library Manager

Install and consume 3rd-party client-side libraries with ease.

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, 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

The Library Manager extension is available from the Visual Studio for Mac extensions gallery. To install the extension:

• 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.

Using Library Manager

Please read the LibMan support in Visual Studio for Mac blog post

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 for more information.

Light bulbs

Inside libman.json there are light bulbs that show up with helpful commands.

Road map and release notes

See the CHANGELOG for road map and release notes

Feedback

Check out the contributing page to see the best places to log issues and start discussions.

Reporting Security Issues

Please refer to SECURITY.md