Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Installation of some libraries dramatically slower than alternative tooling

Open
#389 18 comments 10 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp
Domain
performance, tooling

Research direction

Start by running the listed npm, Bower, and LibMan cache-clean installation commands for ckeditor@4.6.2 and compare their timings. Trace the LibMan install path invoked by libman install --provider cdnjs --destination libman_libs/ckeditor; done means uncached installation is substantially closer to the alternative tooling times.

Written by the indexing model from the issue text.

Description

P2
Functional impact

Does the bug result in any actual functional issue, if so, what?

If the library is cached, installation is quick enough. However, without libraries in cache, the performance of installing / restoring a library is dramatically slower than alternatives such as NPM and Bower.

Minimal repro steps

What is the smallest, simplest set of steps to reproduce the issue. If needed, provide a project that demonstrates the issue.

  1. mkdir libman-speed-test
  2. cd libman-speed-test/
  3. npm cache clean --force
  4. bower cache clean
  5. libman cache clean
  6. time npm install ckeditor@4.6.2
  7. time bower install ckeditor#4.6.2 --save
  8. time libman install ckeditor@4.6.2 --provider cdnjs --destination libman_libs/ckeditor
Expected result

What would you expect to happen if there wasn't a bug

LibMan should install / restore the specified library in an amount of time comparable to alternatives such as NPM and Bower.

Actual result

What is actually happening

With the above steps, installing the specified library takes:

  • NPM: 3.63s
  • Bower: 8.49s
  • LibMan: 2m47.92s
Further technical details

Optional, details of the root cause if known

Dominant language
C#
Stars
486
Forks
91
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aspnet/LibraryManager

All issues in aspnet/LibraryManager

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.