-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Issues: facebook/flow
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
[WIP] Builtin declaration merging
CLA Signed
declarations
Issues with library definitions or .js.flow features
Experiment
#7919
opened Jul 11, 2019 by
goodmind
Loading…
Non-exported, module-scoped values in a library definition are still importable
declarations
Issues with library definitions or .js.flow features
#6982
opened Oct 10, 2018 by
talbenari1
LibDefs dont listen to [ignore] -
declarations
Issues with library definitions or .js.flow features
#6663
opened Jul 30, 2018 by
bradennapier
Types imported into files that globally declare fail silently when not imported elsewhere.
declarations
Issues with library definitions or .js.flow features
#5807
opened Feb 13, 2018 by
hally9k
Symlinked library's .js.flow files are ignored
declarations
Issues with library definitions or .js.flow features
#5736
opened Jan 30, 2018 by
popham
flow floods Issues with library definitions or .js.flow features
/tmp
with flowlib_xxx
directories.
bug
declarations
#5349
opened Nov 16, 2017 by
Parakleta
Support flow-typed directories in yarn workspaces
declarations
Issues with library definitions or .js.flow features
module resolution
#5183
opened Oct 25, 2017 by
k15a
Module declaration wildcards
declarations
Issues with library definitions or .js.flow features
feature request
#5101
opened Oct 13, 2017 by
wbobeirne
No way to support multiple versions of flow in .js.flow files published with a package
declarations
Issues with library definitions or .js.flow features
#4846
opened Sep 10, 2017 by
jedwards1211
module.name_mapper doesn't work when pointing to a file within flow-typed
declarations
Issues with library definitions or .js.flow features
module resolution
#4481
opened Jul 28, 2017 by
bjohn465
Question: conventions for vendor libs
declarations
Issues with library definitions or .js.flow features
question
#3671
opened Apr 6, 2017 by
zs-zs
[libdef] declare module auto-export is too much magic
declarations
Issues with library definitions or .js.flow features
#3119
opened Jan 2, 2017 by
ryyppy
Flow declarations requires server restart to fix library parse errors
declarations
Issues with library definitions or .js.flow features
#2789
opened Nov 11, 2016 by
reaperdtme
Type check class that extends class from build in module
declarations
Issues with library definitions or .js.flow features
#2753
opened Nov 4, 2016 by
pitrew
intersection types and possibly undefined errors causing additional, invalid missing prop errors
bug
declarations
Issues with library definitions or .js.flow features
#2180
opened Aug 2, 2016 by
jedwards1211
Best Practices for 3rd party authoring
declarations
Issues with library definitions or .js.flow features
question
#2108
opened Jul 20, 2016 by
dozoisch
Extending EventEmitter stops module class from checking
declarations
Issues with library definitions or .js.flow features
feature request
#2102
opened Jul 20, 2016 by
karelbilek
No simple way to author and share flow packages.
declarations
Issues with library definitions or .js.flow features
feature request
#1996
opened Jun 23, 2016 by
Gozala
ProTip!
Add no:assignee to see everything that’s not assigned.