Node.js – How to update “yarn” to the latest version, 1.13.0

node.jsnpmyarnpkg

I tried "npm update yarn -g" and "npm intall yarn -g", but the yarn verison is still 1.12.3.

I run the command in a empty folder, please see below. Thank you.

Microsoft Windows [Version 10.0.17134.320]
(c) 2018 Microsoft Corporation. All rights reserved.

D:\test>dir
 Volume in drive D is D
 Volume Serial Number is 18E2-7E00

 Directory of D:\test

01/16/2019  10:38 PM    <DIR>          .
01/16/2019  10:38 PM    <DIR>          ..
               0 File(s)              0 bytes
               2 Dir(s)  467,370,369,024 bytes free

D:\test>npm update yarn -g

D:\test>yarn -v
1.12.3

D:\test>npm install yarn -g
C:\Users\myuser\AppData\Roaming\npm\yarn -> C:\Users\myuser\AppData\Roaming\npm\node_modules\yarn\bin\yarn.js
C:\Users\myuser\AppData\Roaming\npm\yarnpkg -> C:\Users\myuser\AppData\Roaming\npm\node_modules\yarn\bin\yarn.js
+ yarn@1.13.0
updated 1 package in 0.469s

D:\test>yarn -v
1.12.3

D:\test>npm -v
6.4.1

D:\test>

Best Answer

There is a known bug on npm update yarn -g here is the related GitHub issue so you should use this instead:

npm install -g yarn

Alternatively, you can install brew first than update trough brew like this:

brew upgrade yarn

If you're using Windows you can find a brew alternative, such as choco, and update with like this:

choco upgrade yarn

Related Solutions

Javascript – the purpose of Node.js module.exports and how do you use it

module.exports is the object that's actually returned as the result of a require call.

The exports variable is initially set to that same object (i.e. it's a shorthand "alias"), so in the module code you would usually write something like this:

let myFunc1 = function() { ... };
let myFunc2 = function() { ... };
exports.myFunc1 = myFunc1;
exports.myFunc2 = myFunc2;

to export (or "expose") the internally scoped functions myFunc1 and myFunc2.

And in the calling code you would use:

const m = require('./mymodule');
m.myFunc1();

where the last line shows how the result of require is (usually) just a plain object whose properties may be accessed.

NB: if you overwrite exports then it will no longer refer to module.exports. So if you wish to assign a new object (or a function reference) to exports then you should also assign that new object to module.exports

It's worth noting that the name added to the exports object does not have to be the same as the module's internally scoped name for the value that you're adding, so you could have:

let myVeryLongInternalName = function() { ... };
exports.shortName = myVeryLongInternalName;
// add other objects, functions, as required

followed by:

const m = require('./mymodule');
m.shortName(); // invokes module.myVeryLongInternalName

Node.js – How to update NodeJS and NPM to the next versions

See the docs for the update command:

npm update [-g] [<pkg>...]

This command will update all the packages listed to the latest version (specified by the tag config), respecting semver.

Additionally, see the documentation on Node.js and NPM installation and Upgrading NPM.

The following original answer is from the old FAQ that no longer exists, but should work for Linux and Mac:

How do I update npm?
npm install -g npm
Please note that this command will remove your current version of npm. Make sure to use sudo npm install -g npm if on a Mac.

You can also update all outdated local packages by doing npm update without any arguments, or global packages by doing npm update -g.

Occasionally, the version of npm will progress such that the current version cannot be properly installed with the version that you have installed already. (Consider, if there is ever a bug in the update command.) In those cases, you can do this:
curl https://www.npmjs.com/install.sh | sh

To update Node.js itself, I recommend you use nvm, the Node Version Manager.

Best Answer

Related Solutions

Javascript – the purpose of Node.js module.exports and how do you use it

Node.js – How to update NodeJS and NPM to the next versions

How do I update npm?

Related Topic