Skip to content

Commit

Permalink
Document the removal of yarn global (#903)
Browse files Browse the repository at this point in the history
Not sure of the wording desired here but this confused me a bit when I migrated until I came across #821. I'm confident other people will be left confused as well. Wrote this based on what I read there in the aforementioned issue.
  • Loading branch information
julientregoat committed Feb 7, 2020
1 parent 39e749e commit 55a6a38
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions packages/gatsby/content/advanced/migration.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,10 @@ Run `npx @yarnpkg/doctor .` (or `yarn dlx @yarnpkg/doctor .`) in your project to

Note that the doctor is intended to report any potential issue - it's then up to you to decide whether they are a false positive or not (for example it won't traverse Git repositories). For this reason we don't recommend using it as a CI tool.

### Use `yarn dlx` instead of `yarn global`

`yarn dlx` is designed to execute one off scripts that may have been installed as global packages with `yarn 1.x`. Managing system-wide packages is outside of the scope of `yarn`. To reflect this, `yarn global` has been removed. [Read more on GitHub](https://github.com/yarnpkg/berry/issues/821).

### Make sure you use `resolve@1.9+`

Older releases don't support Plug'n'Play at all. Since the `resolve` package is used by pretty much everything nowadays, making sure that you use a modern release can go a long way to solve the most obnoxious bugs you may have.
Expand Down

0 comments on commit 55a6a38

Please sign in to comment.