NPM install fails: No compatible version found: unzip-response@^1.0.2

[tiaantiaan]

It seems that the latest version of got requires unzip-response@^1.0.2. The latest 1.* version of unzip-response on npm is however, 1.0.1.

[floatdrop]

I see 1.0.2 in npm show unzip-response:

❯ npm show unzip-response
{ name: 'unzip-response',
  description: 'Unzip a HTTP response if needed',
  'dist-tags':
   { latest: '2.0.1',
     '1.x-branch': '1.0.2' },
  versions:
   [ '1.0.0',
     '1.0.1',
     '1.0.2',
     '2.0.0',
     '2.0.1' ],
  maintainers:
   [ 'sindresorhus <sindresorhus@gmail.com>',
     'floatdrop <floatdrop@gmail.com>' ],
  time:
   { modified: '2016-11-01T08:28:04.401Z',
     created: '2015-07-18T16:32:28.789Z',
     '1.0.0': '2015-07-18T16:32:28.789Z',
     '1.0.1': '2016-09-06T13:46:49.405Z',
     '2.0.0': '2016-09-06T13:55:25.954Z',
     '2.0.1': '2016-09-06T18:43:08.276Z',
     '1.0.2': '2016-11-01T08:28:04.401Z' },
  homepage: 'https://github.com/sindresorhus/unzip-response#readme',
  keywords:
   [ 'http',
     'unzip',
     'zlib',
     'gzip',
     'deflate',
     'incoming',
     'message',
     'response',
     'stream' ],
  repository:
   { type: 'git',
     url: 'git+https://github.com/sindresorhus/unzip-response.git' },
  bugs: { url: 'https://github.com/sindresorhus/unzip-response/issues' },
  license: 'MIT',
  readmeFilename: 'readme.md',
  version: '2.0.1',
  engines: { node: '>=4' },
  scripts: { test: 'xo && ava' },
  files: 'index.js',
  devDependencies:
   { ava: '*',
     'get-stream': '^2.3.0',
     pify: '^2.3.0',
     rfpify: '^1.0.0',
     xo: '*' },
  xo: { esnext: true },
  gitHead: '71858052fe94b89678d14ba54e8e96cacbda92c3',
  dist:
   { shasum: 'd2f0f737d16b0615e72a6935ed04214572d56f97',
     tarball: 'https://registry.npmjs.org/unzip-response/-/unzip-response-2.0.1.tgz' },
  directories: {} }

Which version of got you are using? Maybe you are using caching proxy or private registry?

[tiaantiaan]

Ah, it is working now. I am using version 5.7.0. It was a problem on my side. It seems that my local repository cache took a while to update to the new version that was only published 2 hours ago.

Thanks for your trouble, and the great work!