Add Yarn files to .gitignore

[zhongwuzw]

Summary:

After running yarn install in the root directory of a React Native project, cached files from Yarn appear when checking Git changes, which can be a bit annoying. Let's ignore them! :)

This commit references #42313.

Changelog:

[GENERAL] [ADDED] - Add Yarn files to .gitignore in react-native

Test Plan:

yarn cached files should ignore after exec pod install

[cortinico]

/rebase

[huntie]

@zhongwuzw How are you configuring Yarn here? Yarn should not generate any v3/v4 files in .yarn/ when it detects a Yarn Classic (1.x) project such as this repository. (Happy to be corrected on if this behaviour has changed.)

Are you instead aiming to ignore .yarn/ files in a newly created React Native project via the Community CLI? (cc @szymonrybczak)

[zhongwuzw]

@zhongwuzw How are you configuring Yarn here? Yarn should not generate any v3/v4 files in .yarn/ when it detects a Yarn Classic (1.x) project such as this repository. (Happy to be corrected on if this behaviour has changed.)

@huntie I don't change any configs in my react-native repo, maybe because my yarn version is v3?

Are you instead aiming to ignore .yarn/ files in a newly created React Native project via the Community CLI? (cc @szymonrybczak)

No, I did some work in react-native repo , not a rn project via cli.

[huntie]

@zhongwuzw Thanks for clarifying!

Interesting. Can you share more about how you installed Yarn on your system?

On my Mac, I've used brew install yarn, which is currently 1.22.19 globally, and works with this repo. (Then, what I mentioned was the other way round: If I cd into a project specifying Yarn 4 (containing .yarnrc.yml), Corepack/my Yarn 1.x binary will select that newer Yarn version for that other project.)

I tried out a Corepack install (i.e. following modern Yarn's current install process). If I spin up a fresh GitHub Codespace and try this, it also resolves to Yarn 1.x:

---

The main thing to note here is this repository requires Yarn 1.x. I'll open a separate PR which helps programatically manage this via Corepack. And perhaps we should also update our contributing docs.

[zhongwuzw]

@huntie Sorry I forgot how to install and upgrade my yarn on my Mac :) , and I don't use any yml to specify yarn's version.

[huntie]

@zhongwuzw Okay 🙂 Curious if you could try again with the change from #47091.

[zhongwuzw]

@zhongwuzw Okay 🙂 Curious if you could try again with the change from #47091.

@huntie I applied the changes of #47091, I removed the .yarn directory and exec yarn install again , it still creates .yarn directory.

[huntie]

@zhongwuzw Can you also check and remove any .yarnrc[.yml] in the project dir and all parent directories?

Annoyingly, if globally configured (example is contrived), Yarn can self-upgrade itself in the repo, ignoring "packageManager" and even "engines" -_-.

• Do you get any similar Yarn output saying it's migrating your project?
• Also can you try freshly cloning facebook/react-native in a separate directory?

Either way, we require Yarn 1.x in this repo, so I won't be able to accept this .gitignore change, which will mask an incorrect install.

[zhongwuzw]

@zhongwuzw Can you also check and remove any .yarnrc[.yml] in the project dir and all parent directories?

Not have any .yarnrc[.yml] in the project dir and all parent directories.

Annoyingly, if globally configured (example is contrived), Yarn can self-upgrade itself in the repo, ignoring "packageManager" and even "engines" -_-.

* Do you get any similar Yarn output saying it's migrating your project?

No.

• Also can you try freshly cloning facebook/react-native in a separate directory?

@huntie I tried it and applied your #47091, it also creates .yarn directory.

Either way, we require Yarn 1.x in this repo, so I won't be able to accept this .gitignore change, which will mask an incorrect install.

ok, I'll add the gitignore on my local env. I'll close it.