Skip to content
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

Feature Request: Make parsing failures more verbose #52

Open
lmosele opened this issue Jul 6, 2022 · 1 comment
Open

Feature Request: Make parsing failures more verbose #52

lmosele opened this issue Jul 6, 2022 · 1 comment

Comments

@lmosele
Copy link

lmosele commented Jul 6, 2022

console.error(`Failed to parse: ${filePath}`);

I'm currently operating within a React/Flow codebase and am finding that everything is awesome aside from a miscelleanous series of components fail to be parsed entirely. It's not clear as to why since the error itself isnt surfaced, but I suspect it either trips up on the flow types of any extra exports within the file?

If possible I'd love to see a few more config options that specify pre-parsing rules (ie maybe a regex exclude?). Not entirely sure what the best move would be, but open to helping out if necessary!

@moroshko
Copy link
Owner

moroshko commented Jul 6, 2022

Flow is not supported at the moment (we only have TypeScript support).
PR is welcome!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants