This draft's references do not show that the subject
qualifies for a Wikipedia article. In summary, the draft needs multiple published sources that are:
in-depth (not just passing mentions about the subject)
Make sure you add references that meet these criteria before resubmitting. Learn about
mistakes to avoid when addressing this issue. If no additional references exist, the subject is not suitable for Wikipedia.
If you would like to continue working on the submission, click on the "Edit" tab at the top of the window.
If you have not resolved the issues listed above, your draft will be declined again and potentially deleted.
If you need extra help, please ask us a question at the AfC Help Desk or get live help from experienced editors.
Please do not remove reviewer comments or this notice until the submission is accepted.
Where to get help
If you need help editing or submitting your draft, please ask us a question at the AfC Help Desk or get live help from experienced editors. These venues are only for help with editing and the submission process, not to get reviews.
If you need feedback on your draft, or if the review is taking a lot of time, you can try asking for help on the
talk page of a
relevant WikiProject. Some WikiProjects are more active than others so a speedy reply is not guaranteed.
To improve your odds of a faster review, tag your draft with relevant
WikiProject tags using the button below. This will let reviewers know a new draft has been submitted in their area of interest. For instance, if you wrote about a female astronomer, you would want to add the Biography, Astronomy, and Women scientists tags.
Flow is a popular, open-source
type-checker for
Javascript code which is built and maintained by
Meta Platforms.[3][2][4][5] It is used as an alternative for
TypeScript and offers stricter analysis, but has a smaller ecosystem.[6] For a while,
React recommended Flow as the static type checker to use with JSX, although React no longer provides guidance regarding type-checking following the recent redesign of their website.[7] According to statistics provided by GitHub's dependency graph, Flow is depended on by over 170 thousand different repositories hosted on GitHub alone.[8] In comparison, TypeScript is used in over 15 million repositories.[9]
Features
It supports writing types for libraries in the .flow format, which is somewhat similar to the .d.ts format; however it uses Flow types rather than TypeScript types, which leads to some differences.[10] In addition, it supports checking the types of objects using exact object types, [11] which has been the default in Flow since v0.202.[12] One of TypeScript's major pain points is its lack of support of exact object types.
One of the major benefits of Flow is that it forces the use of explicit type annotations on a module level, which prevents mistakes when deciding
SemVer bumps. Additionally, while it is slower,[13][14][15] it is considerably more complete.
History
Flow was first announced in 2014, and open-sourced at that time.[3]
In February 2015, Flow introduced typecasting and added support for defining types meant to be used outside the current module.[16][17] In comparison, TypeScript added support for import type declarations in early 2020.[18]
Later in February 2015, Flow introduced Flow comments, which allows writing type annotations as comments rather than as a syntax extension.[19] They are now one of the most common usages of Flow; in comparison, TypeScript is far more commonly used with its syntax extension.
In 2020, a major rework of Flow's architecture was completed, offering up to 6 times faster type-checking.[21][22]
In 2021, Facebook announced that Flow would, going forward, be prioritizing internal users of Flow at Facebook, although it would remain open-source.[22][23]
In 2023, Flow announced that it had completed the transition to switch Exact Object Types on by default.[12]