forked from babel/babel
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[pull] master from babel:master #270
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
They are now alphabetically ordered, but the data is the same
Contributors |
* Fix plugin ordering in preset-env * Update stdout fixtures * Comments [skip ci]
…11021) * chore: pin yarn version in e2e vue tests * fix: replace yarn-upgrade by bump-babel-dependencies * chore: update e2e-cra test
* refactor: reimplement nullish coalescing precedence tracking Co-authored-by: Toru Nagashima <public@mysticatea.dev> * fix: Coalesce has same precedence with LogicalOR * fix flow errors Co-authored-by: Toru Nagashima <public@mysticatea.dev>
Introduce a `ImportAttribute` structure and add an `attributes` key on the `ImportDeclaration` node. [skip ci]
* Fix rest parameters indexing with TypeScript 'this parameter' The TypeScript [this parameter][0] is a fake parameter and should not be taken into account when counting the function parameters. This patch skips it by using the condition taken from the `transform-typescript` plugin. Note: since the `transform-typescript` plugin is removing this kind of parameter, including it before the `transform-parameters` plugin solves the issue. This patch fixes the issue in other cases. [0]: https://www.typescriptlang.org/docs/handbook/functions.html#this-parameters * nit: improve the 'this parameter' detection condition * improve performance by checking the parameter list length before accessing it * simplify the test a bit by using the `isIdentifier` second parameter
Fixes issue 10989 where the only the identifier in a member expression that is the value of an object property would be parsed. Removing checkExpressionErrors in parseExprSubscripts results in the subscript also being parsed.
* ignore compat-data build * ignore CONTRIBUTING.md when publishing preset-env * docs: update preset-env CONTRIBUTING.md
* Bug replication test * Simplify test * Fixes #10896 * Merge path.crawl `ClassDeclaration` and `Declaration` visitors Merged to avoid subtle assumption that `Declaration` is called before `ClassDeclaration` * Move registartion of class id in crawl to BlockScoped * Add some assertions to crawl test
…#11029) * fix(babel-parser): avoid state.clone() to clone the whole token store Fixed the performance issue on large input when turned on option {tokens: true} and typescript plugin which uses quite a few state.clone(). * test(babel-parser): turn on 2 typescript tests with tokens:true The output.json is generated by old master to make sure no regression. * fix(babel-parser): avoid duplicated tokens trapped by mainly typescript/flow plugins * test(babel-parser): update output.json to latest master result * chore(babel-parser): improve performance by storing tokensLength in state
* refactor: remove isBinding parameter * remove unused contextDescription * refactor: remove unnecessary nullish check * refactor: simplify toAssignable on ParenthesizedExpression * tests: categorize createParenthesizedExpression tests
* polish: throw human-friendly error when item-option pair is incorrectly unwrapped * add testcase for plugin * fix: exclude false positive * fix: validate should support plugin optionsSourceKind * Revert "fix: validate should support plugin optionsSourceKind" * fix: validate plugin object in assertNoUnwrappedItemOptionPairs * fix flow error * update test fixtures * refactor: move to loadDescriptor catch clause * chore: throw Error instead of builtin ReferenceError * fix flow errors * chore: add more test cases
* chore: map mobile browser data to their desktop version * chore: skip android until upstream support is resolved * Revert "chore: skip android until upstream support is resolved" This reverts commit 436e9af. * Update fixtures Co-authored-by: Nicolò Ribaudo <nicolo.ribaudo@gmail.com>
This file is the same as `native-modules.json`, which is exported in package.json
* Avoid compiling the typeof helper with itself * Update fixtures
* Fix compat-data build script * Update compat table * Update mappings for transform-parameters compat-table/compat-table#1570 * Update unrelated fixture * Update
* chore: compact loc information in parser fixtures * chore: update test fixtures
* Ignore abstract methods when decorating class * Address Nico's feedback * Add input/output test * Update test output to account for _nonIterableRest changes
* Set correct async/generator in IIFE for params * Reject in async params * Skip async test on node 6 (it doesn't support async fns)
* Fix e2e publish test when branching from an older version * Fix * Fix * Fix
* Don't call `createSuper` in loose mode (it was unused) * Update fixtures
* Fix createSuper in Babel <7.5.5 In Babel <7.5.5, addHelper only throws when called for the first time. This was fixed by #10208, but since we are already adding a workaround for <7.9.0, we may as well fix <7.5.5 * Use 7.0.0 in "babel-old-version" test
…#11373) * Fixed useBuiltIns and modules validation when using 'false' as option * Added tests for 'validateUseBuiltInsOptions' and for 'validateModulesOption' when input is 'false' Co-authored-by: Jovica Markoski <jovica@upshiftwork.com>
* Don't check type annotations when deciding params scope * Also type params
bigInts are enabled by default
Berkmann18
approved these changes
Apr 7, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by pull[bot]. Want to support this open source service? Please star it : )