-
Notifications
You must be signed in to change notification settings - Fork 481
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
Add support for Flow's IndexedAccessType
#478
Comments
Thanks @gkz for the update on master. I tried with this But now it's choking on: |
Thanks for the report. When people make changes to our AST output, sometimes If you want you can use yarn resolutions to resolve |
For reference to other potential FLow users: Yarn "resolutions": {
"**/ast-types": "npm:@gkz/ast-types",
"**/flow-parser": "0.152"
} Npm "overrides": {
"ast-types": "npm:@gkz/ast-types",
"flow-parser": "0.152"
}, Downside, |
Actual |
I tried removing the overrides and all the errors are back. So I guess the whole chain transitive is not up to date or fixed yet. |
Apologies for the tangent on a closed issue, but this is currently the highest relevant search result for |
Currently
[email protected]
choke on Flow's indexed access types.It should be "just" a matter of updating
recast
, which comes withast-types
.Support for
IndexedAccessType
was added as of[email protected]
.EDIT: as of today, both
[email protected]
and[email protected]
are not published on thelatest
tag, butnext
./cc @benjamn
The text was updated successfully, but these errors were encountered: