No description or website provided.
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Update links to be better suited for this project Oct 18, 2018
art Updated readme Apr 20, 2017
build Changes to use new json immutable tree (#400) Nov 15, 2018
common/tools/VsctToXliff Adding localization files and targets. Using Multilingual App Toolkit… Mar 1, 2018
lib Changes to use new json immutable tree (#400) Nov 15, 2018
src Update versions in vsix manifest Nov 16, 2018
test Temporarily disable couple of JsonHelpersTests Nov 15, 2018
tools/ShimGenerator Rename CLI package to Microsoft.Web.Librarymanager.Cli Aug 6, 2018
.editorconfig Formatting rules (#101) Jun 6, 2018
.gitattributes Add project files. Mar 31, 2017
.gitignore Stress and Perf fixes (#85) Jun 5, 2018
CHANGELOG.md Added Uninstall method on Manifest.cs Mar 31, 2017
Directory.Build.props Fix nuget package properties Aug 6, 2018
Directory.Build.targets Consolidate package versions and metadata (#102) Jun 7, 2018
Install-dotnet.ps1 Update dotnet version used to build CLI tool Jun 14, 2018
LICENSE.txt Added license headers to all .cs files Mar 31, 2017
LibraryManager.Settings.targets Adding localization files and targets. Using Multilingual App Toolkit… Mar 1, 2018
LibraryManager.msbuild Fix nuget package properties Aug 6, 2018
LibraryManager.sln Changes to use new json immutable tree (#400) Nov 15, 2018
README.md Update build status badge. May 9, 2018
appveyor.yml Changes to use new json immutable tree (#400) Nov 15, 2018
nuget.config Resolve the reviewed issues Jun 2, 2018
version.json Changes to use new json immutable tree (#400) Nov 15, 2018

README.md

Microsoft Library Manager

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

AppVeyor 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

  • Add any library from cdnjs.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
  • Optional manifest file (libman.json)
  • Very fast
  • Full Visual Studio 2017 integration

Getting started

Right-click any web project in Solution Explorer and hit Manage Client-side Libraries....

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.