-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Strip away flow types #1863
Comments
So I think we can just automatically detect flow and apply the babel plugin by looking at the first line as it should say: |
Another possible solution: If we can detect a module that contains flow types (in order to locally link it), wouldn't be less-workaroundish to make parcel apply the transform right away, exclusively against that module? |
Yeah I think that'll be the best approach @chiefGui , currently doing some research on flow to make sure the annotation on the first line is really required. So I don't make assumptions of a framework I've never used |
Also from the short period of time I've worked with Flow, I also do remember that I was required to annotate my files with Finally, seems like in the Typography's case, they're also consistently using This is just a support to help you on your research. |
🐛 bug report
Parcel is currently not able to consume flow typed modules
🎛 Configuration (.babelrc, package.json, cli command)
N/A
🤔 Expected Behavior
Flow types should be stripped (perhaps configurable through babel)
😯 Current Behavior
Flow types cause errors
💁 Possible Solution
.flow
and.js
files..flow
being the typed one and.js
being processed by babel to strip away the typings🔦 Context
Issue #1799
💻 Code Sample
cc @chiefGui
The text was updated successfully, but these errors were encountered: