yarn add global yarn@0.17.8: config.maybeReadManifest is not a function

[appsforartists]

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

What is the current behavior?
https://gist.github.com/appsforartists/71aa9c12cb32927daba62c488a923659

If the current behavior is a bug, please provide the steps to reproduce.
yarn global add yarn@0.17.8

Please mention your node.js, yarn and operating system version.
yarn@0.16.1
node@6.2.1
macOS@10.11.6

[appsforartists]

Incidentally, re-running yarn global add yarn@0.17.8 (now that yarn appears to have upgraded) seems to work fine.

[Daniel15]

Installing Yarn via Yarn is not a supported use case at the moment (also see my comments on #1998) so there's probably bugs with it. In general, global packages may need some more love, as Yarn has mainly been focused on project-specific dependencies.

[Daniel15]

The correct way to upgrade Yarn using Yarn is to use the self-update command (https://yarnpkg.com/en/docs/cli/self-update), but I don't think it's fully-functional yet. Eventually it will upgrade Yarn using the same installation method you originally used (varies based on platform)

[BYK]

Closing since this issue seems to be quite stale. Also, we do not support installing yarn from npm as @Daniel15 mentioned earlier.

[appsforartists]

Are the plans for self-update to ever work, or is Homebrew the only supported upgrade path?

[Daniel15]

There are plans to reimplement self-update, however it'll just update using the same installation method. For example, if you install Yarn via Homebrew, it'll update using Homebrew. Sent from my phone.

…

On Jan 24, 2018 9:21 AM, "Brenton Simpson" ***@***.***> wrote: Are the plans for self-update to ever work, or is Homebrew the only supported upgrade path? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2015 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAFnHVggm3fULsZfZTMoNOAa2jMVYEEyks5tN2asgaJpZM4K7JD9> .