[Question] Why is bigint literal rejected but seems well supported in caniuse?
See original GitHub issueI am testing code that uses bigint
literals like const a = 22n
. When testing using playwright, I get this error:
[WebServer] ✘ [ERROR] Big integer literals are not available in the configured target environment ("chrome87", "edge88", "es2020", "firefox78", "safari13" + 2 overrides)
Support for bigInt literals seems wide though (chrome87,edge88, es2020, firefox78), excepting Safari13.
Why is reporting error in all of them ?
Also just replacing by BigInt(a)
passes all, but I would prefer the n
literal.
Issue Analytics
- State:
- Created 10 months ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
"BigInt literals are not available when targeting lower than ...
the problem is bigint is a new feature. if you target an old version it won't be available. exactly like the error message...
Read more >Optional chaining (?.) - JavaScript - MDN Web Docs - Mozilla
If the object accessed or function called is undefined or null , it returns undefined instead of throwing an error.
Read more >Spring Data Neo4j
Neo4j supports defining properties not only on nodes but also on relationships. To express those properties in the model SDN provides @ ...
Read more >Sitemap - Sciter
Question about script optimizations in Sciter · Sciter with Skia/OpenGL on MacOS · Lightweight inline vector images in Sciter.
Read more >MySQL Connector/J 8.0 Developer Guide
MySQL Connector/J. Connector/J implements the Java Database Connectivity (JDBC) API, as well as a number of value-adding extensions of it. It also supports...
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
@santimirandarp What is your
@playwright/test
version? I also seeviteConfig
that is not supported in Playwright, could it be the problem?I pasted your config, commented out
viteConfig
and ran the following test:Everything passed for me:
Could you please share a full repro so that we can debug locally?
Closing as part of the triage process since it seemed stale or did not get enough upvotes in the past. Please create a new issue with a detailed reproducible or feature request if you still face issues.