Navigation Menu

Skip to content
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.

Node.js 8 + npm 5 install winston-mail@~0.5.0: No matching version found for moment@= 1.7.0 #17360

Closed
1 of 13 tasks
harishanchu opened this issue Jun 21, 2017 · 1 comment
Closed
1 of 13 tasks

Comments

@harishanchu
Copy link

I'm opening this issue because:

  • npm is crashing.
  • npm is producing an incorrect install.
  • npm is doing something I don't understand.
  • Other (see below for feature requests):

What's going wrong?

winston-mail version ~0.5.0 is not installed after the update of npm (to version 5).

How can the CLI team reproduce the problem?

npm install winston-mail@~0.5.0

I get an error

npm WARN deprecated mimelib@0.2.14: This module is deprecated
npm ERR! code ETARGET
npm ERR! notarget No matching version found for moment@= 1.7.0
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget 
npm ERR! notarget It was specified as a dependency of 'emailjs'
npm ERR! notarget 

npm ERR! A complete log of this run can be found in:

supporting information:

  • npm -v prints: 5.0.3
  • node -v prints: v8.0.0
  • npm config get registry prints: https://registry.npmjs.org/
  • Windows, OS X/macOS, or Linux?: Linux
  • Network issues:
    • Geographic location where npm was run:
    • I use a proxy to connect to the npm registry.
    • I use a proxy to connect to the web.
    • I use a proxy when downloading Git repos.
    • I access the npm registry via a VPN
    • I don't use a proxy, but have limited or unreliable internet access.
  • Container:
    • I develop using Vagrant on Windows.
    • I develop using Vagrant on OS X or Linux.
    • I develop / deploy using Docker.
    • I deploy to a PaaS (Triton, Heroku).
@kenany kenany added the npm5 label Jun 21, 2017
zkat added a commit that referenced this issue Jun 29, 2017
Fixes: #17360
Credit: @zkat
@zkat
Copy link
Contributor

zkat commented Jun 29, 2017

This is fixed by 8b4bb19, which will go out with the next npm@5 release.

@zkat zkat closed this as completed Jun 29, 2017
@zkat zkat added the bug label Jun 29, 2017
zkat added a commit that referenced this issue Jul 5, 2017
Fixes: #17360
Credit: @zkat
zkat added a commit that referenced this issue Jul 5, 2017
Fixes: #17360
Credit: @zkat
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants