Cannot find name 'bigint'
See original GitHub issueType: Bug Version: 2.5.4 Subject: Type Error Environment: TypeScript 3.1.6
We are receiving the following error on build with the latest version (2.5.4).
ERROR in node_modules/idx/lib/idx.d.ts(52,21): error TS2304: Cannot find name 'bigint'.
node_modules/idx/lib/idx.d.ts(53,13): error TS2304: Cannot find name 'bigint'.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Using BigInt in TypeScript - Stack Overflow
I believe I should be able to use BigInt now in TypeScript...but changing some code base to use it and I get "Cannot...
Read more >TypeScript compiler cannot find name 'BigInt' #275 - GitHub
The BigInt type in the Stats.d.ts file causes TypeScript to throw a 2304 (cannot find name) error, so the compilation fails.
Read more >Unable to run ionic old project: Cannot find name 'bigint'
I am trying to run my old project to modification, I have successfully run npm install but unable to serve the app. It's...
Read more >Microsoft/TypeScript - Gitter
I believe I should be able to use BigInt now in TypeScript...but changing some code base to use and I get "Cannot find...
Read more >Unable to use BigInt in typescript version 3.4.5. Error TS2304 ...
[Solved]-Unable to use BigInt in typescript version 3.4.5. Error TS2304: Cannot find name 'BigInt'-angular.js ... I am able to resolve the error by...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I just published idx@2.5.5 which includes https://github.com/facebookincubator/idx/pull/80. Thanks everyone!
Hi @mohsen1 I got that already. I just wanted to make sure you are aware of the issue. After all, this is a breaking change for TypeScript users and the version number is increased just as if it is a patch. It will break compilations all over the world and people will have to take action.
If you want to fix this, you can publish a minor release (2.6.0) or, even better a major release (3.0.0), then revert the change and make another patch to the older version (2.5.5). Additionally, this should be documented well to avoid further misunderstandings.