New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

yarn self-update should update using the same installation method originally used #1139

Open
Daniel15 opened this Issue Oct 17, 2016 · 48 comments

Comments

Projects
None yet
@Daniel15
Member

Daniel15 commented Oct 17, 2016

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

What is the current behavior?
yarn self-update always downloads a tarball.

What is the expected behavior?
yarn self-update should update using the same installation method used by the user. For example, if Yarn was installed via the Debian/Ubuntu package, yarn self-update should run sudo apt-get update && sudo apt-get install yarn. On Windows when installed via the installer, it should download https://yarnpkg.com/latest.msi and execute it.

This is closely related to #1138 ("add yarn version check on startup") in that both issues need some way of determining the installation method used by the user.

Daniel15 added a commit to Daniel15/yarn that referenced this issue Oct 30, 2016

Daniel15 added a commit to Daniel15/yarn that referenced this issue Oct 30, 2016

kittens added a commit that referenced this issue Nov 1, 2016

Add installationMethod property to package.json (#1557)
* Add installationMethod property to package.json

References #1139, #942, #1429, #1138

* Make set-installation-method.js executable
@busches

This comment has been minimized.

Show comment
Hide comment
@busches

busches Dec 6, 2016

Contributor

Do you want to close this since self-update was removed with #1429?

Contributor

busches commented Dec 6, 2016

Do you want to close this since self-update was removed with #1429?

@Daniel15

This comment has been minimized.

Show comment
Hide comment
@Daniel15

Daniel15 Dec 6, 2016

Member
Member

Daniel15 commented Dec 6, 2016

@jakearchibald

This comment has been minimized.

Show comment
Hide comment

https://yarnpkg.com/en/docs/cli/self-update should probably be removed/updated

@meta-meta

This comment has been minimized.

Show comment
Hide comment
@meta-meta

meta-meta Dec 21, 2016

If I'm on 0.18.1, how do I update to the next version?

If I'm on 0.18.1, how do I update to the next version?

@Daniel15

This comment has been minimized.

Show comment
Hide comment
@Daniel15

Daniel15 Dec 21, 2016

Member

@meta-meta Currently, you need to manually upgrade.

Member

Daniel15 commented Dec 21, 2016

@meta-meta Currently, you need to manually upgrade.

@octopitus

This comment has been minimized.

Show comment
Hide comment
@octopitus

octopitus Jan 17, 2017

how about yarn global add yarn?

how about yarn global add yarn?

@dancoates

This comment has been minimized.

Show comment
Hide comment
@dancoates

dancoates Jan 18, 2017

I'm a big fan of Yarn but am a little concerned at how self-update was removed with no deprecation notice, no mention in the release notes, and that it was bundled in with a PR that is largely unrelated and where there was no discussion about removing self-update.

I understand that it is early days for Yarn and that API changes are to be expected but it would be good if there was a process for removing core functionality.

(sorry if this isn't the right place to discuss, but this PR is where the docs link to)

I'm a big fan of Yarn but am a little concerned at how self-update was removed with no deprecation notice, no mention in the release notes, and that it was bundled in with a PR that is largely unrelated and where there was no discussion about removing self-update.

I understand that it is early days for Yarn and that API changes are to be expected but it would be good if there was a process for removing core functionality.

(sorry if this isn't the right place to discuss, but this PR is where the docs link to)

@Daniel15

This comment has been minimized.

Show comment
Hide comment
@Daniel15

Daniel15 Jan 18, 2017

Member

how about yarn global add yarn?

Installing Yarn via Yarn is not a supported use case at the moment, and can cause several issues. We don't recommend it at the moment.

@dancoates - The self-update command never really worked 100% correctly, that PR just removed the remnants of the existing command while adding some framework stuff for the new self-update (which will come in the future, as per this issue)

Member

Daniel15 commented Jan 18, 2017

how about yarn global add yarn?

Installing Yarn via Yarn is not a supported use case at the moment, and can cause several issues. We don't recommend it at the moment.

@dancoates - The self-update command never really worked 100% correctly, that PR just removed the remnants of the existing command while adding some framework stuff for the new self-update (which will come in the future, as per this issue)

@CatinhoCR

This comment has been minimized.

Show comment
Hide comment
@CatinhoCR

CatinhoCR Jan 26, 2017

How can I manually update yarn? Not sure about that one, I used brew on my mac to get it working but not sure what "manual" means here... any tips appreciated.

How can I manually update yarn? Not sure about that one, I used brew on my mac to get it working but not sure what "manual" means here... any tips appreciated.

@Daniel15

This comment has been minimized.

Show comment
Hide comment
@Daniel15

Daniel15 Jan 26, 2017

Member
Member

Daniel15 commented Jan 26, 2017

@andreafalzetti

This comment has been minimized.

Show comment
Hide comment
@andreafalzetti

andreafalzetti Jan 27, 2017

@CatinhoCR I initially installed yarn using npm, so I did npm uninstall -g yarn and then brew install yarn - And now I've got the latest version. It would also work using the brew upgrade command as @Daniel15 mentioned.

@CatinhoCR I initially installed yarn using npm, so I did npm uninstall -g yarn and then brew install yarn - And now I've got the latest version. It would also work using the brew upgrade command as @Daniel15 mentioned.

@slootzky

This comment has been minimized.

Show comment
Hide comment
@slootzky

slootzky Jan 30, 2017

npm update yarn -g

npm update yarn -g

@BeHappyF

This comment has been minimized.

Show comment
Hide comment
@BeHappyF

BeHappyF Feb 9, 2017

You might install yarn width homebrew.So brew uninstall yarn.And it's not a good choose to install yarn with homebrew when you need to across the wall.Everytime you need to brew update.It's always time out.....

BeHappyF commented Feb 9, 2017

You might install yarn width homebrew.So brew uninstall yarn.And it's not a good choose to install yarn with homebrew when you need to across the wall.Everytime you need to brew update.It's always time out.....

@wardbell

This comment has been minimized.

Show comment
Hide comment
@wardbell

wardbell Mar 2, 2017

Sadly, npm update yarn -g does not always do the trick. For example, it did not update from v.0.20.3 to v.0.21.3 on my OS/X machine. But the following did work:

npm uninstall yarn -g
npm install yarn -g

wardbell commented Mar 2, 2017

Sadly, npm update yarn -g does not always do the trick. For example, it did not update from v.0.20.3 to v.0.21.3 on my OS/X machine. But the following did work:

npm uninstall yarn -g
npm install yarn -g
@Daniel15

This comment has been minimized.

Show comment
Hide comment
@Daniel15

Daniel15 Mar 2, 2017

Member

npm sometimes has weird issues which is why we don't recommend using it to install Yarn.

Member

Daniel15 commented Mar 2, 2017

npm sometimes has weird issues which is why we don't recommend using it to install Yarn.

@jeff-kilbride

This comment has been minimized.

Show comment
Hide comment
@jeff-kilbride

jeff-kilbride Mar 3, 2017

@wardbell Simply running install works, too:

npm install yarn -g

No need to uninstall first.

@wardbell Simply running install works, too:

npm install yarn -g

No need to uninstall first.

@kristojorg

This comment has been minimized.

Show comment
Hide comment
@kristojorg

kristojorg Mar 10, 2017

I have tried updating manually through homebrew, but when I type yarn --version it is still showing 19.0. I am now trying to uninstall, but seemingly also cannot do that... yarn --version still shows 19.0 after a brew uninstall yarn. I also tried npm uninstall yarn with no luck either.

Can you tell me what I need to delete in order to have yarn completely uninstalled so I can reinstall with the newer version?

I have tried updating manually through homebrew, but when I type yarn --version it is still showing 19.0. I am now trying to uninstall, but seemingly also cannot do that... yarn --version still shows 19.0 after a brew uninstall yarn. I also tried npm uninstall yarn with no luck either.

Can you tell me what I need to delete in order to have yarn completely uninstalled so I can reinstall with the newer version?

@adrianmcli

This comment has been minimized.

Show comment
Hide comment
@adrianmcli

adrianmcli Mar 12, 2017

@kristojorg I had the same problem. I (think I) fixed it by doing a bunch of things:

  1. Removing yarn binaries manually:
rm -f /usr/local/bin/yarnpkg
rm -f /usr/local/bin/yarn
  1. Remove yarn cache:
rm -rf ${HOME}/.yarn
  1. If you have the following in your .zshrc or .bash_profile, remove it:
export PATH="$PATH:`yarn global bin`"
  1. Install via curl:
curl -o- -L https://yarnpkg.com/install.sh | bash
  1. Make sure there is the following line in your .zshrc or .bash_profile:
export PATH="$HOME/.yarn/bin:$PATH"

Now if you try to run yarn -v, you should get the latest stable version.

adrianmcli commented Mar 12, 2017

@kristojorg I had the same problem. I (think I) fixed it by doing a bunch of things:

  1. Removing yarn binaries manually:
rm -f /usr/local/bin/yarnpkg
rm -f /usr/local/bin/yarn
  1. Remove yarn cache:
rm -rf ${HOME}/.yarn
  1. If you have the following in your .zshrc or .bash_profile, remove it:
export PATH="$PATH:`yarn global bin`"
  1. Install via curl:
curl -o- -L https://yarnpkg.com/install.sh | bash
  1. Make sure there is the following line in your .zshrc or .bash_profile:
export PATH="$HOME/.yarn/bin:$PATH"

Now if you try to run yarn -v, you should get the latest stable version.

@kristojorg

This comment has been minimized.

Show comment
Hide comment

Thank you!

@NameFILIP

This comment has been minimized.

Show comment
Hide comment
@NameFILIP

NameFILIP Mar 13, 2017

@kristojorg Can you also change 2. to have ${HOME} instead of /Users/adrianmcli

@kristojorg Can you also change 2. to have ${HOME} instead of /Users/adrianmcli

@obkalu

This comment has been minimized.

Show comment
Hide comment
@obkalu

obkalu Apr 11, 2017

*Just adding this for the benefit of those on Microsoft Windows.
If you originally installed Yarn using Chocolatey (the package manager for Windows), then to update it to the latest release, simply do the following:

  1. Launch open the Windows command shell (cmd.exe) as an administrator.
  2. Run the command: c:>choco upgrade yarn
  3. Run, c:>yarn --version, and confirm that it's been upgraded to the latest version. Voila!

obkalu commented Apr 11, 2017

*Just adding this for the benefit of those on Microsoft Windows.
If you originally installed Yarn using Chocolatey (the package manager for Windows), then to update it to the latest release, simply do the following:

  1. Launch open the Windows command shell (cmd.exe) as an administrator.
  2. Run the command: c:>choco upgrade yarn
  3. Run, c:>yarn --version, and confirm that it's been upgraded to the latest version. Voila!
@aitchkhan

This comment has been minimized.

Show comment
Hide comment
@aitchkhan

aitchkhan Jun 1, 2017

On Ubuntu 16.04, yarn automatically updates via Software & Updates.

On Ubuntu 16.04, yarn automatically updates via Software & Updates.

@M-D-M

This comment has been minimized.

Show comment
Hide comment
@M-D-M

M-D-M Jun 16, 2017

I had a similar problem, and the problem wasn't that npm wasn't updating yarn (it was), but that there were apparently two links in my environment:

One for /usr/bin/yarn that was pointing to /usr/lib/node_modules/yarn/bin/yarn.js (this was the most recent version installed by npm)

And one for /usr/local/bin/yarn that was pointing to /usr/local/lib/node_modules/yarn/bin/yarn.js (this was an old version)

I don't know where the /usr/local/bin/yarn link was coming from, but it was the one being used by my shell when I just typed yarn. I removed the link and now all is good.

M-D-M commented Jun 16, 2017

I had a similar problem, and the problem wasn't that npm wasn't updating yarn (it was), but that there were apparently two links in my environment:

One for /usr/bin/yarn that was pointing to /usr/lib/node_modules/yarn/bin/yarn.js (this was the most recent version installed by npm)

And one for /usr/local/bin/yarn that was pointing to /usr/local/lib/node_modules/yarn/bin/yarn.js (this was an old version)

I don't know where the /usr/local/bin/yarn link was coming from, but it was the one being used by my shell when I just typed yarn. I removed the link and now all is good.

@skube

This comment has been minimized.

Show comment
Hide comment
@skube

skube Jun 22, 2017

@M-D-M How did you remove the /usr/local/bin/yarn link if you didn't know where it was coming from?

skube commented Jun 22, 2017

@M-D-M How did you remove the /usr/local/bin/yarn link if you didn't know where it was coming from?

@M-D-M

This comment has been minimized.

Show comment
Hide comment
@M-D-M

M-D-M Jun 22, 2017

@skube sudo unlink /usr/local/bin/yarn

M-D-M commented Jun 22, 2017

@skube sudo unlink /usr/local/bin/yarn

@skube

This comment has been minimized.

Show comment
Hide comment
@skube

skube Jun 24, 2017

@M-D-M Thanks. So I did unlink /usr/local/bin/yarn which seemed to work.
and then in order to update to the latest, ran npm i -g yarn which seemed to just link up again

❯ npm i -g yarn
/usr/local/bin/yarnpkg -> /usr/local/lib/node_modules/yarn/bin/yarn.js
/usr/local/bin/yarn -> /usr/local/lib/node_modules/yarn/bin/yarn.js

And yet I'm still not updated to the latest 0.24.6

❯ yarn -v
yarn install v0.24.5
[1/4] 🔍  Resolving packages...
success Already up-to-date.
✨  Done in 1.51s.

skube commented Jun 24, 2017

@M-D-M Thanks. So I did unlink /usr/local/bin/yarn which seemed to work.
and then in order to update to the latest, ran npm i -g yarn which seemed to just link up again

❯ npm i -g yarn
/usr/local/bin/yarnpkg -> /usr/local/lib/node_modules/yarn/bin/yarn.js
/usr/local/bin/yarn -> /usr/local/lib/node_modules/yarn/bin/yarn.js

And yet I'm still not updated to the latest 0.24.6

❯ yarn -v
yarn install v0.24.5
[1/4] 🔍  Resolving packages...
success Already up-to-date.
✨  Done in 1.51s.
@M-D-M

This comment has been minimized.

Show comment
Hide comment
@M-D-M

M-D-M Jun 24, 2017

Interestingly enough, when I do sudo npm install --global yarn, the /usr/local/bin links aren't being created, so there's some difference in our environments I can't account for. As for 0.24.5 being the available version, that seems maybe be an npm problem -- 0.24.6 isn't being installed, for some reason.

M-D-M commented Jun 24, 2017

Interestingly enough, when I do sudo npm install --global yarn, the /usr/local/bin links aren't being created, so there's some difference in our environments I can't account for. As for 0.24.5 being the available version, that seems maybe be an npm problem -- 0.24.6 isn't being installed, for some reason.

@jeff-kilbride

This comment has been minimized.

Show comment
Hide comment
@jeff-kilbride

jeff-kilbride Jun 24, 2017

I can confirm that 0.24.6 is not being installed. I have 0.24.5 and when I run npm outdated -g, npm doesn't recognize there's an update available. I don't know if this is an npm issue or an issue with the yarn package.

I am using nvm to manage my node installations, so I don't really have a choice. I need to use npm to install yarn.

I can confirm that 0.24.6 is not being installed. I have 0.24.5 and when I run npm outdated -g, npm doesn't recognize there's an update available. I don't know if this is an npm issue or an issue with the yarn package.

I am using nvm to manage my node installations, so I don't really have a choice. I need to use npm to install yarn.

@skube

This comment has been minimized.

Show comment
Hide comment
@skube

skube Jun 26, 2017

Interestingly, on another machine I was able to...

warning Your current version of Yarn is out of date. The latest version is "0.24.6" while you're on "0.21.3".
info To upgrade, run the following command:
$ curl -o- -L https://yarnpkg.com/install.sh | bash

So I did

❯ curl -o- -L https://yarnpkg.com/install.sh | bash
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  6746    0  6746    0     0  22490      0 --:--:-- --:--:-- --:--:-- 22561
Installing Yarn!
/usr/local/bin/yarn
> Downloading tarball...

> We've added the following to your .zshrc
> If this isn't the profile of your current shell then please add the following to your correct profile:

export PATH="$HOME/.yarn/bin:$PATH"

> Successfully installed Yarn 0.24.6! Please open another terminal where the `yarn` command will now be available.

skube commented Jun 26, 2017

Interestingly, on another machine I was able to...

warning Your current version of Yarn is out of date. The latest version is "0.24.6" while you're on "0.21.3".
info To upgrade, run the following command:
$ curl -o- -L https://yarnpkg.com/install.sh | bash

So I did

❯ curl -o- -L https://yarnpkg.com/install.sh | bash
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  6746    0  6746    0     0  22490      0 --:--:-- --:--:-- --:--:-- 22561
Installing Yarn!
/usr/local/bin/yarn
> Downloading tarball...

> We've added the following to your .zshrc
> If this isn't the profile of your current shell then please add the following to your correct profile:

export PATH="$HOME/.yarn/bin:$PATH"

> Successfully installed Yarn 0.24.6! Please open another terminal where the `yarn` command will now be available.
@nextlevelshit

This comment has been minimized.

Show comment
Hide comment
@nextlevelshit

nextlevelshit Jun 29, 2017

@octopitus In my case I had to add permissions with sudo yarn add global yarn.

@octopitus In my case I had to add permissions with sudo yarn add global yarn.

@localredhead

This comment has been minimized.

Show comment
Hide comment
@localredhead

localredhead Jul 2, 2017

brew upgrade yarn and brew link --overwrite node worked to update yarn on OSX sierra

localredhead commented Jul 2, 2017

brew upgrade yarn and brew link --overwrite node worked to update yarn on OSX sierra

@pencilcheck

This comment has been minimized.

Show comment
Hide comment
@pencilcheck

pencilcheck Jul 7, 2017

You mean brew link --overwrite yarn for the second command right?

You mean brew link --overwrite yarn for the second command right?

@rrotteveel

This comment has been minimized.

Show comment
Hide comment
@rrotteveel

rrotteveel Sep 8, 2017

I believe @localredhead has installed yarn with node. I installed yarn as follows:
brew install yarn --without-node, because I manage node by using nvm.

Probably he is overwriting the link to node, so that he's using the right version instead of the one coming with/from yarn.

I believe @localredhead has installed yarn with node. I installed yarn as follows:
brew install yarn --without-node, because I manage node by using nvm.

Probably he is overwriting the link to node, so that he's using the right version instead of the one coming with/from yarn.

@mikechamberlain

This comment has been minimized.

Show comment
Hide comment
@mikechamberlain

mikechamberlain Sep 12, 2017

It might seem obvious to some, but on Windows mine was installed (I think from the MSI, or from a dev env setup script my company provides) in Program Files (x86). No matter what upgrade method I used yarn version wouldn't budge. I eventually discovered the cause with which yarn which pointed to the offending location. I had to use Windows' "Change or Remove a program" to first to remove it, then simply npm install -g yarn to reinstall at the latest version. Now I can just use npm to control the version, which is much better.

mikechamberlain commented Sep 12, 2017

It might seem obvious to some, but on Windows mine was installed (I think from the MSI, or from a dev env setup script my company provides) in Program Files (x86). No matter what upgrade method I used yarn version wouldn't budge. I eventually discovered the cause with which yarn which pointed to the offending location. I had to use Windows' "Change or Remove a program" to first to remove it, then simply npm install -g yarn to reinstall at the latest version. Now I can just use npm to control the version, which is much better.

@maplion

This comment has been minimized.

Show comment
Hide comment
@maplion

maplion Sep 19, 2017

@mikechamberlain This worked for me, thanks!

maplion commented Sep 19, 2017

@mikechamberlain This worked for me, thanks!

tonietto referenced this issue in tonietto/dotfiles Sep 21, 2017

Remove yarn from PATH
 To make use of yaourt package config instead

@BYK BYK removed their assignment Oct 27, 2017

@BYK

This comment has been minimized.

Show comment
Hide comment
@BYK

BYK Oct 27, 2017

Member

Latest state: we need to reimplement the self-update command that uses the original installation method.

Member

BYK commented Oct 27, 2017

Latest state: we need to reimplement the self-update command that uses the original installation method.

@onurtemizkan

This comment has been minimized.

Show comment
Hide comment
@onurtemizkan

onurtemizkan Oct 28, 2017

Contributor

Working on the reimplementation.

Contributor

onurtemizkan commented Oct 28, 2017

Working on the reimplementation.

@Daniel15

This comment has been minimized.

Show comment
Hide comment
@Daniel15

Daniel15 Oct 28, 2017

Member

@onurtemizkan It should be relatively straightforward. Feel free to message me if you get stuck :)

We already have information on the command that needs to be ran (as Yarn prints out a notice with the command when the version is outdated), Yarn just needs to actually run it. A slightly different case is on Windows when the installer was used, as we'd have to download the installer then msiexec it.

Member

Daniel15 commented Oct 28, 2017

@onurtemizkan It should be relatively straightforward. Feel free to message me if you get stuck :)

We already have information on the command that needs to be ran (as Yarn prints out a notice with the command when the version is outdated), Yarn just needs to actually run it. A slightly different case is on Windows when the installer was used, as we'd have to download the installer then msiexec it.

@SMotaal

This comment has been minimized.

Show comment
Hide comment
@SMotaal

SMotaal Mar 6, 2018

Sorry to interrupt 😉

Have you considered simply delegating this to npm (assuming of course yarn runs if npm exists in the first place).

» npm update -g yarn

The nice thing is that if it does not work out you can always:

So we tried to get npm to handle the update...

Here are your options:
…

Now, aren't u glad to be using yarn for your other packages!

SMotaal commented Mar 6, 2018

Sorry to interrupt 😉

Have you considered simply delegating this to npm (assuming of course yarn runs if npm exists in the first place).

» npm update -g yarn

The nice thing is that if it does not work out you can always:

So we tried to get npm to handle the update...

Here are your options:
…

Now, aren't u glad to be using yarn for your other packages!
@Daniel15

This comment has been minimized.

Show comment
Hide comment
@Daniel15

Daniel15 Mar 6, 2018

Member

@SMotaal There's a few issues with that:

  • If you installed Yarn via another method, you'll now have two versions of Yarn installed (one via the system package manager, and one via npm)
  • Not everyone has npm installed. Yarn does not require npm installed to run
Member

Daniel15 commented Mar 6, 2018

@SMotaal There's a few issues with that:

  • If you installed Yarn via another method, you'll now have two versions of Yarn installed (one via the system package manager, and one via npm)
  • Not everyone has npm installed. Yarn does not require npm installed to run
@Resen4983

This comment has been minimized.

Show comment
Hide comment
@Resen4983

Resen4983 Mar 7, 2018

if your system is Windows and had installed npm ,you can use npm install yarn@latest -g to update to top version.

if your system is Windows and had installed npm ,you can use npm install yarn@latest -g to update to top version.

@SMotaal

This comment has been minimized.

Show comment
Hide comment
@SMotaal

SMotaal Mar 7, 2018

I can't remember how I set it up on this mac roughly a year ago, I know I was using something other than NPM at one point, but when I lost my thread I simply NPMed and I have no issues other than yarn complaining when I'm fairly behind which reminds me to update and I simply npm update -g yarn and forget about it till next reminder.

From a user's perspective, I think yarn can recommend "supported" and maybe mention "unofficial" where if "unofficial" and it does not "work as intended" please use "supported" to install and here is "recommended" if you need to undo "unofficial"

Honestly, it is important for a package manager to have a clear path for itself to be well-managed.

SMotaal commented Mar 7, 2018

I can't remember how I set it up on this mac roughly a year ago, I know I was using something other than NPM at one point, but when I lost my thread I simply NPMed and I have no issues other than yarn complaining when I'm fairly behind which reminds me to update and I simply npm update -g yarn and forget about it till next reminder.

From a user's perspective, I think yarn can recommend "supported" and maybe mention "unofficial" where if "unofficial" and it does not "work as intended" please use "supported" to install and here is "recommended" if you need to undo "unofficial"

Honestly, it is important for a package manager to have a clear path for itself to be well-managed.

@Stanzilla

This comment has been minimized.

Show comment
Hide comment
@Stanzilla

Stanzilla Mar 12, 2018

@onurtemizkan are you still working on this?

@onurtemizkan are you still working on this?

@WhoAteDaCake

This comment has been minimized.

Show comment
Hide comment
@WhoAteDaCake

WhoAteDaCake Apr 18, 2018

Are there any updates?
My current approach is: yarn global add yarn@latest which doesn't seem like ideal way

WhoAteDaCake commented Apr 18, 2018

Are there any updates?
My current approach is: yarn global add yarn@latest which doesn't seem like ideal way

@GabrielDuarteM

This comment has been minimized.

Show comment
Hide comment
@GabrielDuarteM

GabrielDuarteM Apr 19, 2018

For those just wanting to update yarn automatically on windows, without having to download the binary, I've been using choco for a while to do that, and it is doing this job flawlessly. It's a cmd line tool to install programs (just like apt-get). You just run choco install yarn, and yarn is installed. To update, the command is choco upgrade yarn.

For those just wanting to update yarn automatically on windows, without having to download the binary, I've been using choco for a while to do that, and it is doing this job flawlessly. It's a cmd line tool to install programs (just like apt-get). You just run choco install yarn, and yarn is installed. To update, the command is choco upgrade yarn.

@Stanzilla

This comment has been minimized.

Show comment
Hide comment
@Stanzilla

Stanzilla Apr 19, 2018

No sorry, chocolatey is just horrible.

No sorry, chocolatey is just horrible.

@Daniel15

This comment has been minimized.

Show comment
Hide comment
@Daniel15

Daniel15 Apr 19, 2018

Member
Member

Daniel15 commented Apr 19, 2018

@begin-again

This comment has been minimized.

Show comment
Hide comment
@begin-again

begin-again May 8, 2018

Scoop is an alternative to Chocolatey and works a lot like brew.

begin-again commented May 8, 2018

Scoop is an alternative to Chocolatey and works a lot like brew.

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