Yarn seams to be using a different version of NPM

[ssylvia]

Do you want to request a feature or report a bug?
Bug

What is the current behavior?
When running a script with yarn I get the following warning:

npm WARN npm npm does not support Node.js v10.13.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/
npm WARN lifecycle The node binary used for scripts is /var/folders/6_/ggyf3s1j6772klpkpzhmg_08s9xzsr/T/yarn--1541072250935-0.34762921316103146/node but npm is using /Users/{username}/.nvm/versions/node/v10.13.0/bin/node itself. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.

Please mention your node.js, yarn and operating system version.

which yarn

/usr/local/bin/yarn
Installed with homebrew

which node

/Users/{username}/.nvm/versions/node/v10.13.0/bin/node
Installed with nvm

which npm

/Users/step6692/.nvm/versions/node/v10.13.0/bin/npm

yarn --version

1.12.1

node --version

v10.13.0

npm --version

6.4.1

On MacOS Mojave 10.14 (18A391)

[arcanis]

Yarn has specific mechanisms to force the scripts it runs to use the exact same Node binary as the one used to run Yarn itself. It seems like npm conflicts with this because they do the opposite.

[kondei]

I have the same problem.

[kondei]

How can I fix it?
I can run nothing now.

[kondei]

npm config set scripts-prepend-node-path true

seems to "fix" it...

[wKich]

@arcanis can you explain why?

I switch node by using n cli. So binary in temp dir and global installation directory has same version. But I always receive this warning.

And more over yarn create new trash dir with node exec every time I call yarn

[smac89]

@kondei Another option is to include a .npmrc in the folder with that option in it.

See this SO answer: https://stackoverflow.com/a/51295237/2089675

[kondei]

@smac89 I have already done so.
thank you. 👍

[BYK]

Closing as this is by design and there doesn't seem to be anything on our side to change or fix.

[dmost714]

I just encountered this issue on an "out of the box" clean setup.
I installed MacOS Catalina (10.15.7) on a Macbook Pro.
Installed Homebrew via their suggested terminal blurb.
Installed Yarn (brew install yarn)
Attempted to build my Gatsby project, and received this error.
I typed "npm upgrade", and the error is gone.
Hope that works for someone else as well.

[craigphicks]

It appears that the warning message can appear (and it does for me) even when yarn is calling the correct node
version. This can happen because yarn may call the correct node version through a shell script as follows -

$ cat /tmp/yarn--1635268434808-0.4758243621447591/node
#!/bin/sh

exec "/usr/local/bin/node" "$@"
$ which node
/usr/local/bin/node

In that case the debugger won't be loading two separate versions of node, so no problem, and the warning can be safely ignored.