When using pnpm, the correct filepath cannot be resolved.

[wupengabc]

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.

[wupengabc]

At first I suspected this problem was caused by pnpm, because the resolved file path was incorrect when loading textures from minecraft-assets. However, after further investigation, it seems the root cause is actually related to incorrect item texture paths returned by the project.

For example, when retrieving the texture for heavy_core, the returned path may contain block/ instead of blocks/. This results in a file path that does not exist.

Workaround

Replacing block/ with blocks/ fixes the problem in my case:

let texture = assets.getTexture("heavy_core")

if (texture.includes("block/") && !texture.includes("blocks/")) {
texture = texture.replace("block/", "blocks/")
}

const texture_base64 =
"data:image/png;base64," +
fs.readFileSync(
path.join(
__dirname,
"./node_modules/minecraft-assets/minecraft-assets/data/",
assets.version,
texture + ".png"
),
"base64"
)

console.log(texture_base64)
Summary
The issue does not appear to be caused by pnpm.
Instead, some texture paths returned by assets.getTexture() seem to reference block/ instead of blocks/.
Manually replacing the path resolves the issue.