aspnet / LibraryManager

Other
446 stars 78 forks source link
client-side library-management visual-studio-extension

Microsoft Library Manager

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

Build Status

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

Installation

Context menu

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.

context menu libman.json

Intellisense

Edit the libman.json file to install libraries. Every time the file is saved, Visual Studio will install/restore the packages.

libman.json

See libman.json reference for more information.

Light bulbs

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

Light bulbs

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