`yarn outdated` fails when scoped packages are present in package.json #620

Jessidhia · 2016-10-11T16:06:44Z

Can be reproduced with:

mkdir folder
cd folder
yes '' | yarn init # all defaults, doesn't matter
yarn add @types/react # or any other scoped package
yarn outdated

yarn outdated v0.15.1
error https://registry.yarnpkg.com/@types/react: Not found
    at Request.params.callback [as _callback] (/Users/kovensky/.nodenv/versions/6.7.0/lib/node_modules/yarnpkg/lib/util/request-manager.js:273:18)
    at Request.self.callback (/Users/kovensky/.nodenv/versions/6.7.0/lib/node_modules/yarnpkg/node_modules/request/request.js:187:22)
    at emitTwo (events.js:106:13)
    at Request.emit (events.js:191:7)
    at Request.<anonymous> (/Users/kovensky/.nodenv/versions/6.7.0/lib/node_modules/yarnpkg/node_modules/request/request.js:1048:10)
    at emitOne (events.js:96:13)
    at Request.emit (events.js:188:7)
    at IncomingMessage.<anonymous> (/Users/kovensky/.nodenv/versions/6.7.0/lib/node_modules/yarnpkg/node_modules/request/request.js:969:12)
    at emitNone (events.js:91:20)
    at IncomingMessage.emit (events.js:185:7)
info Visit http://yarnpkg.com/en/docs/cli/outdated for documentation about this command.

The text was updated successfully, but these errors were encountered:

rickhanlonii · 2016-10-12T16:56:20Z

Workaround for now is to remove any scoped packages from package.json and re-run

djforth · 2016-10-13T21:17:21Z

+1 getting same issue

jeffcarbs · 2016-10-18T16:56:39Z

FYI: Just installed yarn v0.16.0 which adds support for private/scoped NPM packages and this bug still exists.

Trace: 
  Error: https://registry.yarnpkg.com/@kadira/storybook: Not found
      at Request.params.callback [as _callback] (~/.nvm/versions/node/v6.6.0/lib/node_modules/yarn/lib/util/request-manager.js:294:18)
      at Request.self.callback (~/.nvm/versions/node/v6.6.0/lib/node_modules/yarn/node_modules/request/request.js:187:22)
      at emitTwo (events.js:106:13)
      at Request.emit (events.js:191:7)
      at Request.<anonymous> (~/.nvm/versions/node/v6.6.0/lib/node_modules/yarn/node_modules/request/request.js:1048:10)
      at emitOne (events.js:96:13)
      at Request.emit (events.js:188:7)
      at IncomingMessage.<anonymous> (~/.nvm/versions/node/v6.6.0/lib/node_modules/yarn/node_modules/request/request.js:969:12)
      at emitNone (events.js:91:20)
      at IncomingMessage.emit (events.js:185:7)

jsynowiec · 2016-10-18T21:13:42Z

~~#1071~~ #1276 was not yet merged. The outdated command fails, because yarn is trying to query the registry for @types/<typdef> and the NPM registry returns 404 due to the / character in a scoped package name that needs to be escaped, eg. https://registry.npmjs.org/@types%2Fnode

jtsom · 2016-10-19T12:56:37Z

FYI.. looks like it's happening (on windows) when doing an yarn install also:

Trace: 
  Error: ENOENT: no such file or directory, open 'C:\Code\ng2testing\node_modules\@types\jasmine\index.d.ts'
      at Error (native)

Package name was not escaped when querying NPM registry.

samccone · 2016-10-26T04:37:05Z

This is fixed on master 👐

geovanisouza92 · 2016-10-26T09:47:22Z

Just to know, when the next release containing this fix is planned?

rparree · 2016-11-25T05:38:04Z

I am still seeing this problem

For example with the angular quickstarts:

$ git clone https://github.com/angular/quickstart.git quickstart && cd quickstart
…
$ yarn install
yarn install v0.17.8
info No lockfile found.
[1/4] Resolving packages...
error Couldn't find package "@types/node" on the "npm" registry.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

I assume the "next release" mentioned in previous post (from Oct 26) has been released. Perhaps it is a regression?

My versions:

$ yarn versions
yarn versions v0.17.8
{ yarn: '0.17.8',
  'angular-quickstart': '1.0.0',
  http_parser: '2.7.0',
  node: '6.9.1',
  v8: '5.1.281.84',
  uv: '1.9.1',
  zlib: '1.2.8',
  ares: '1.10.1-DEV',
  icu: '57.1',
  modules: '48',
  openssl: '1.0.2j' }
