yarnpkg/yarn

Yarn install --offline fails for scoped package with file resolution override

Open

#4,909 opened on Nov 12, 2017

View on GitHub
 (3 comments) (0 reactions) (1 assignee)JavaScript (41,514 stars) (2,731 forks)batch import
cat-bughelp wantedtriaged

Description

What is the current behavior?

  1. Set up a project with a local tarball mirror and pruning (Sample Project).
  2. Set the resolution for a scoped package to a file in package.json.
  3. Clear the global yarn cache.
  4. 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

Contributor guide

Tech stack
javascriptnodejs
Domain
clibuild systemdeveloper experience
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Familiarity with YarnUnderstanding of npm scoped packagesAbility to debug JavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
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.