flow · Issues· 516 open
Open on GitHubLocally synced open issues (discussions stay on GitHub)
- #9500
Memory leak
bugneeds triageUpdated Sep 17, 2026 - #9487
Configure auto import
discussionUpdated Aug 27, 2026 - #9346
Flow’s parser does not understand `export from` attributes (the `with { type: "json" }` syntax).
bugneeds triageUpdated Jun 30, 2026 - #9347
`flow-remove-types` throws a syntax error on ES `import` attributes
bugneeds triageUpdated Jun 29, 2026 - #9091
[Discussion]: Any plans to make Flow more interpopble with TS ecosystem?
discussionUpdated May 23, 2026 - #9065
☂️ Known unsoundness issues
Typing: soundnessUpdated May 23, 2026 - #7673
Cannot resolve JSON file starting with a dot
bugmodule resolutionHas PRgood first issueUpdated May 11, 2026 - #7427
If a `name_mapper` points to a non-existent file, it should tell user that the mapped path doesn't exist (instead of the original path)
enhancementmodule resolutionerror messagesgood first issueUpdated Mar 3, 2026 - #9344
Add a prefix to Flow specific AST node type
parsingUpdated Jan 23, 2026 - #9343
Rename `typeParameters` property to `typeArguments`
parsingUpdated Dec 24, 2025 - #8537
Inconsistent `Program.range` with other parsers
bugparsingneeds triageUpdated Nov 10, 2025 - #8062
Error message when trying to call a class as a function is confusing
error messagesdiscussionUpdated Sep 6, 2025 - #7918
[Summary] Flowtype / VSCode pain points and potential improvements
LSPdiscussionMeta IssueUpdated Aug 23, 2025 - #9305
Generic type is fully incompatible with conditional type
bugTyping: completenessUpdated Aug 11, 2025 - #9291
First always inferred as mixed in [infer First, ...infer Rest]
bugneeds triageUpdated Jun 12, 2025