Add support for TypeScript syntax

[ota-meshi]

It seems that the ESLint core rules are currently working on supporting TypeScript syntax.

It seems that this package does not handle TypeScript syntax well in some patterns, but it would be good if it could cover those.
However, I'm not yet sure what kind of problems it has.

At least the n/no-deprecated-api rule of eslint-plugin-n does not seem to handle the following expression using ! well. I think this is because this package does not support TypeScript syntax.

/* eslint "n/no-deprecated-api": "error" */
const fs = require("fs");
fs.exists("./foo.js", function() {}); // Reported
fs!.exists("./foo.js", function() {}); // Ignore?

https://eslint-online-playground.netlify.app/#eNqNUs2O0zAQfpXBl2yr1mklBFKqhT1w4QTiul6kkEwigzs2toO66ubdmcTe0vK3e7Gsme9nPJ+PIvimxEO9dwZlDKISjaUQoQtwDR6/D9rjlRJdUGKxU9QFiQcdYuCaLDtr5VfurKAbqIna0tUCjuNiB2UJn9BZH7GdSC+ezXrfk/X4VpFYCQxGU5Q8UKd7pvBwej+JAtkWP5qh1wSdt3tQGbt2c3FNSvCwGRxDaiZoEe8dhsZrF9epXjBUER5mcItdPZgIt4oAjtMB0GmDoYLbYrksl3JZ3K1SPZlxJ+MAqDobLRXHDDY19UPd4wc3vfic5Gof0FenOWUqZB5Ab+yX2pwz4DGZCgqPdWvJ3BePzfHS1w/z8CduQSXZdYvOY1NzPOva6YJ10Hvrs8gswcfdjlNwdfON5+b9W+IEZiElpi0qUfFtb1u24DhTA4mfjhzvyVOJaScJ/Hn7Um5fyw08PMCb6+0ruZEbJWa7zG/xxzt0SC1So3/TuUkLKqffM6kZfkCI2Xo2n/v/bZ59kb+ibv74H2XK4/n4C6N/0H6xngRk2UtcTmgU40/nozeR

@JoshuaKGoldberg Do you have any information regarding this?

[JoshuaKGoldberg]

Yeah it'd be great to include support here! eslint/eslint#19173

ESLint core is making the rules listed in that issue aware of TypeScript syntax: meaning if the parser happens to create nodes that happen to match what @typescript-eslint/parser generates, they'll know what to do with them. The equivalent here would be properly handling those new TS* nodes and node properties in eslint-utils functions.

eslint/eslint#19493 is a good reference example for no-array-constructor. The only logical change to the rule was adding a check for node.typeArguments.

We should note that this is different from ESLint's core parser generating those TypeScript-specific nodes itself. ESLint still won't parse TypeScript syntax by default.

[github-actions]

🎉 This issue has been resolved in version 4.7.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