Done in 0.06s.

I am on Fedora/25.

jsynowiec · 2016-11-25T05:57:39Z

@rparree thanks for posting. Try cleaning your caches or reinstall yarn first. I can't reproduce.

$ yarn        
yarn install v0.17.8
info No lockfile found.
[1/4] 🔍  Resolving packages...
warning lite-server > browser-sync > localtunnel > request > tough-cookie@2.2.2: ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130
warning lite-server > browser-sync > localtunnel > request > node-uuid@1.4.7: use uuid module instead
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
[4/4] 📃  Building fresh packages...
success Saved lockfile.
✨  Done in 31.27s.
$ yarn --version
0.17.8

rparree · 2016-11-25T06:03:06Z

I tried after cleaning my cache (again), it still doesn't work

rparree at hprp in ~/tmp/quickstart on master
$ yarn cache clean
yarn cache v0.17.8
success Cleared cache.
Done in 41.74s.
rparree at hprp in ~/tmp/quickstart on master
$ yarn 
yarn install v0.17.8
info No lockfile found.
[1/4] Resolving packages...
error Couldn't find package "@types/selenium-webdriver" on the "npm" registry.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

I am using nvm might that cause a problem?

jsynowiec · 2016-11-25T06:27:36Z

Are you using some kind of npm proxy or private registry?

rparree · 2016-11-25T06:33:48Z

no proxy and no private registry. Where could i place some logging to see what he request/response us?

tx.,

jsynowiec · 2016-11-25T06:37:16Z

Try this https://twitter.com/jasonlaster11/status/798926995405021185 if you want to check the installed version or clone yarn repository, build and attach a debugger.

rparree · 2016-11-25T07:13:38Z

I'be used betwixt:

Request URL:https://registry.yarnpkg.com/@angular%2fcommon
Request Method:GET
Status Code:401 Unauthorized
Remote Address:104.16.63.173:443

The same request with curl

$ curl -I https://registry.yarnpkg.com/@angular%2fcommon
HTTP/2 200 
date: Fri, 25 Nov 2016 07:06:04 GMT
content-type: application/json
..

