Engine and dependency updates

[novemberborn]

Drop 18 and 23. Require nearly latest minor versions so we can adopt the latest stable features.

Update dependencies.

[hildjj]

bcoe/c8#581 can be worked around with an "overrides" statement in package.json for yargs@18.0.0

[novemberborn]

I tried that but it didn't work. Doesn't look like downgrading
helped either though.

[hildjj]

This seemed to mostly work for me:

diff --git a/package.json b/package.json
index 19c4259c..99cedd5d 100644
--- a/package.json
+++ b/package.json
@@ -132,7 +132,7 @@
 		"@sindresorhus/tsconfig": "^8.1.0",
 		"@types/node": "^24.10.15",
 		"ansi-escapes": "^7.3.0",
-		"c8": "^10.1.3",
+		"c8": "^11.0.0",
 		"execa": "^9.6.1",
 		"expect": "^30.2.0",
 		"sinon": "^21.0.1",
@@ -154,5 +154,13 @@
 	"volta": {
 		"node": "24.14.0",
 		"npm": "11.11.0"
+	},
+	"overrides": {
+		"c8": {
+			"yargs": "18.0.0"
+		},
+		"@ava/v6": {
+			"yargs": "18.0.0"
+		}
 	}
 }

[ericcornelissen]

I might be mistaken but I believe the "overrides" field does not apply to consumers of a package. That is, if ava where to add this and I installed ava as a dependency, my project would not follow the overrides specified by ava.

Unfortunately the docs don't specify the behavior very clearly, so I'm not sure about this (and I'm unsure how to test it), but I believe the following paragraphs says so:

Overrides are only considered in the root package.json file for a project. Overrides in installed dependencies (including workspaces) are not considered in dependency tree resolution. Published packages may dictate their resolutions by pinning dependencies or using an npm-shrinkwrap.json file.

[ericcornelissen]

My two cents: I think you can either wait for bcoe/c8#581 to be resolved or drop Node.js v25 support for now, Node.js v26 should be just around the corner anyway and you can always add Node.js v25 support back later if needed/requested.

[novemberborn]

@ericcornelissen c8 is a dev dependency here so it doesn't matter.

[ericcornelissen]

@ericcornelissen c8 is a dev dependency here so it doesn't matter.

Can't believe I missed that 😳 glad to see CI passing now though.