BigInt support

[joshuajbouw]

Rule Suggestion

Is your rule for a general problem or is it specific to your development style?
It is a general problem for those that are using BigInt that is apart of official repos now.

What does your suggested rule do?
Ignores BigInt and "n" at the end of integers flagging that they are BigInt.

Here are some examples above.

List several examples where your rule could be used

const num = 10n
const num2 = BigInt(20)
const arr = new BigUint64Array(64)
const arr2 = new BigInt64Array(64)

Additional context
Now that TC-39 is out in V8, Node.js as well as JS, it would make sense to start supporting BigInt as it is officially accepted.

If there are any temporary solutions, I will be grateful.

[JoshuaKGoldberg]

Hi @joshuajbouw - what exactly is your issue? You haven't posted any rule names or error message. Is a TSLint rule flagging something as an error that shouldn't be?

[joshuajbouw]

Yeah, with BigInt, tslint doesn't know exactly what to do with them. So, it flags everything BigInt related. Everything does compile as-is correctly and it does run as intended.

[JoshuaKGoldberg]

it flags everything BigInt related

What error messages are you seeing?

[joshuajbouw]

I had updated the issue above with pictures showing the error messages.

[JoshuaKGoldberg]

Gotcha, the screenshots edited into your OP help. Thanks!

Your issue isn't with TSLint; it's with TypeScript. Out of the three:

• [tslint] Missing semicolon (semicolon): Not related to BigInt support. Check your tslint.json rule configurations.
• [ts] Cannot find name 'BigInt': This is coming to TypeScript in 3.2 according to Support for TC39 "BigInt: Arbitrary precision integers in JavaScript" proposal microsoft/TypeScript#15096 (whoo!). Until then you can try using the "typescript": "next" package in your package.json.
• [ts] Cannot find name 'BigInt64Array': Same as above.

If you have any other issues, you'll want to file them on the TypeScript repository.