-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
feat(es/parser): Support stripping flow with ES parser #9114
base: main
Are you sure you want to change the base?
Conversation
hello, last week I found out I can't switch to @swc/jest for a React Native project, where react-native and expo dependencies need to be transformed, because they include the Flow types. do you think this will be merged in the foreseeable future? thanks. |
BTW I found https://github.com/changwoolab/flow-aware-swc-jest and tried it but also got some error. just sharing for visibility/reference |
@kdy1 hi, any update on this effort? |
@rtrembecky Is there any concrete use plan? |
Ah you want to use swc/jest for a RN project |
well it's simple, our RN tests take too long to spin and one of the issues I identified is babel transpilation of RN modules, which are being shipped with Flow. I'd like to switch to a faster engine (SWC) but still support Flow-stripping. |
In Re.Pack 5 we're using It would be amazing to have a builtin support for doing this with |
|
CodSpeed Performance ReportMerging #9114 will improve performances by 3.43%Comparing Summary
Benchmarks breakdown
|
Description:
This PR adds support for flow syntax without a feature to construct AST. The parser strips out extra syntax, and the returned AST is identical to ECMAScript AST.