Skip to content

"npm does not support Node.js v13.0.0" #30066

Closed
Closed
"npm does not support Node.js v13.0.0"#30066
Assignees
ljharb

Description

@mgol
mgol
opened on Oct 22, 2019
  • Version: v13.0.0
  • Platform: Darwin mgolebiowski-mac 18.7.0 Darwin Kernel Version 18.7.0: Tue Aug 20 16:57:14 PDT 2019; root:xnu-4903.271.2~2/RELEASE_X86_64 x86_64 i386 MacBookPro15,1 Darwin
  • Subsystem:

Under Node.js 13.0.0, running many commands using the included npm version (6.12.0) results in the message:

npm WARN npm npm does not support Node.js v13.0.0
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can't make any promises that npm will work with this version.
npm WARN npm Supported releases of Node.js are the latest release of 6, 8, 9, 10, 11, 12.
npm WARN npm You can find the latest version at https://nodejs.org/

I can understand some npm versions not supporting a newly released Node.js version but the version that's bundled with Node shouldn't print such messages.

Activity

  1. mgol commented on Oct 22, 2019

    @mgol
    mgol
    on Oct 22, 2019
    ContributorAuthor

    I installed Node using nvm if that matters:

    nvm install 13

  2. Trott commented on Oct 22, 2019

    @Trott
    Trott
    on Oct 22, 2019
    Member

    Yeah, @ljharb and others are on the case: npm/cli#269

    Once there's an npm release, updating npm will fix it.

    I'm guessing once there's an npm release, we'll see a Node.js 13.0.1 or 13.1.0 pretty quickly to bundle the new npm.

  3. richardlau
    pinned this issue on Oct 22, 2019

  4. Trott commented on Oct 22, 2019

    @Trott
    Trott
    on Oct 22, 2019
    Member

    @nodejs/releasers Might it make sense to float the patch in npm/cli#269 on core and push out a 13.0.1 quickly? I'm guessing that would be a ton of work that no one has the time for today or even this week, but asking anyway in case I'm wrong....

  5. ljharb commented on Oct 22, 2019

    @ljharb
    ljharb
    on Oct 22, 2019
    SponsorMember

    If npm can merge and release that fix ASAP, i can get the node PR up shortly afterwards

  6. ljharb
    self-assigned this
    on Oct 22, 2019

  7. realJustinLee commented on Oct 23, 2019

    @realJustinLee
    realJustinLee
    on Oct 23, 2019

    Same issue encountered. Looking forward to the patch.

  8. akash07k commented on Oct 23, 2019

    @akash07k
    akash07k
    on Oct 23, 2019

    Same here, uninstalled and reinstall node and NPM but no luck. :(

  9. tamhaneaniket commented on Oct 23, 2019

    @tamhaneaniket
    tamhaneaniket
    on Oct 23, 2019

    Having the same issue....Is there a workaround available?

  10. targos commented on Oct 23, 2019

    @targos
    targos
    on Oct 23, 2019
    Member

    The workaround is to ignore the warning. It is not an error and you can still use npm until we release a fix.

  11. MylesBorins
    added 2 commits that reference this issue on Oct 23, 2019

    deps: npm: patch support for 13.x

    d8aa38c

    deps: npm: patch support for 13.x

    2f36976

  12. akash07k commented on Oct 23, 2019

    @akash07k
    akash07k
    on Oct 23, 2019 via email

  13. 25 remaining items

  14. Trott commented on Dec 5, 2019

    @Trott
    Trott
    on Dec 5, 2019
    Member

    FYI

    $ uname -a
Darwin cpf 19.0.0 Darwin Kernel Version 19.0.0: Thu Oct 17 16:17:15 PDT 2019; root:xnu-6153.41.3~29/RELEASE_X86_64 x86_64

$ npm -v
6.13.2

$ node -v
v13.2.0

    getting warning in this setup

    There are lots of warnings you could be getting, but you are all-but-certainly not getting the warning reported in this issue if you are really running npm 6.13.2. This bug was fixed in 6.12.1. If you are seeing this, then you are running npm 6.12.0 or earlier.

  15. cuipengfei commented on Dec 5, 2019

    @cuipengfei
    cuipengfei
    on Dec 5, 2019

    FYI

    $ uname -a
Darwin cpf 19.0.0 Darwin Kernel Version 19.0.0: Thu Oct 17 16:17:15 PDT 2019; root:xnu-6153.41.3~29/RELEASE_X86_64 x86_64

$ npm -v
6.13.2

$ node -v
v13.2.0

    getting warning in this setup

    There are lots of warnings you could be getting, but you are all-but-certainly not getting the warning reported in this issue if you are really running npm 6.13.2. This bug was fixed in 6.12.1. If you are seeing this, then you are running npm 6.12.0 or earlier.

    Just tried this, when installing something, getting warning saying that "npm does not support Node.js v13.2.0"

    # pfcui @ cpf in ~ [15:34:21]
$ node -v
v13.2.0

# pfcui @ cpf in ~ [15:43:05]
$ npm -v
6.13.2

# pfcui @ cpf in ~ [15:43:07]
$ npm install -g expo-cli
npm WARN npm npm does not support Node.js v13.2.0
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can't make any promises that npm will work with this version.
npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9.
npm WARN npm You can find the latest version at https://nodejs.org/

  16. ljharb commented on Dec 5, 2019

    @ljharb
    ljharb
    on Dec 5, 2019
    SponsorMember

    what does which node and which npm say?

  17. cuipengfei commented on Dec 5, 2019

    @cuipengfei
    cuipengfei
    on Dec 5, 2019

    what does which node and which npm say?

    /usr/local/bin/node
    /usr/local/bin/npm

  18. Trott commented on Dec 5, 2019

    @Trott
    Trott
    on Dec 5, 2019
    Member

    The fact that it says that 9 is the highest supported version--not mentioning 10 or 12, much less 13--indicates that it is a very old version of npm. Whatever is going on here, it's something weird. I mean, like someone bumped the version of npm only but not the actual code otherwise and compiled it and installed it. Or you're running an otherwise weirdly-hacked npm. I mean, I'm not saying that's it. I'm just saying, something weird is going on.

    What's the output of these commands?:

    whereis npm
ls -l `which npm`
sum `which npm`

  19. Trott commented on Dec 5, 2019

    @Trott
    Trott
    on Dec 5, 2019
    Member

    Oh! Maybe somehow npm is using a different node than your command line. What does this say?

    /usr/bin/env node -v

  20. Trott commented on Dec 5, 2019

    @Trott
    Trott
    on Dec 5, 2019
    Member

    And while we're at it, let's just be complete-ish:

    whereis node
ls -l `which node`
sum `which node`

    How did you install Node.js? With the default installer? Or a version manager? Or what?

  21. cuipengfei commented on Dec 6, 2019

    @cuipengfei
    cuipengfei
    on Dec 6, 2019

    And while we're at it, let's just be complete-ish:

    whereis node
ls -l `which node`
sum `which node`

    How did you install Node.js? With the default installer? Or a version manager? Or what?

    It was installed via brew.

    I have done brew uninstall and reinstalled the LTS version, which have damaged the crime scene, however it seems to be fine now. No warnings anymore.

  22. FJBDev commented on Dec 27, 2019

    @FJBDev
    FJBDev
    on Dec 27, 2019

    Encountered this issue today when I tried to install the latest version 13.5.0

    npm WARN npm npm does not support Node.js v13.5.0

    After several hours of searching and testing/rebooting/uninstalling..etc This is what fixed it to me

  23. jufemaiz commented on Dec 29, 2019

    @jufemaiz
    jufemaiz
    on Dec 29, 2019

    @FJBDev i'm seeing the same on a node:13-alpine image.

  24. amerikan commented on Jan 3, 2020

    @amerikan
    amerikan
    on Jan 3, 2020 · Hidden as resolved

  25. ljharb commented on Jan 3, 2020

    @ljharb
    ljharb
    on Jan 3, 2020
    SponsorMember

    node 13.5 comes with npm 6.13.4, so there's something wrong with your node installation there.

  26. eyalk5 commented on Jan 30, 2020

    @eyalk5
    eyalk5
    on Jan 30, 2020

    I get : npm does not support Node.js v13.6.0

  27. Trott commented on Jan 30, 2020

    @Trott
    Trott
    on Jan 30, 2020
    Member

    I get : npm does not support Node.js v13.6.0

    Then you're running a version of npm that didn't ship with the 13.6.0 binary.

  28. Trott commented on Jan 30, 2020

    @Trott
    Trott
    on Jan 30, 2020
    Member

    I get : npm does not support Node.js v13.6.0

    Then you're running a version of npm that didn't ship with the 13.6.0 binary.

    Might be fixed if you run npm install -g npm but probably better to figure out why a different npm got in your path.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions