microsoft / microsoft/component-detection
Feature Request - Add support for LibMan manifest (libman.json)
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 553
- Forks
- 135
- Avg merge
- 20h 58m
- Merged PRs (30d)
- 6
Description
See: Use LibMan with ASP.NET Core in Visual Studio
Repos using this are not normally configured with a package manifest other then libman.json. The dependencies are then vendored/installed in target directories (that further do not contain manifests) - ex: wwwroot/lib/lodash/ .
AB#2114917
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the repository's existing component and manifest-detection entry points, then compare their handling with the libman.json format described in the linked ASP.NET Core documentation. Check how dependencies vendored under paths such as wwwroot/lib/lodash/ would be discovered; done means LibMan dependencies are detected without requiring another package manifest.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100