I did notice in the request header from yarn there is a authorization header (just obfuscated it below as i don't know what password is being used, seems like a generated one for my username)

accept:application/json
accept-encoding:gzip, deflate
authorization:Basic *****************
connection:close
host:registry.yarnpkg.com
user-agent:yarn/0.17.8 npm/? node/v6.9.1 linux x64

When i tried that with curl:

$ curl -I 'https://registry.yarnpkg.com/@angular%2fcommon' -H 'accept: application/json' -H 'accept-encoding: gzip, deflate' -H 'authorization: Basic ****************' -H 'connection: close' -H 'user-agent: yarn/0.17.8 npm/? node/v6.9.1 linux x64' --compressed
HTTP/2 401 
...

There is no authorisation header on the packages that are not scoped.

jsynowiec · 2016-11-25T07:56:05Z

This might be a problem with yarn registry. Try setting yarn to use the npm registry directly
yarn config set registry https://registry.npmjs.org

rparree · 2016-11-25T08:06:09Z

Same problem :(

Why does it only add an authorisation header when the package is scoped?

I noticed that a test fails as well which uses a scoped module:

 FAIL  __tests__/commands/outdated.js
  ● hides when current > latest (next, beta tag)

    Error: couldnt find @wyze/yarn-outdated-next
      
      at src/registries/npm-registry.js:84:15:84:15�[2m

rparree · 2016-11-25T08:19:44Z

This resolves to true:

this.getScopedOption(registry.replace(/^https?:/, ''), 'always-auth') || this.getOption('always-auth')
      || removePrefix(requestUrl, registry)[0] === '@';

(EDIT: added the whole boolean expression, as my problem is in the last expression)

yarn/src/registries/npm-registry.js

Line 56 in b4e42e3

    
           const alwaysAuth = this.getScopedOption(registry.replace(/^https?:/, ''), 'always-auth')

jsynowiec · 2016-11-25T08:24:00Z

This should be moved to a separate issue.

rparree · 2016-11-25T08:35:01Z

see #2030

sebmck added cat-bug cat-compatibility labels Oct 11, 2016

This was referenced Oct 11, 2016

outdated - package: @google-cloud not found #709

Closed

Bug with @types/package dependencies #651

Closed

eugene1g mentioned this issue Oct 11, 2016

yarn compatibility storybookjs/storybook#542

Closed

truckingsim mentioned this issue Oct 13, 2016

yarn outdated can't find @types/* packages #983

Closed

dylanparry mentioned this issue Oct 14, 2016

Fix 'yarn outdated' for scoped packages (See #620 / #983) #1071

Closed

wyze mentioned this issue Oct 16, 2016

'yarn outdated' doesn't look for registry.npmjs.org #1126

Closed

hawkrives mentioned this issue Oct 18, 2016

[BUG] Support TypeScript 2.0's @types/* repo #1181

Closed

geovanisouza92 mentioned this issue Oct 18, 2016

Investigate possible use of yarn instead npm, when present cyclejs-community/create-cycle-app#11

Closed

jsynowiec mentioned this issue Oct 19, 2016

"Yarn outdated" errors with @exponent/ex-navigation #1234

Closed

hawkrives mentioned this issue Oct 19, 2016

Yarn install fails, private modules? #1266

Closed

This was referenced Oct 19, 2016

Fix yarn outdated for scoped packages (#620) #1276

Merged

yarn outdated fails and advises to report a bug #1309

Closed

sebmck pushed a commit that referenced this issue Oct 25, 2016

Fix yarn outdated for scoped packages (#620) (#1276)

3a25859

Package name was not escaped when querying NPM registry.

samccone closed this as completed Oct 26, 2016

wyze mentioned this issue Oct 26, 2016

yarn outdated fails with @types/core-js package #1475

Closed

dylanparry mentioned this issue Oct 28, 2016

yarn outdated - crashes due to 404 for @angular/http package #1535

Closed

wyze mentioned this issue Nov 3, 2016

yarn outdated crashes with @typopro/web-montserrat #1655

Closed

ikhilko mentioned this issue Nov 13, 2016

An unexpected error occured while using "Scoped packages" #1797

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

`yarn outdated` fails when scoped packages are present in package.json #620

`yarn outdated` fails when scoped packages are present in package.json #620

Jessidhia commented Oct 11, 2016 •

edited

Loading

rickhanlonii commented Oct 12, 2016

djforth commented Oct 13, 2016

jeffcarbs commented Oct 18, 2016 •

edited

Loading

jsynowiec commented Oct 18, 2016 •

edited

Loading

jtsom commented Oct 19, 2016

samccone commented Oct 26, 2016

geovanisouza92 commented Oct 26, 2016

rparree commented Nov 25, 2016

jsynowiec commented Nov 25, 2016

rparree commented Nov 25, 2016

jsynowiec commented Nov 25, 2016 •

edited

Loading

rparree commented Nov 25, 2016

jsynowiec commented Nov 25, 2016

rparree commented Nov 25, 2016 •

edited

Loading

jsynowiec commented Nov 25, 2016 •

edited

Loading

rparree commented Nov 25, 2016

rparree commented Nov 25, 2016 •

edited

Loading

jsynowiec commented Nov 25, 2016

rparree commented Nov 25, 2016

yarn outdated fails when scoped packages are present in package.json #620

yarn outdated fails when scoped packages are present in package.json #620

Comments

Jessidhia commented Oct 11, 2016 • edited Loading

rickhanlonii commented Oct 12, 2016

djforth commented Oct 13, 2016

jeffcarbs commented Oct 18, 2016 • edited Loading

jsynowiec commented Oct 18, 2016 • edited Loading

jtsom commented Oct 19, 2016

samccone commented Oct 26, 2016

geovanisouza92 commented Oct 26, 2016

rparree commented Nov 25, 2016

jsynowiec commented Nov 25, 2016

rparree commented Nov 25, 2016

jsynowiec commented Nov 25, 2016 • edited Loading

rparree commented Nov 25, 2016

jsynowiec commented Nov 25, 2016

rparree commented Nov 25, 2016 • edited Loading

jsynowiec commented Nov 25, 2016 • edited Loading

rparree commented Nov 25, 2016

rparree commented Nov 25, 2016 • edited Loading

jsynowiec commented Nov 25, 2016

rparree commented Nov 25, 2016

`yarn outdated` fails when scoped packages are present in package.json #620

`yarn outdated` fails when scoped packages are present in package.json #620

Jessidhia commented Oct 11, 2016 •

edited

Loading

jeffcarbs commented Oct 18, 2016 •

edited

Loading

jsynowiec commented Oct 18, 2016 •

edited

Loading

jsynowiec commented Nov 25, 2016 •

edited

Loading

rparree commented Nov 25, 2016 •

edited

Loading

jsynowiec commented Nov 25, 2016 •

edited

Loading

rparree commented Nov 25, 2016 •

edited

Loading