PrismarineJS / PrismarineJS/node-minecraft-assets
When using pnpm, the correct filepath cannot be resolved.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 22
- Forks
- 21
- Avg merge
- 50m
- Merged PRs (30d)
- 2
Description
The expected filepath is
mine_test\node_modules\minecraft-assets\minecraft-assets\data\1.21.8\block\heavy_core.png,
but the resolved filepath is
mine_test\node_modules\.pnpm\minecraft-assets@1.17.0\node_modules\minecraft-assets\minecraft-assets\data\1.21.8\block\heavy_core.png.
Contributor guide
No contributing guide indexed for this repository
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 reproducing the filepath resolution with pnpm and compare the expected path against the resolved .pnpm path shown in the issue. Trace the package's asset lookup entry point; done means the expected minecraft-assets path resolves correctly under pnpm without breaking the existing lookup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100