This includes some breaking changes from glob that have an effect on us:
Results are no longer returned sorted - so we now do a .sort() ourselves on the array
Backslashes are no longer considered valid in Windows paths and are interpreted as an escape character - there is a backwards compatibility option for this which we're using - I'd rather just bring users along but it will be quite an involved change and not something we need to do immediately
Requires Node.js 18 or above - this means we should land #2325 before this, although no tests have failed on 14 or 16 interestingly
Nothing breaking for our users, though.
⚡️ What's your motivation?
Fixes #2329 as the vulnerable dependency is no longer present (at least not in production code - you can see via npm ls inflight that some test packages still depend on it, but we can handle that in due course). Also just gets us current.
🏷️ What kind of change is this?
:bank: Refactoring/debt/DX (improvement to code design, tooling, documentation etc. without changing behaviour)
:bug: Bug fix (non-breaking change which fixes a defect)
coverage: 97.931% (-0.5%) from 98.458% when pulling 28421d19aa773a91835cca292679732d5ef8c92f on fix/glob-upgrade into 89ec3b6e86540c12e53267633e5876a67ae854bc on main.
🤔 What's changed?
Upgrade
glob
to the latest version.This includes some breaking changes from
glob
that have an effect on us:.sort()
ourselves on the arrayNothing breaking for our users, though.
⚡️ What's your motivation?
Fixes #2329 as the vulnerable dependency is no longer present (at least not in production code - you can see via
npm ls inflight
that some test packages still depend on it, but we can handle that in due course). Also just gets us current.🏷️ What kind of change is this?
📋 Checklist:
This text was originally generated from a template, then edited by hand. You can modify the template here.