Glob dependency is outdated

[valleywood]

Problem: test-exclude (used by babel-plugin-istanbul for Jest coverage) expects glob to export a function, but glob v11 exports an object. This breaks coverage collection.

The latest possible version of glob that can be installed is 10.3.3.

The earliest fixed version is 10.5.0.

Version in package.json here specified as ^10.4.1

[YasharF]

This can be fixed by #65

[ericcornelissen]

Furthermore, all versions of glob prior to v12 have been deprecated, so test-exclude should be updated to move to a newer (major) version of glob.

[YasharF]

For anyone looking for a temporary workaround while waiting for the fix in PR #65 to be merged and released, you can use a fork with the patch applied and reference it via an override. Since it's unclear when the next release will happen, this can unblock you in the meantime.

If you don't want to maintain your own fork, I have one with the patch applied that you can reference directly in your package.json with:

  "overrides": {
    "test-exclude": "github:SeattleDevs/test-exclude"
  },

If you prefer to do this yourself (this is how the fork above was created):

1. Fork https://github.com/istanbuljs/test-exclude

2. Clone your fork locally, then pull in the commits from PR Replace glob with tinyglobby, minimatch with micromatch #65 and push them to your repo:

git remote add upstream https://github.com/istanbuljs/test-exclude.git
git fetch upstream
git checkout -b pr-65 upstream/pull/65/head
git push origin pr-65

3. Add the following export to your fork's package.json:

  ,"exports": {
    ".": "./index.js",
    "./package.json": "./package.json",
    "./index.js": "./index.js",
    "./is-outside-dir.js": "./is-outside-dir.js",
    "./is-outside-dir-posix.js": "./is-outside-dir-posix.js",
    "./is-outside-dir-win32.js": "./is-outside-dir-win32.js",
    "./nyc.config.js": "./nyc.config.js"
  }

4. Remove release-please.yml config as you are not publishing to npm. You can also remove the funding yml if you like I guess.
5. Reference your fork in your project's package.json:

  "overrides": {
    "test-exclude": "github[your/repo username]/test-exclude"
  },

6. Optionally, you can add Dependabot and a CI workflow to keep the fork's dependencies up to date.

• similar to https://github.com/SeattleDevs/test-exclude/blob/master/.github/workflows/ci.yaml and https://github.com/SeattleDevs/test-exclude/blob/master/.github/dependabot.yml

7. Once a new version is published to npm, you can remove the override and fork.

[ericcornelissen]

This appears to have been resolved with the release of test-exclude@8.0.0