Likely to cause new Flow errors:
- Imports of
reactmodule will always resolve to Flow's builtin react type definitions. If you use a custom react typing module, you might see errors.
Notable bug fixes:
- Preserve Flow WASM linker settings, including memory growth.
- Correct parser ranges for
unique symboltypes and signed mapped-property variance.
Parser:
- Rename the
ImportTypeESTree field fromargumenttosource. - Preserve computed object type property keys in parser output.
Library Definitions:
- Flow will now include DOM typing from TypeScript's
lib.dom.d.tsby default. If your project is not supposed to run in the browser, you can switch back to the old behavior withbuiltin_lib=core-onlyin flowconfig's[options]section. - Flow's
IterableandArrayLiketype now align with those from TypeScript. You might see errors when your existing code assumes the old typing.