chore: use npx --yes

[slorber]

Motivation

temp workaround for npm/cli#4619 until we use a newer node/npm version in CI matrix without this bug

Already attempted in #7167 : we can now try again thanks to Node 16 upgrade

[netlify]

✅ [V2]

Name	Link
🔨 Latest commit	15b48b2
🔍 Latest deploy log	https://app.netlify.com/sites/docusaurus-2/deploys/62989a63c9d13f00098f5f9a
😎 Deploy Preview	https://deploy-preview-7549--docusaurus-2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[github-actions]

⚡️ Lighthouse report for the deploy preview of this PR

URL	Performance	Accessibility	Best Practices	SEO	PWA	Report
/	🟠 84	🟢 100	🟢 100	🟢 100	🟢 90	Report
/docs/installation	🟠 84	🟢 99	🟢 100	🟢 100	🟢 90	Report

[Josh-Cena]

I didn't realize the core has no README... We should definitely have something better...

[slorber]

yes 😄 also surprised

this was just for the CI anyway

[slorber]

@Josh-Cena the CI path filtering is a bit too aggressive IMHO

When we commit to root package.json or other similar global things, all CIs should rather run?

In my case only a few checks did run, and I had to commit a readme to trigger more.

While I really want Windows CI to run in this case because it was the reason we didn't merge the previous PR

We probably want to include a few extra things:

• package.json / .yarn-lock
• jest.config.mjs

Any opinion?

[netlify]

✅ [V2]

Name	Link
🔨 Latest commit	5d4d3ea
🔍 Latest deploy log	https://app.netlify.com/sites/docusaurus-2/deploys/62989b9ce6cc530009c84af6
😎 Deploy Preview	https://deploy-preview-7549--docusaurus-2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[Josh-Cena]

• package.json / yarn-lock
• jest.config.mjs

Agree to trigger for package.json & jest config, but probably not yarn lock, because lockfile changes without package JSON changes are... not meant to be there, if you get what I mean. They do not really mean anything in practice.

[github-actions]

Size Change: 0 B

Total Size: 798 kB

ℹ️ View Unchanged

Filename	Size
website/.docusaurus/globalData.json	52.6 kB
website/build/assets/css/styles.********.css	106 kB
website/build/assets/js/main.********.js	600 kB
website/build/index.html	38.9 kB

_{compressed-size-action}

[slorber]

Agree to trigger for package.json & jest config, but probably not yarn lock, because lockfile changes without package JSON changes are... not meant to be there, if you get what I mean. They do not really mean anything in practice.

Not sure what you mean here

If you decide to re-generate a lockfile without touching package.json file, and due to upgraded dependencies the build fails on Windows for some obscure reason, don't we want to catch it before merging?

[Josh-Cena]

Ah yes, that would make sense.