Can't specify destination folder for library!
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
The issue does not name a source file, test, or entry point. Start by tracing how the destination and files settings are interpreted for the unpkg provider, then determine how a package path such as dist/popper.js could be copied into the configured destination root. Done means the configuration produces PopperJS/popper.js without the dist folder and existing package lookup still works.
Written by the indexing model from the issue text.
Description
Libman doesn't support the concept of moving files, which makes it unusable! In my configuration file below, the entire folder hierarchy in the PopperJS folder. All I want to do is copy dist/popper.js to PopperJS to get the following:
\PopperJS
- popper.js
Instead I get this:
\PopperJS
\dist
-popper.js",
There's no way to specify moving the file to the root. Instead, it creates the "dist" folder. If you try to remove the "dist" from the "files", it won't find the file in the package. Is there a way to specify the final directory?
{
"provider": "unpkg",
"library": "popper.js@1.14.2",
"destination": "Themes/Vigoda/Content/PopperJS",
"files": [
"dist/popper.js",
]
}
- Dominant language
- C#
- Stars
- 486
- Forks
- 91
- PR merge metrics
- No merged PRs in 30d
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.
More from aspnet/LibraryManager
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
aspnet/LibraryManager#824 · 1 comment · 3 reactions ·
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
aspnet/LibraryManager#804 · 2 reactions ·
-
Difficulty 1/5 Under an hour Newbie friendliness 48/100
aspnet/LibraryManager#829 · 1 comment · 3 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
aspnet/LibraryManager#820 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
aspnet/LibraryManager#808 · 5 comments ·
All issues in aspnet/LibraryManager
Similar issues
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Type: enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
apache/arrow-adbc#4809 ·
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
microsoft/vscode-azurefunctions#5197 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
microsoft/microsoft-ui-reactor#1274 ·