Fix CMS Quick Start for NPM compatibility

[nclsndr]

What does it do?

Invite user to coherently use npm over yarn. The rationale being that the CLI is prompting for npm use by default.

Why is it needed?

This would help newcomers to the JS stack to not stumble upon errors because of Yarn. Neither creating both the package-lock.json from npm and yarn.lock from yarn.

Related issue(s)/PR(s)

I did not found any related issues.

[strapi-cla]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

Nico André seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
documentation	Ready	Preview	Comment	Sep 17, 2025 3:32pm

[pwizla]

Thanks, @nclsndr!
It makes sense, indeed (though I personally prefer yarn, but let's stay consistent with the product 😄)
The PR is now approved, merged, should be live on docs.strapi.io in a few minutes, and will be mentioned in the next weekly snapshot release.