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 #269
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
…t-type Add flow-object-type rule
Add docs for flow-object-type rule
…r-arrow-parens Add an automated fix for arrow-parens
Add func-params-comma-dangle rule
* Update Dependencies fixes babel/eslint-plugin-babel#65 * Remove PhantomJS & is-my-json-valid PhantomJS & is-my-json-valid is not actually used anywhere * Change ESLint peerDependency version back to >=1.0.0
…valid-this Added `babel/no-invalid-this`
* Drop support Node < 4 * Add missing changes * Update `.travis.yml`
* Deprecate built-in rules * fix update to babel-eslint 7 with awaitexpression * deprecate flow-object-type
* Add semi from eslint * Add ClassProperty support to semi rule Fixes babel/eslint-plugin-babel#43
Deprecate rule `no-await-in-loop`
Refactor rules to use eslint-rule-composer
* chore: add test files # Conflicts: # packages/babel-node/package.json * fix: respect short flags when finding filename index * fix: use attributeName for kebab-case
* feat: add babel-preset-env to babel-standalone * chore: copy preset-env-standalone test * polish: tune warning message when babel-preset-env-standalone is loaded
Co-authored-by: Justin Ridgewell <[email protected]>
* fix: disallow private name in object member and TS type elements * chore: update test262 whitelist * chore: make flow happy * Update packages/babel-parser/src/parser/expression.js Co-Authored-By: Nicolò Ribaudo <[email protected]> * chore: update test fixtures * Update packages/babel-parser/src/parser/expression.js Co-Authored-By: Brian Ng <[email protected]> * chore: update test fixtures Co-authored-by: Nicolò Ribaudo <[email protected]> Co-authored-by: Brian Ng <[email protected]>
…10977) * Use @babel/eslint-parser for tests * Update rules/tests * Update docs * add @babel/eslint-shared-fixtures to package.json * remove bug fix * convert RuleTester to ESM * Update devDep versions
They are not published
* Remove syntax plugins enabled by default Moved to babel-archive: babel/babel-archive@8f23ddc - `@babel/plugin-syntax-async-generators` - `@babel/plugin-syntax-bigint` - `@babel/plugin-syntax-dynamic-import` - `@babel/plugin-syntax-json-strings` - `@babel/plugin-syntax-nullish-coalescing-operator` - `@babel/plugin-syntax-object-rest-spread` - `@babel/plugin-syntax-optional-catch-binding` - `@babel/plugin-syntax-optional-chaining` * Fix build script * Fix jest config * Remove archived plugins from tests
* refactor: replace refShorthandDefaultPos by refExpressionErrors * fix: duplicate __proto__ keys should be allowed in patterns * docs: add comments for ExpressionErrors.doubleProto [ci-skip] * test: add more test for coverage
* Added precedence for nullish-coalescing-operator * Made precedence equal to logical OR * Renamed the folders made for testing * Fixed the output test file of nullish-coalescing op
I really don't like this commit, but import() is currently breaking our publish script. When "normal" tests we are transpiling import() so that it works with Jest. We can't do it while publishing because we need to publish the untranspiled import() so that it can load real .mjs files. Follow up to #10903
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 : )