Yarn install --offline fails for scoped package with file resolution override · yarnpkg/yarn#4909

(3 评论) (0 反应) (1 负责人)JavaScript (41,514 star) (2,731 fork)batch import

cat-bughelp wantedtriaged

描述

What is the current behavior?

Set up a project with a local tarball mirror and pruning (Sample Project).
Set the resolution for a scoped package to a file in package.json.
Clear the global yarn cache.
Run a yarn install --offline. Yarn will first try and resolve the package to the tarball which will fail. It will then look in the global cache but the scoped cache dir (in this case npm-@types) doesn't exist and the install will fail here.

This seems like a very niche use case but our CI machines do a build with this exact setup so we can't use file resolutions until this is resolved.

@lelandrichardson

技术栈: javascriptnodejs
领域: clibuild systemdeveloper experience
议题类型: bug
难度: 3
预计时间: 1-2 days
活动状态: stale
清晰度: clear
前置要求: Familiarity with YarnUnderstanding of npm scoped packagesAbility to debug JavaScript
新手友好度: 30
研究方向: Examine the npm resolver.js file, specifically the offline resolution logic around line 109. Identify why the scoped cache directory (e.g., npm @types) is not created before attempting to access it. The fix likely involves ensuring the directory exists or modifying the cache lookup to handle missing directories gracefully. Also consider the resolution override from package.json and how it interacts with the tarball mirror. Refer to the sample project linked in the issue for reproduction steps.