Yarn: Yarn install Error

[luanmuniz]

Arguments: 
/Users/luanmuniz/.nvm/versions/node/v6.9.0/bin/node /usr/local/bin/yarn install --production

PATH: 
/Users/luanmuniz/.nvm/versions/node/v6.9.0/bin:/usr/local/bin:/usr/local/heroku/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/MacGPG2/bin

Yarn version: 0.16.0
Node version: 6.9.0
Platform: darwin x64

npm manifest: 
  {
    "name": "api",
    "version": "0.0.1",
    "private": true,
    "bugs": "###",
    "scripts": {
      "start": "node index.js",
      "nodemon": "nodemon index.js",
      "postinstall": "cp ../lib ./lib",
      "test": "./node_modules/grunt-cli/bin/grunt -v test"
    },
    "engines": {
      "node": ">=4.*"
    },
    "dependencies": {
      "body-parser": "^1.10.2",
      "compression": "^1.3.0",
      "csurf": "^1.6.5",
      "deep-extend": "^0.4.1",
      "express": "^4.11.1",
      "express-params": "0.0.3",
      "helmet": "^0.15.0",
      "joi": "^9.0.4",
      "lodash": "^3.6.0",
      "marked": "^0.3.3",
      "method-override": "^2.3.1",
      "moment": "^2.15.0",
      "mysql": "^2.5.4",
      "newrelic": "^1.30.3",
      "universal-event-tracker": "^2.1.8",
      "uuid": "^2.0.1"
    },
    "devDependencies": {
      "grunt": "^0.4.5",
      "grunt-cli": "^0.1.13",
      "grunt-contrib-jshint": "^0.11.0",
      "grunt-david": "^0.4.0",
      "grunt-env": "^0.4.4",
      "grunt-execute": "^0.2.2",
      "grunt-jscs": "^2.3.0",
      "grunt-mocha-test": "^0.12.7",
      "load-grunt-tasks": "^3.1.0",
      "mocha": "^2.2.4",
      "should": "^7.0.1",
      "sinon": "^1.14.1",
      "supertest": "^1.0.1",
      "time-grunt": "^1.0.0"
    }
  }

yarn manifest: 
  No manifest

bower manifest: 
  No manifest

Lockfile: 
  No lockfile

Trace: 
  TypeError: Cannot use 'in' operator to search for '1.3.0' in undefined
      at /usr/local/Cellar/yarn/0.16.0/libexec/lib/node_modules/yarn/lib/resolvers/registries/npm-resolver.js:62:24
      at next (native)
      at step (/usr/local/Cellar/yarn/0.16.0/libexec/lib/node_modules/yarn/node_modules/babel-runtime/helpers/asyncToGenerator.js:17:30)
      at /usr/local/Cellar/yarn/0.16.0/libexec/lib/node_modules/yarn/node_modules/babel-runtime/helpers/asyncToGenerator.js:35:14
      at Promise.F (/usr/local/Cellar/yarn/0.16.0/libexec/lib/node_modules/yarn/node_modules/core-js/library/modules/_export.js:35:28)
      at /usr/local/Cellar/yarn/0.16.0/libexec/lib/node_modules/yarn/node_modules/babel-runtime/helpers/asyncToGenerator.js:14:12
      at Function.findVersionInRegistryResponse (/usr/local/Cellar/yarn/0.16.0/libexec/lib/node_modules/yarn/lib/resolvers/registries/npm-resolver.js:72:7)
      at /usr/local/Cellar/yarn/0.16.0/libexec/lib/node_modules/yarn/lib/resolvers/registries/npm-resolver.js:89:34
      at next (native)
      at step (/usr/local/Cellar/yarn/0.16.0/libexec/lib/node_modules/yarn/node_modules/babel-runtime/helpers/asyncToGenerator.js:17:30)

[wyze]

Possibly fixed by #1281. There are other issues in the PR that are all similar.

[parro-it]

@wize I'm getting the same error, but your PR didn't solve it. Apparently there are some problem with Cloudfare dns, I receive this error message as content of body var here

Please enable cookies.
Error 1001 Ray ID: 2f5631442ced435e • 2016-10-21 16:47:37 UTC

DNS resolution error

What happened?

You've requested a page on a website (registry.yarnpkg.com) that is on the CloudFlare network. CloudFlare is currently unable to resolve your requested domain (registry.yarnpkg.com). There are two potential causes of this:

Most likely: if the owner just signed up for CloudFlare it can take a few minutes for the website's information to be distributed to our global network.
Less likely: something is wrong with this site's configuration. Usually this happens when accounts have been signed up with a partner organization (e.g., a hosting provider) and the provider's DNS fails.
CloudFlare Ray ID: 2f5631442ced435e • Your IP: <MY IP> • Performance & security by CloudFlare

[tgvarik]

Also seeing the CloudFlare DNS resolution error on registry.yarnpkg.com.

[bramblex]

I got the same error

[parro-it]

Seems to be due to a general dns outage http://appleinsider.com/articles/16/10/21/us-internet-users-suffering-under-ddos-attacks-on-key-dns-provider

[jamiebuilds]

Yeah, Dyn has been getting DDoS'd all day:

• http://status.npmjs.org/
• https://status.github.com/

[jamiebuilds]

registry.yarnpkg.com is now bypassing npm's DNS by pointing directly to it's IP address so there should not be anymore problems.

[jascodes]

@thejameskyle All of sudden yarn stoped working

can't connect to 104.16.59.173 (cloudflare seems to block it)
I am from india and using internet connection reliance jio(4g); my bsnl broadband is down today(never had problem). This is not first time I had issue using yarn with my 4g connection.

Thx

[jascodes]

@thejameskyle
Error: connect ECONNREFUSED 104.16.59.173:443 at Object.exports._errnoException (util.js:1026:11) at exports._exceptionWithHostPort (util.js:1049:20) at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1085:14)

[SuhairZain]

@jas99
Same issue here. I have the same issue with another service provider (Airtel). Were you able to find a solution for this?

[jascodes]

@SuhairZain I kinna started working for me again after a while.