yarnpkg/yarn

yarn fails to install angular application in offline mode

Open

#5123 opened on Dec 25, 2017

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

Description

Issue:

$ yarn install --offline yarn install v1.3.2 [1/4] 🔍 Resolving packages... error Couldn't find any versions for "tslib" that matches "^1.7.1" in our cache (possible versions are ""). This is usually caused by a missing entry in the lockfile, running Yarn without the --offline flag may help fix this issue.

angular is depending on tslib ^1.7.1 https://github.com/angular/angular/blob/master/package.json and there is no 1.7.2 version available; the next available version is 1.8.0

I suspect yarn is not able to make out next minor version and is just looking out for version greater that 1.7.1

in online mode, it is getting installed properly. with a yarn.lock file which mentions dependency as 1.8.1; it gets installed well in offline mode.

Steps to reproduce:

  1. ng new proj1 --skip-install
  2. cd proj1; yarn install --offline

Expected behaviour: yarn should install the node_modules in offline mode.

Contributor guide

Tech stack
javascripttypescriptnodejsangular
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.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Node.js basicsYarn package managerUnderstanding of semverJavaScript/TypeScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Examine the yarn resolver's semver handling in offline mode, focusing on how it matches versions when the exact version is not in cache. Look at the source code in packages/package resolver/src/index.js and related files. Review the issue comments for any proposed fixes or workarounds. Consider writing a test that reproduces the offline resolution failure for a dependency with a caret range.