Skip to content

Commit 9efa1cf

Browse files
eoingroatmerceyz
authored andcommitted
docs: clarify the zero-installs requirements (#4619)
(cherry picked from commit 8a32d6f)
1 parent a4c8334 commit 9efa1cf

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

packages/gatsby/content/features/zero-installs.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,9 @@ Note that these challenges are not unique to Yarn — you may remember a time wh
2525

2626
In order to make a project zero-install, you must be able to use it as soon as you clone it. This is very easy starting from Yarn 2!
2727

28-
- First, ensure that your project is using [Plug'n'Play](/features/pnp) to resolve dependencies via the cache folder and **not** from `node_modules`.
28+
- First, check that you are using Yarn 2 or later using `yarn --version`. You can change the version with [`yarn set version <version>`](/cli/set/version/)
29+
30+
- Next, ensure that your project is using [Plug'n'Play](/features/pnp) to resolve dependencies via the cache folder and **not** from `node_modules`.
2931

3032
- While in theory you could check-in your `node_modules` folder rather than the cache, in practice the `node_modules` contains a gigantic amount of files that frequently change location and mess with Git's optimizations. By contrast, the Yarn cache contains exactly one file per package, that only change when the packages themselves change.
3133

0 commit comments

Comments
 (0)