chore(deps): update dependency globby to v14

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
globby	^13.2.2 -> ^14.0.0

---

Release Notes

sindresorhus/globby (globby)

v14.0.0

Compare Source

Breaking

• Require Node.js 18 2c06ae5

Improvements

• Add convertPathToPattern() method 3bd00a6

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[pi0]

Here we go this is first engine-incompatible/runtime-compatible dependency..

npm seems to use soft warnings:

pnpm (interestingly) not even a warning

yarn fails:

---

Considering pnpm and npm the major package managers have soft warning behavior and issue with yarn is solvable using skip-engines flag ++ Node.js 16 is EOL for a while and to avoid stalling behind more dependencies, i am thinking to do this by next minor release with clear instruction for users that really have no option rather than sticking with Node 16. More and more (nested) dependencies such as @sindresorhus/merge-streams are being Node 18 and this change is inevitable.

/cc @danielroe If you have serious concerns about delaying this, love to hear and discuss alternatives.

[pi0]

Seems Nuxt (via devtools, tailwindcss) already has Node 18 depednency is-installed-globally (it is also soft-warn)

[danielroe]

Thank you for the research. I'm happy to go ahead. We should add something to Nuxt docs too (as well, perhaps, as Nitro's).