Release 4.0 #1838
Closed
Release 4.0 #1838
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
Fixes jquery#1554 Closes jquerygh-1557
When parsing `export default class`, treat it as a real class declaration and do not perform the two-step process (parse as a class expression and then mutate the node into a class declaration). Fixes jquery#1570 Closes jquerygh-1571
Various fixes necessary to satistify strict null checking: * Safeguard against possible null value * Initialize values before they are used * Annotate arrays because there is no type widening anymore Other TypeScript 2.0 features being utilized: * Use `readonly` property feature whenever appropriate * Remove unused local variables * Remove unused function parameters * Unify return paths Also, bump TypeScript formatter to the version that uses TypeScript 2. Fixes jquery#1569 Closes jquerygh-1572
`parse` is still supported but the use of it is discouraged. The consumer must choose between `parseScript` and `parseModule` to perform a syntactical analysis on a script or a module, respectively. Fixes jquery#1576 Closes jquerygh-1577
Instead of `Identifier`, use `IdentifierName` in `ExportSpecifier`. Fixes jquery#1578 Closes jquerygh-1580
This is for ESTree compatibility. Fixes jquery#1575 Closes jquerygh-1581
For every test case, the source type is indicated by the file name's suffix: .module.js indicates a module, otherwise it is a script. Fixes jquery#1593 Closes jquerygh-1594
* `async` for function declarations/expressions, methods, and arrow expressions * A new `await` expression Fixes jquery#1079 Closes jquerygh-1597
Fixes jquery#1605 Closes jquerygh-1607
The right place to do this is before parsing any statement list item, not just a specific, smaller set of statements. Fixes jquery#1596 Closes jquerygh-1609
Reentry to the JSX world means that the last lookahead token being collected needs to be excluded. Fixes jquery#1613 Closes jquerygh-1614
This fixes the problem with incorrect node type in the parameters (object expression vs object pattern, etc). Fix jquery#1751 Fix jquery#1748 Closes jquerygh-1753
This reverts commit 45a8626.
This fixes issues with redeyed, but unfortunately documentjs needs to be excluded (outdated, tests can't run with modern Node.js anymore). Closes jquerygh-1798
Only a real lexing should throw an exception for an unknown JSX token. This ensures that a non-empty expression container does not cause any problem. Fixes jquery#1786 Closes jquerygh-1816
Instead of trying to handle it by itself, the special lexer for JSX should simply defer to the vanilla lexer if it can't understand the upcoming token. Fix jquery#1815 Closes jquerygh-1820
This is also now enforced via TSLint's prefer-const (with TSLint dependency bumped to v5). Fix jquery#1817 Closes jquerygh-1823
Were specified as "token" and "comments" in the description of the parse method Closes jquerygh-1832
|
Please ignore this confusing commit view from GitHub interface, I had to reconstruct this special 4.0 branch because the master branch already contains some implementation of ES2018 support which we don't want to include in 4.0 (it's focused only ES2017). |
|
👍 Awesome! |
|
Merged! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 #1589 for the details.