🔧 chore: use yarn v3.6.1 to manage project

[tp26610]

I plan to add an example App to this project and manage it with Yarn v3. This PR is the first step, and the example App will be added gradually over the next few PRs.

[LinusU]

Hmm, I personally would prefer using npm as it doesn't require anything extra. This adds 905 lines to the repository, more lines than the rest of the project 😅

What are the advantages of using yarn?

---

Also, what are the advantages of having the example app inside this repo? What I do when I want to test out a release is to use npm pack and npm add that tar gz file to an example app, to be 100% that it's the same setup as someone installing the final package from npm.

As this is just a simple polyfill, I don't see that there is any functionality that anyone would need to explore before deciding to use this package? 🤔

---

edit: I got curious so did a quick line count by hand, it seems to be ~420 lines of code in the repo right now 😁

[tp26610]

Thanks for the feedback! Having an example app just makes it easier for contributors to run the project and test that everything works properly on both Android and iOS — saves a bunch of setup time 🙂

As for Yarn, I just followed the official React Native “Create Module Library” guide, which uses Yarn v3 by default. No strong reason behind it, just sticking to what the docs suggest for now 😅

Personally, I don’t mind the repo getting a bit larger — as long as the published package stays small and clean on npm, that’s what really matters