v0.221.0

Compare Source

Likely to cause new Flow errors:

• Changed the signature of React.Fragment to only accept children and the key prop.
• Changed the signature of React.useRef to return an opaque type.
• Fixed a case where, in some cases, contextually-typed callbacks being passed as props would be typed as any rather than producing underconstrained-implicit-instantiation errors. This will result in new underconstrained errors, but removes a source of untracked unsoundness.
• Banned non-tuple arrays from being spread into tuple types. It previously resulted in any without error.

Notable bug fixes:

• Improved signature help support for optional chaining calls and intersection types. Now we will show all possible signature possibilities for overloaded functions.

Performance:

• Incremental error collation, which helps IDE performance when you have a lot of suppressed errors, is now the default.
• Optimized the way we generate global types for normal source files. You might see a reduction in checking times (3-9% as measured internally at Meta). (D510558 samzhou19815)
• Optimized the way we analyze syntactic environment required for type checking. On a large file like this, it improves the checking time from 4s to 2s. (D508506 samzhou19815)
• Optimized substitution performance when conditional type and mapped types are operating on large and deep objects.

Library Definitions:

• Updated IntersectionObserver types.
• IndexedDB transaction now allows consuming storeNames as DOMStringList.
• Added options to IndexedDB transaction.
• Added durability to IDBTransaction.

v0.220.1

Compare Source

Notable bug fixes:

• We will now provide auto type import for default-exported classes.
• We no longer suggest defined values when doing auto complete in object keys when we are under a type annotation.

v0.220.0

Compare Source

Likely to cause new Flow errors:

• Fixed an issue where access of optional tuple element was not considered | void
• We rewrote how we generate types for library definitions, which makes the validation of libdef files stricter. You might see more errors as a result of the stricter validation. e.g. all unbound names in libdef files will cause an error, instead of the first reference of the unbound name.

Notable bug fixes:

• Fixed a bug in "refactor to react component" code actions. Previously, it would incorrectly replace all jsx children with the newly refactored JSX elements
• Fixed signature help when the function called is typed as an alias (e.g. try-Flow)
• Fixed some spurious errors in generic calls when the solution involves unions (e.g. try-Flow)
• Fixed a bug that caused weird errors when you try to use indexed access in export positions. example

v0.219.5

Compare Source

Misc:

• Bug fixes in preparation of new feature rollout

v0.219.4

Compare Source

Misc:

• Bug fixes in preparation of new feature rollout

v0.219.3

Compare Source

Misc:

• Bug fixes in preparation of new feature rollout

v0.219.2

Compare Source

Misc:

• Bug fixes in preparation of new feature rollout

v0.219.0

Compare Source

Likely to cause new Flow errors:

• We changed the upper bound of React.Element to be an inexact empty object, effectively making it opaque.
  React doesn't recommend inspecting children and React.Element, so we make the change to increase friction. See https://react.dev/reference/react/Children#alternatives for alternatives.
  To keep existing code type safe, you can add a function like the following to explicitly expose the internal of React.Element:

export default function DangerouslyAccessReactElementInternals_DO_NOT_USE_IN_NEW_CODE<
  E: React$ElementType,
  P,
>(e: React$Element<E, P>): {
  +key: React$Key | null,
  +props: P,
  +ref: any,
  +type: C,
} {
  return e;
}

• Conditional types will now only distribute over a union if A in A extends B ? C : D is a generic type. This is a behavior change that might cause new errors (example). Previously, we distribute over unions in more cases, which contradicts what we said in the docs, and caused some weird behavior that's fixed in this version.
• If an exported class contains unannotated propTypes, Flow will now emit signature-verification-failure.

New Features:

• Hovering on enum members in IDE now show documentation if it's available.
• Added casting_syntax option which can be colon (current), as, or both. If setting is both, both (x: T) and x as T are allowed. If set to colon or as, only (x: T) and x as T are allowed respectively.

Notable bug fixes:

• Previously, when Flow cannot decide which branch to take in a generic conditional type, Flow will produce a abstract type that's unusable almost everywhere. Now Flow will still produce an abstract type, but it will be bounded above by a union type of both branches of conditional type. example.

Misc:

• Flow's insert type quickfix in IDE will stop inserting very specific React.Element types. Instead, it will insert general types like React.MixedElement.

Library Definitions:

• Add type definition for CanvasRenderingContext2D.roundRect.
• Add tagName to DOM element declarations (thanks @​aselbie).

v0.218.1

Compare Source

New Features:

• Error collation during rechecks should become faster thanks to incremental computation. (Available with the flag --incremental-error-collation.)

v0.218.0

Compare Source

Likely to cause new Flow errors:

• We start to validate variance inside $ReadOnly, which is previously completely unchecked. It also results in Flow complaining about some incorrect bounds. example

New Features:

• Hover types will now show a specialized version of the callee expression at a call to a generic or intersection-typed function.

Notable bug fixes:

• improve coverage accuracy for the element access portion on element calls, obj[m](arg).

Misc:

• We slightly optimized Flow's performance of subtyping check between two union types.

Library Definitions:

• Add defintions Array.prototype.findLastIndex(), String.prototype.at(), TypedArray.prototype.at() and Object.hasOwn() (thanks @​pascalduez).
• Update URL defintions (thanks @​pascalduez).
• Add typing for cause option in Error constructor.

v0.217.2

Compare Source

This is same as 0.217.1, but we have some issue publishing 0.217.1 to npm, so we will publish this new version instead.

v0.217.1

Compare Source

Notable bug fixes:

• Previously, while global find ref/rename (experimental.global_find_ref=true/experimental.global_rename=true) is ongoing, all other IDE services will be blocked. We fixed it so that other IDE requests can still be served.