-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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 @flowtyped scope resolution before actual Node resolution #7758
Conversation
@nmote this doesn't actually work if this and [libs] .json fix both get merged, because @flowtyped is still using libdefs |
I tried to implement there this feature request #4917. Not sure how slower this makes dependency resolving, this basically reads package.json on every import |
@jedwards1211 I think you would be interested to check this out? |
Thanks, though I've never found time to learn much OCaml so it's hard for me to tell exactly what this is doing...what do you mean by versioned .js.flow? I didn't see anything in your proposal repo about it |
@jedwards1211 check tests in this PR, they're in JS. I still didn't updated proposal, because when I profiled this it increases time of dependency resolution significantly :\ |
https://github.com/facebook/flow/tree/d4176e0a9b0487bd1abee050d0db2fba94521bfd/tests/declaration_files_node_versions |
d4176e0
to
1ac6c8b
Compare
This pull request has been merged in 04467ee. |
Proof of concept for #7750
Issues
Depends on flow-typed NPM migration
Clashes with (in particular if there would be migration period from old libdefs to .js.flow)