yarnpkg/yarn

yarn global add . fails

Open

#3256 opened on Apr 26, 2017

View on GitHub
 (11 comments) (14 reactions) (0 assignees)JavaScript (41,514 stars) (2,731 forks)batch import
cat-compatibilitygood first issuehelp wantedtriaged

Description

What is the current behavior? Running yarn global add . in the directory of a local module results in:

[1/4] Resolving packages...
error Received malformed response from registry for undefined. The registry may be down.

What is the expected behavior? This may or may not be a question/feature request, but I'm intending to perform the equivalent to

npm install -g .

whereby the local module would be installed from the local code base to exist as a globally installed module. Is this currently possible?

Please mention your node.js, yarn and operating system version. Yarn: 0.23.2 Node: 6.10.2 OS: elementary OS Loki

Contributor guide

Tech stack
javascriptnodejs
Domain
clitoolingdeveloper 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-3 hours
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
basic yarn usagenodejs environment
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate the yarn global add command in the codebase, specifically the package resolution logic. The error 'Received malformed response from registry for undefined' suggests a missing package name or URL. Check the issue comments and any related PRs for more context. The issue may require understanding of how yarn handles global installations and registry requests.