Update: support bigint and dynamic import (refs #11803)#11983
Update: support bigint and dynamic import (refs #11803)#11983kaicataldo merged 13 commits intomasterfrom
Conversation
We can update |
|
What's the status of this PR? #11803 depends on it. |
|
Please track #11803. This PR is waiting on new |
|
A small fix for
There might be an issue with |
7240156 to
85a73d9
Compare
This avoids a dependency deduplication conflict for developers
kaicataldo
left a comment
There was a problem hiding this comment.
LGTM. Thanks @mysticatea and @platinumazure for working on this!
What is the purpose of this pull request? (put an "X" next to item)
[X] Add something to the core (#11803).
What changes did you make? (Give an overview)
This PR adds supports of bigint and dynamic import.
espreeandeslint-visitor-keys.CodePathAnalyzerto handleImportExpressionnode as throwable.new-caprule's false positive.astUtils.getPrecedencefunction to fixno-extra-parenfalse positive.astUtils.isNullLiteralfunction to fixeqeqeqfalse positive.func-call-spacingrule to recognizeImportExpressionnode.function-paren-newlinerule to recognizeImportExpressionnode.indentrule to recognizeImportExpressionnode.no-extra-parensrule to recognizeImportExpressionnode.env.es2020to declare new global variables:BigInt,BigInt64Array, andBigUint64Array.env.es2017to declare new global variables:AtomicsandSharedBufferArray. I'm not sure why we have not had it.(platinumazure: Consumed espree/eslint-visitor-keys, fixed merge conflicts, did some minor chores to get tests to pass-- see commit list.)
Is there anything you'd like reviewers to focus on?
There are a ton of remaining stuff (see #11803), but those are "enhancements which increase errors." As following our semver policy, we need a major update to add those... :(
Or maybe can we add those with a minor?