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
Version 2.13.0 #3486
Version 2.13.0 #3486
Conversation
I've updated the description with a list of ES2020 features that are relevant for JSHint. |
We published the project license change using version 2.12.0, so I'm updating this pull request to describe 2.13.0 instead. |
836df69
to
8763239
Compare
Rebased on top of the |
dc00db3
to
f5b0971
Compare
This commit extends the options parsing system to tolerate the values "11" and "2020" for the `esversion` linting option. It does not introduce support for any features introduced by the new edition of the language.
No call site for `propertyName` specifies an object value for the second argument. The `optionalidentifier` function returns only string values or undefined. These two invariants make the untested code paths unreachable. Remove them both.
In so-called "object short notation," an IdentifierName is interpreted as both a LiteralPropertyName and an IdentifierReference. The second is a more restrictive goal than the first, so it is not necessary to apply the LiteralPropertyName validation rules. Removing that validation logic allows for an otherwise-unused parameter of the internal `propertyName` function to be removed.
Extend consideration to include bindings created using DestructuringBindingPattern.
Currently, the `setExported` method only makes the specified binding as "used." This is unnecessary in this context because when `expression` processes an IdentifierReference, it does the same. Remove the branch.
The situation described by this condition does not constitute syntactically invalid code, so it should be reported with a warning.
Add an internal test so the coverage analysis tool recognizes that the modified branch is verified.
Tolerate parsing errors regarding escape sequences in IdentifierNames as these reflect a pre-existing deficiency which will require a dedicated patch to correct.
We've landed a bunch of bug fixes to the I've pushed the prior version of this branch to my fork of the repository in case that's helpful. |
Any ETA? What's on the TODO list other than |
@jugglinmike With dynamic import PR #3540 merged, is this ready to go out of draft now? |
@almercier Yes! @rwaldron You've already reviewed everything in this branch, so no further action required here. That said, it would be nice to get gh-3541 in for the next release. Would you mind taking a look at that? |
I'm very much looking forward to see this available in my development environment. Will this be approved and merged anytime soon, so as to make it into the next tagged version? |
@jugglinmike @rwaldron It's been about a month since any update on this, do you have an estimated timeline on when this could be released? |
This is a tracking branch for the next minor release of JSHint. If you'd like
to implement a new feature, this is the place to submit it!
ES2020 features:
import.meta
globalThis
export * as ns from "mod"