n/no-unsupported-features/es-syntax with TypeScript transpilation about eslint-plugin-n

[aladdin-add]

yes,sounds a bug to me. will take a look later.~

[AndrewMSHowe]

More info: I downgraded XO back to 0.49, and I got a bunch of errors about "Definition for rule n/no-unsupported-features/es-syntax was not found." That was what I added to my config file. And removing that made it the errors go away. So It is somehow hooking up with eslint-plugin-n, but the ignores thing is not working I think?

[aladdin-add]

as seen in the node.green:

• optional chaining was supported in node.js>=14.5.0 https://node.green/#ES2020-features-optional-chaining-operator-----
• logical assignment: node.js>=15.14.0 https://node.green/#ES2021-features-Logical-Assignment

ofc, you can safely disable the rule if using a transpiier like ts/babel/esbuild/...

[aladdin-add]

if using xo v0.49 => the rule is node/no-unsupported-features/es-syntax.
xo v0.50 => n/no-unsupported-features/es-syntax. (a breaking change)

[AndrewMSHowe]

OK, but I had xo 0.50, and I had "n/", and it didn't seem to ignore those rules.

[AndrewMSHowe]

In theory, should this have worked? Or is there an issue with what I have written?
"n/no-unsupported-features/es-syntax": ["error", { "ignores": [ "optionalChaining", "nullishCoalescingOperator" ] }]

[aladdin-add]

I tried with the provided config, it output a config errror:

ESLint: 8.15.0

Error: .eslintrc.js:
        Configuration for rule "n/no-unsupported-features/es-syntax" is invalid:
        Value "nullishCoalescingOperator" should be equal to one of the allowed values.

turns out it should be named "nullishCoalescingOperators" 😂. Not sure you didn't see it, maybe an issue in xo?

[AndrewMSHowe]

I'm not sure where I got those strings from, but anyway changing it to "nullishCoalescingOperators" didn't fix anything. And it doesn't explain why "optionalChaining" doesn't work. Well, it does seem that maybe xo is not forwarding these or returning the above error. Someone on the eslint discord channel was sure it was a problem with the n module, but I was not so sure. I guess I'll try reporting it to xo and see if they want to punt it somewhere else :) Thanks for looking into it, anyway.