React-Native - No identifers allowed directly after numeric literal
See original GitHub issueI’ve upgraded api, util, util-crypto and wasm-crypto, and made sure I import the relevant package at the top level as per the release note. And I get this runtime error that we’ve had in the past with BigInt linked: https://github.com/polkadot-js/common/issues/1253 and https://github.com/polkadot-js/common/issues/1245
I’ve been looking in the generated bundle for[0-9]_ or [0-9]n but didn’t find anything worrying. I’m looking more generally now, but the search has several thousand match.
One syntax I came across that could be problematic is 2e3 here for instance
function b() {
setTimeout(function () {
return e(t);
}, 2e3);
I’ll keep searching. And as usual with RN, no stack trace 🙄 my versions:
"@polkadot/api": "^7.13.1",
"@polkadot/reactnative-identicon": "^1.3.1",
"@polkadot/util": "8.6.1",
"@polkadot/util-crypto": "8.6.1",
"@polkadot/wasm-crypto": "^5.0.1",
Issue Analytics
- State:
- Created a year ago
- Comments:30 (29 by maintainers)
Top Results From Across the Web
React Native bug - No identifiers allowed directly after numeric ...
Your code is not valid because 12_200_000 is not a valid number and not defined anywhere. So it needs to be a string...
Read more >[0.65.0] no identifiers allowed directly after numeric literal
I simply upgraded from react-native 0.64.2 to 0.65.0 , hermes-engine from 0.7.2 to 0.8.1 and suddenly got the error ...
Read more >SyntaxError: identifier starts immediately after numeric literal
The JavaScript exception "identifier starts immediately after numeric literal" occurs when an identifier started with a digit. Identifiers can only start ...
Read more >No identifiers allowed directly after numeric literal #222
In Simple Words: It gives error 'No identifiers allowed directly after numeric literal' when use Lighten in React Native, have a look below:...
Read more >SyntaxError: Identifier directly after number in JavaScript
The JavaScript error "Identifier directly after number" occurs when a variable starts with a digit or we try to call a method directly...
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 Free
Top 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
So I guess the only thing that is left is the identicon? (No,
colorwas not upgraded there…)Can you do a small test with just
const a = 2e3; console.log(a)before we assume it is certainly that issue?