Bug: no-unsupported-features/es-builtins: fetch reported unsupported despite Node.js >=18.16.0 about eslint-plugin-n

[scagood]

Thank you for the report!

🤔 Technically fetch was not supported until 21.0.0, and so should be experimental in 18.20.1:

---

However, there is still a bug here, as we mark is as supported in v18:

eslint-plugin-n/lib/rules/no-unsupported-features/es-builtins.js

Lines 604 to 606 in a0b45ee

	fetch: {
	[READ]: { supported: ["18.0.0"] },
	},

This could be related to #252, but 18.0.0 is a subset of >=18.0.0.

[aladdin-add]

can you file the issue in node-semver repo, please? 🙏

[scagood]

It makes me think that the wrong value is getting to isSupported

As the range is truthy:
https://runkit.com/scagood/662900db83c1e60008f2ccd4

[aladdin-add]

> semverRangeSubset('>=18.1.0', '>=18.0.0 <19||>18')
false

it seems an issue in node-semver. I'll revert that change then.

[aladdin-add]

just pushed a patch: https://github.com/eslint-community/eslint-plugin-n/releases/tag/v17.3.1

[scagood]

mmm, that is a strange bug!

const subset = require("semver/ranges/subset")

subset('^17.2.0 || >17', '^17.2.0 || >17')  // true
subset('^17.2.0 || >17', '^17.2.0 || >=18') // true
subset('^17.2.0 || >=18', '^17.2.0 || >17') // true

subset('^17.2.0 || >17', '>=17.2.0') // true
subset('>=17.2.0', '^17.2.0 || >17') // false

subset('^17.2.0 || >=18', '>=17.2.0') // true
subset('>=17.2.0', '^17.2.0 || >=18') // false

---

I was wondering if something like this would work, but alas it does not either:

const [ latest ] = rsort(supported);
const range = getSemverRange(
  [
    ...supported.map((version) => `^${version}`),
    `>= ${major(latest + 1)}`,
  ].join('||'),
);

[scagood]

I am going to close this, as I think the patch did fix it.

We can track the semver issue in #250.