chore: set npm as default package manager to init

[TMisiukiewicz]

Summary:

After discussing it internally, we decided to make npm a default package manager for projects created with init. yarn in version >= 3 generates a lot of issues and makes the first experience with React Native worse.

Test Plan:

1. Run init command locally
2. Once the process is complete, verify package-lock.json is in the folder, and there is no yarn.lock file
   Checklist

---

• Documentation is up to date to reflect these changes.
• Follows commit message convention described in CONTRIBUTING.md

[thymikee]

Thanks! Let's hold on with merging for now and keep on discussing when to proceed

[szymonrybczak]

👍

[cortinico]

yarn in version >= 3 generates a lot of issues and makes the first experience with React Native worse.

Can you elaborate on this?

[szymonrybczak]

Can you elaborate on this?

Since we added Yarn v3.x as the default package manager for init we received a bunch of issues internally/externally e.g. #2467, #2468, that we've tried to resolve but with no lack unfortunately. After time the bump to higher Yarn version seems very unstable to us. By moving to npm by default user still have an ability to migrate to Yarn by running two commands in new project, but now it's opt-in and hopefully we'll avoid a bunch of problems. I hope that this makes decision more clear to you!