Skip to content
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.

Sign up for GitHub

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

Jump to bottom

yarn global upgrade needed? or just use yarn global add ... ? #776

Closed
jokeyrhyme opened this issue Oct 12, 2016 · 5 comments
Closed

yarn global upgrade needed? or just use yarn global add ... ? #776

jokeyrhyme opened this issue Oct 12, 2016 · 5 comments

Comments

@jokeyrhyme
Copy link

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

feature ? really a question about a possible feature? :)

What is the current behavior?

We can yarn add blah and yarn upgrade

We can also yarn global add blah

But we can't yet yarn global upgrade. Is this something we should have?

Note that this is not for parity with npm, because npm --global update pretty much never had the expected behaviour, and its usage was discouraged as far as I can tell.

What is the expected behavior?

yarn global upgrade works its magic, and all globally installed packages are now their latest available versions

I do not think yarn itself should be upgraded, as we'll have yarn self-update for that

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

node --version

v6.7.0

yarn --version

0.15.1

uname -a

Darwin fulmen.local 16.1.0 Darwin Kernel Version 16.1.0: Mon Oct 3 14:03:15 PDT 2016; root:xnu-3789.21.3~20/RELEASE_X86_64 x86_64
@moimael
Copy link

moimael commented Oct 13, 2016

Also I think that a yarn global outdated command is much needed too.

@adamsiwiec
Copy link

This could be dangerous and discouraged, but what about yarn global clean being added to the cli?

@lgh06
Copy link

lgh06 commented Oct 27, 2016

I also wanna update a package globally installed...

@ghost ghost mentioned this issue Nov 2, 2016
Merged
sebmck pushed a commit that referenced this issue Nov 2, 2016
Adding 'yarn global upgrade'(Issue #776) (#1616)
ebe8993
@cchamberlain
Copy link

Not sure why this is necessary? Running lerna global add <package>@latest works fine for me and is inline with how local npm installs work when it comes to updates.

@wyze wyze removed the needs triage label Nov 3, 2016
Jessidhia pushed a commit to Jessidhia/yarn that referenced this issue Nov 4, 2016
Merge branch 'master' into npm4-prepublish
fda0ecf 
* master: (66 commits)
  Add --no-bin-links flag - fixes yarnpkg#929 (yarnpkg#1651)
  Add option to change the prefix of the global bin folder - fixes yarnpkg#630 (yarnpkg#1654)
  patterns -> filteredPatterns
  Add helpful nudge to yarnpkg/rfcs on issue template (yarnpkg#1650)
  Change reporter.log to console.log in generate-lock-entry command - fixes yarnpkg#644 (yarnpkg#1652)
  Fixed add command flag (yarnpkg#1653)
  Nested executables fix (yarnpkg#1210)
  Added short-flags for yarn add (yarnpkg#1618)
  Add name lookups to ls command - fixes yarnpkg#1599 (yarnpkg#1643)
  Disable flaky secureUrl test (yarnpkg#1644)
  Add unit tests for `yarn why`. (yarnpkg#1544)
  Refine flow type for config.generateHardModulePath (yarnpkg#1642)
  Use ~/Library/Caches as default cache location on OSX - fixes yarnpkg#1637 (yarnpkg#1638)
  Update aliases.js (yarnpkg#1635)
  Update aliases.js (yarnpkg#1634)
  Add webhook to archive AppVeyor build artifacts (yarnpkg#1631)
  Attempt to fix failing Circle CI builds (yarnpkg#1629)
  Adding 'yarn global upgrade'(Issue yarnpkg#776) (yarnpkg#1616)
  Show error message in stdout. (yarnpkg#1502)
  Nicer permission errors when trying to write global binaries - fixes yarnpkg#1578 (yarnpkg#1592)
  ...
@sebmck sebmck mentioned this issue Nov 4, 2016
Closed
@turdiyev
Copy link

turdiyev commented Sep 24, 2017 •
edited
Loading

npm install -g yarn works only

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@wyze @cchamberlain @jokeyrhyme @sebmck @moimael @lgh06 @turdiyev @adamsiwiec