Typescript 3.2 will contain support for BigInt and will be released this month (I assume probably during the next days?). BigInt was also enabled by default in Node v10.4. Are there any efforts or plans made to implement the BigInt type definitions for node 10 yet?
@SimonSchick @Flarna @rbuckton
Ehh, @andy-ms is BitInt contained in a lib? They really shouldn't be in node typings since they are also supported in browsers, and copy pasting definitions is always bad :)
It should be in --lib esnext already.
The question wasn't about typescript but about the node type definitions?
E.G. process.hrtime.bigint() and util.types.isBigInt64Array(value)
@lal12 thanks for clarifying, we will probably have to look into doing a split of typings for 3.x at that point in order to support it.
I will look into rolling node 11.x typings for ts 3.1 once it's out.
I think the most important point is to find a good way to split the node typings into a typescript 2.1 and 3.1 part without running into a sync/maintenance nightmare. I don't think that anyone would like to maintain two versions (incl. tests) of node type definitions.
On the one hand there are several hundred of packages depending on node typings working with 2.1 and on the other hand most maintainers of node type definitions would like to use newer typescript features.
I will look into rolling node 11.x typings for ts 3.1 once it's out.
I think backporting them would be important too, since node 10 will be LTS for quire a while.
I'm also in need for process.hrtime.bigint(): bigint. Can't people on 2.x simply use disableLibCheck?
This is also impossible to work around:

once #30477 is merged the infrastructure to use newer typescript features in node typings should be ready.
process.hrtime.bigint() should be covered by #33176
I see this issue has been closed but I do not see bigint types for e.g. fs.Stats.ino https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/node/v10/fs.d.ts which are documented as number | bigint in the docs https://nodejs.org/api/fs.html#fs_stats_ino
Might take a stab at this, can't make any promises atm.
@ttraenkler Could you create a PR? It's much better if people really using an APIs do the changes as they verify it in real apps instead of relying on docs/release notes.
@Flarna I will have a look and might create a PR for the fs module.
Should this issue be reopened? Looks like fs stats are still not updated.
@RReverser This has been implemented and various people including me are using this?
Can you perhaps be more specific what is supposedly missing?
Most helpful comment
This is also impossible to work around:
