Issues with bump: `eslint 10.20.0` and `@antfu/eslint-config 8.2.0`

[kheiner]

Separating from #31.

I think it has do to with the Node Version but 🤷 . Works on my machine (using 24.13.1)

The actions/checkout@v4 runs with node 20.20.2 (tested in 6fdf9c7)

Warning: Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

I didn't see anything in 10.0.0 ... 10.2.0 that suggests it wouldn't work.

Once this is figured out revert the previous reverts: 6fdf9c7 & b58aac1 .

I thought using the runner actions/checkout@v5 would work but it didn't. Tired of messing with it.

• eslint: [ v10.2.0 ]
• Requires Node v20.19+, v22.13+, or v24+.
  • The release pipeline uses node-version: lts/*
  • ~~The ci pipeline uses 20.20.2 via actions/checkout@4. ⚠️ Despite docs saying it should work, it fails on ci pipeline stage. ~~ Verified that eslint requires LTS 22 or later, 20 is incorrect. See Issues with bump: eslint 10.20.0 and @antfu/eslint-config 8.2.0 #33 (comment)
  • Old config format not supported: fixed in 0df1e1d
• @antful/eslint-config: [ v8.2.0 ]
  • TODO: markdown/headling-increment Docs intentionally skip heading to separate concerns + support index.md display of everything. FIX is to add <!-- eslint-disable-next-line markdown/heading-increment --> ahead of errors.
  • TODO: e18e/prefer-regex-test FIX is to run lint:fix.

[kheiner]

Note

The function causing the issue is object.groupBy()

Support for object.groupBy() was added to bun v1.0.19 and node v21.0.0. The first LTS version of Node to support it is v22.0.0

See MDN Documentation

link

        "groupBy": {
          "__compat": {
            "mdn_url": "https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Object/groupBy",
            "spec_url": "https://tc39.es/ecma262/multipage/fundamental-objects.html#sec-object.groupby",
            "tags": [
              "web-features:array-group"
            ],
            "support": {
+            "bun": {
+              "version_added": "1.0.19"
              },
              "chrome": {
                "version_added": "117"
              },
              "chrome_android": "mirror",
              "deno": {
                "version_added": "1.37"
              },
              "edge": "mirror",
              "firefox": {
                "version_added": "119"
              },
              "firefox_android": "mirror",
+            "nodejs": {
+              "version_added": "21.0.0"
              },

The fix!

Update the ci pipeline to use the action actions/setup-node@v4 to mirror the release pipeline handling:

nuxt-directus-sdk/.github/workflows/release.yml

Lines 22 to 24 in 2621146

	- uses: actions/setup-node@v4
	with:
	node-version: lts/*

I have verified that this uses the lts/krypton -> v24.4.1 at present and adds 1s to the time to run the script.