Releases: facebook/flow
Releases · facebook/flow
v0.214.0
Likely to cause new Flow errors:
- Flow now has stricter behavior with
$Call
,$ObjMap
,$ObjMapi
,$ObjMapConst
,$TupleMap
. Previously hidden type errors might be revealed now. - You can no longer disable
tuple_ehancements
,conditional_type
,mapped_type
,type_guards
in flowconfig, since these options have been removed. They were enabled by default since v0.212.0.
IDE:
- We now provide a new refactor that extracts JSX elements into a new React component.
- Extract to constant refactors now works for nested JSX elements and fragments.
Notable bug fixes:
- Added default type arguments for the built-in
React$AbstractComponent
to match theReact.AbstractComponent
type alias in our libdefs. [try-flow]
Library Definitions:
- Added
parseArgs
to the Node.jsutil
module library definition
v0.213.1
Notable bug fixes:
- Fixed a bug where local find references do not return references in jsx props.
v0.213.0
Likely to cause new Flow errors:
- Builtin idx support is removed. idx functions can now be typed with conditional type and mapped type. The v3 release of idx contains these typing changes.
- When using
module.system=haste
, it will now be an error if a.js.flow
file shadows a.js
file with a different path prefix.
Notable bug fixes:
- Fixed a bug that used to cause spurious internal errors when you have non-binding patterns. example
Parser:
- Fixed parsing of multiple
as
/satisfies
casts in a row.
Library Definitions:
- Added support for
Intl.Locale
class
v0.212.0
Likely to cause new Flow errors:
- Flow is now stricter with regards to type checking of spreads,
$NonMaybeType
, and$ReadOnly
. You might see new errors revealed as a result. - Experimental utility types
$Pred
and$Refine
have been deleted. These are replaced by type guards.
New Features:
- Updated
Pick
andOmit
to work on interfaces and instances. - Conditional types, mapped types, type guards, and tuple enhancements are now enabled by default.
Notable bug fixes:
- Prevented hover and go-to-definition requests that infinitely loop.
IDE:
- For imported names using
require
, go-to-definition will now jump to the location of the original definition's name.
v0.211.1
Notable bug fixes:
- Improve fuzzy matching of autoimports
v0.211.0
Likely to cause new Flow errors:
- We fixed an issue where the intersection of two identical object types are turned into empty in spreads. As a result, more errors might be revealed. example
Notable bug fixes:
- We fixed an eager evaluation bug that can lead to some bad interactions between conditional type and mapped type. (example)
Parser:
- We fixed the parser size regression since 0.210.0.
Library Definitions:
- We rewrote the
Omit
type implementation. Now it will preserve the optionality and the variance of the input object. example
v0.210.2
Notable bug fixes:
- Fix a bug where autocompleting a keyword deleted the next 7 characters on the same line
- "Fix" sorting of autoimports. An experimental option (
autoimports_ranked_by_usage=true
) to sort autoimports by how often they are imported was influencing the sorting even when the option was not enabled. This was likely an improvement, but it was a bug to not obey the option.
v0.210.1
Misc:
- Improvements in preparation of new feature rollout
v0.210.0
Likely to cause new Flow errors:
- We further strictified React.Element and React refs related typing. You might also see some existing errors related to React.Element and React ref moved around. Example
New Features:
- Added Pick, Omit, and Record utility types. [try-flow]
Notable bug fixes:
- Fixed a bug where
void
would appear in autocomplete suggestions more than once
Misc:
- Improved keyword autocomplete ordering
Parser:
Library Definitions:
- Added missing CSSOM
replace
andreplaceSync
- Added
arrayBuffers
to Node libdefs forprocess.memoryUsage()
's return type
v0.209.1
Misc:
- Bug fixes in preparation of new feature rollout