yarn install fails for unpublished and linked-in dependency

[viliusl]

Do you want to request a feature or report a bug?
Bug

What is the current behavior?
Given I have a module listed in dependencies/devDependencies that is not yet published and is linked-in to my module, yarn install fails.

If the current behavior is a bug, please provide the steps to reproduce.
https://github.com/viliusl/yarn-link-issue

What is the expected behavior?
For yarn to not fail during install when yet-unpublished dependency is linked-in.

Please mention your node.js, yarn and operating system version.

• node: v6.9.4
• yarn: 0.19.1
• os: macOS 10.12

[alexdohmen]

+1 same here
error: error Couldn't find package "the-next-big-module" on the "npm" registry.

[npiguet]

I have to add my voice to this one. Tested with yarn 0.18.1 and node 5.10.1.

The output from yarn install looks like:

Running 'yarn install' in /home/npiguet/workspace/epb/epb-web-components/epb-charts
yarn install v0.18.1
info No lockfile found.
warning epb-charts@1.0.0: No license field
[1/4] Resolving packages...
error An unexpected error occurred: "https://private.reposiroty/repository/npm/private-module: Not found".
info If you think this is a bug, please open a bug report with the information provided in "/path/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

yarn-error.log contains the following info:

Arguments: 
  /projectpath/node/node /projectpath/node/yarn/dist/bin/yarn.js install

PATH: 
  /projectpath/node:/projectpath/node/yarn/dist/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:

Yarn version: 
  0.18.1

Node version: 
  5.10.1

Platform: 
  linux x64

npm manifest: 
  {
    "name": "private-module",
    "version": "1.0.0",
    "description": "Description",
    "main": "./dist/private-module.js",
    "typings": "./dist/index",
    "globalDependencies": {
      "react": "0.14.8",
      "react-dom": "0.14.8"
    },
    "devDependencies": {
      "gulp": "3.9.1"
    },
    "scripts": {
      "typings-install": "typings install"
    },
    "dependencies": {
      "ts-loader" : "1.3.3",
      "process-nextick-args": "1.0.7",
      "private-module": "1.0.0"
  
    }
  }

yarn manifest: 
  No manifest

Lockfile: 
  No lockfile

Trace: 
  Error: https://private-registry/repository/npm/private-module: Not found
      at Request.params.callback [as _callback] (/projectpath/node/yarn/dist/lib/util/request-manager.js:309:18)
      at Request.self.callback (/projectpath/node/yarn/dist/node_modules/request/request.js:186:22)
      at emitTwo (events.js:100:13)
      at Request.emit (events.js:185:7)
      at Request.<anonymous> (/projectpath/node/yarn/dist/node_modules/request/request.js:1081:10)
      at emitOne (events.js:90:13)
      at Request.emit (events.js:182:7)
      at IncomingMessage.<anonymous> (/projectpath/node/yarn/dist/node_modules/request/request.js:1001:12)
      at IncomingMessage.g (events.js:273:16)
      at emitNone (events.js:85:20)

[MikeTaylor]

I have this problem, too, and it's a killer. I means that before I can start development work on a new package linked in via yarn link, I first have to release a null version -- which will then be ignored, but whose presence will allow the link to work. I am keen to see this fixed.

[bestander]

As reported in #1214 (comment)

I'm getting this issue on version 0.24.5.
I have some packages that i developed and they are not published on any server, they are just linked.
My projects uses this linked packages and some published packages like express or bluebird.
when I try to run "yarn" to install all or a specific package it returns the error:

error Couldn't find package "package-name" on the "npm" registry
steps to reproduce:

cd path/to/a-dev-package
yarn link
cd path/to/a/project
yarn link a-dev-package
yarn add bluebird
it returns :
error Couldn't find package "a-dev-package" on the "npm" registry

[dandv]

Same problem with 0.27.5. The only workaround was to not list my linked package among the dependencies in package.json, but then I get a linter warning on the require/import line that the dependent module is not listed in the dependencies.

I'd rather not look into para-package-management workarounds like yalc.

[arcanis]

I'm not sure this is a bug - even if you're using yarn link to install the dependency, we still need to resolve it according to its range in order to put it inside the lockfile 🤔

[arcanis]

I'm going to remove this one from the 1.0 milestone - it's not a bug strictly speaking, so we will want to think about this more in depth before changing the behavior. I agree it could be clearer.