chore(deps): bump flow-parser from 0.254.2 to 0.257.1 in /dev-client

[dependabot]

Bumps flow-parser from 0.254.2 to 0.257.1.

Release notes

Sourced from flow-parser's releases.

v0.257.1

Misc:

• Flow language server will stop advertising that we can handle all code actions kinds prefixed with "source". It can help to prevent VSCode sending flow irrelevant code actions to handle during save.

v0.257.0

Likely to cause new Flow errors:

• We have improved inference for exported primitive literal values.
  • Before this change the inferred type for export const obj = {f: "foo"}; was {f: str<"foo">}, where str<"foo"> was a type that opportunistically and unsoundly behaved either as string or as the singleton type "foo".
  • Flow will now infer the type {f: string} for obj.
  • For const like exports, e.g. export const x = "foo"; Flow will export the type "foo".
  • To fix errors that arise due to this change, you can provide annotations around exported literals or use the as const modifier.
• We fixed a major unsoundness with regards to dictionary object creation. Previously, the computed property will just be ignored for string or any keys. Now, if the computed property is added to some existing objects (e.g. {foo: string, [stringTypedKey]: v}), then we will error on the property. Otherwise, the {[key]: value} will be {[typeof key}: typeof value}
• We fixed a bug that causes opaque type's underlying representation to leak beyond the file it's defined. You might see more errors as a result.
• Flow will now perform a complete function call check even when [react-rule-unsafe-mutation] errors are raised.
• Previously we incorrectly distribute-over-union for maybe or optional input types of conditional type. (e.g. (?string) extends string ? true : false is evaluated to true | false instead of false). This is now fixed, and code that depends on the bug might have new errors.
• If you have refiend a value based on typeof x === 'function', and then do typeof x === 'object', the result is now empty as that is impossible.
• Singleton types are now also considered in conditional equality checks on member expressions. (e.g. try-Flow)
• React.Config type, deprecated in v0.254, is now removed.

New Features:

• 'key' in x now refines the type of x to objects which have the property key.
  • in checks for both own and non-own properties.
  • If we find that a key does not exist in an inexact object or instance/interface, then the negation is not refined since the property may or may not exist.
  • An optional property is also considered as if it may or may not exist.
  • If a proto/super is a union, every member of the union must have it
  • If the input to the refinement is an intersection, one member of that intersection must have it
  • We don't refine arrays since it's not useful (check for .length instead), and also because Flow doesn't handle array holes.
• Flow now supports no_unchecked_indexed_access=true in flowconfig, which is equivalent to noUncheckedIndexedAccess from TS. It will add | void to every indexed access with general string key on dictionary objects or number key on arrays.
• Support for React 19's ref-as-prop model is now available via react.ref_as_prop=partial_support, and this is now the default. (To disable it, use react.ref_as_prop=disabled.) Under this mode, ref prop in jsx will be treated as a regular prop for function components, but utility types like React.ElementConfig<...> still won't include the regular ref prop yet.
• Flow now allows using union of strings as the type of computed property keys.
• You can now destructure object properties using number literal keys (which are int-like).

Notable bug fixes:

• Refining type guards with opaque types will now refine the general type (example of code that used to fail before, but now passes: try-Flow)
• Allow more flexibility in checks involving super type of opaque type (e.g. try-Flow)
• Fixed a bug when using opaque types in type guards in files other than the one where the type guard function was defined.
• We now allow a union of generic or opaque string typed values to be used as a key of computed property, if it's bounded by a string type.

Library Definitions:

• Add libdef types for getNotifications and showNotification API for ServiceWorkerRegistration

v0.256.0

Notable bug fixes:

• Fixed a limitation when checking intersections of polymorphic types (e.g. tryFlow)
• Fixed an internal error raised when using super in an object method. Such cases are now user-facing errors.

v0.255.0

Likely to cause new Flow errors:

• Referencing a react-component typed value in type position will now create a React$RendersExactly<typeof Component> type instead of React$Element<typeof Component> type. All existing usages intended to create an exact react element will now error as a result. Using it as type passed to render type, React.PropsOf, React.PropOf and React.RefOf is unaffected and will not be affected in the future. If you want exact react elements, the only way that doesn't trigger Flow error is by ExactReactElement_DEPRECATED<typeof Component>.

... (truncated)

Changelog

Sourced from flow-parser's changelog.

0.257.1

Misc:

• Flow language server will stop advertising that we can handle all code actions kinds prefixed with "source". It can help to prevent VSCode sending flow irrelevant code actions to handle during save.

0.257.0

Likely to cause new Flow errors:

• We have improved inference for exported primitive literal values.
  • Before this change the inferred type for export const obj = {f: "foo"}; was {f: str<"foo">}, where str<"foo"> was a type that opportunistically and unsoundly behaved either as string or as the singleton type "foo".
  • Flow will now infer the type {f: string} for obj.
  • For const like exports, e.g. export const x = "foo"; Flow will export the type "foo".
  • To fix errors that arise due to this change, you can provide annotations around exported literals or use the as const modifier.
• We fixed a major unsoundness with regards to dictionary object creation. Previously, the computed property will just be ignored for string or any keys. Now, if the computed property is added to some existing objects (e.g. {foo: string, [stringTypedKey]: v}), then we will error on the property. Otherwise, the {[key]: value} will be {[typeof key}: typeof value}
• We fixed a bug that causes opaque type's underlying representation to leak beyond the file it's defined. You might see more errors as a result.
• Flow will now perform a complete function call check even when [react-rule-unsafe-mutation] errors are raised.
• Previously we incorrectly distribute-over-union for maybe or optional input types of conditional type. (e.g. (?string) extends string ? true : false is evaluated to true | false instead of false). This is now fixed, and code that depends on the bug might have new errors.
• If you have refiend a value based on typeof x === 'function', and then do typeof x === 'object', the result is now empty as that is impossible.
• Singleton types are now also considered in conditional equality checks on member expressions. (e.g. try-Flow)
• React.Config type, deprecated in v0.254, is now removed.

New Features:

• 'key' in x now refines the type of x to objects which have the property key.
  • in checks for both own and non-own properties.
  • If we find that a key does not exist in an inexact object or instance/interface, then the negation is not refined since the property may or may not exist.
  • An optional property is also considered as if it may or may not exist.
  • If a proto/super is a union, every member of the union must have it
  • If the input to the refinement is an intersection, one member of that intersection must have it
  • We don't refine arrays since it's not useful (check for .length instead), and also because Flow doesn't handle array holes.
• Flow now supports no_unchecked_indexed_access=true in flowconfig, which is equivalent to noUncheckedIndexedAccess from TS. It will add | void to every indexed access with general string key on dictionary objects or number key on arrays.
• Support for React 19's ref-as-prop model is now available via react.ref_as_prop=partial_support, and this is now the default. (To disable it, use react.ref_as_prop=disabled.) Under this mode, ref prop in jsx will be treated as a regular prop for function components, but utility types like React.ElementConfig<...> still won't include the regular ref prop yet.
• Flow now allows using union of strings as the type of computed property keys.
• You can now destructure object properties using number literal keys (which are int-like).

Notable bug fixes:

• Refining type guards with opaque types will now refine the general type (example of code that used to fail before, but now passes: try-Flow)
• Allow more flexibility in checks involving super type of opaque type (e.g. try-Flow)
• Fixed a bug when using opaque types in type guards in files other than the one where the type guard function was defined.
• We now allow a union of generic or opaque string typed values to be used as a key of computed property, if it's bounded by a string type.

Library Definitions:

• Add libdef types for getNotifications and showNotification API for ServiceWorkerRegistration

0.256.0

Notable bug fixes:

• Fixed a limitation when checking intersections of polymorphic types (e.g. tryFlow)
• Fixed an internal error raised when using super in an object method. Such cases are now user-facing errors.

0.255.0

... (truncated)

Commits

• a10f3f9 v0.257.1
• 83ff18e [flow][match] Error on as patterns directly on binding patterns
• fd84ce5 [flow][match] Error (for now) on new bindings in 'or' patterns
• f858f40 [flow] Stop including source as supported code actions
• 9773592 [flow][test] Use a more realistic default codeActionLiteralSupport kinds
• 186aa6d [flow][match] Tests for error on duplicate binding name
• f4f5e1e [flow][match] Error on repeated object keys in object patterns
• 82c1fa3 [flow][match] Error on unary pattern + on bigint literal
• 67befeb [flow][match] Error on invalid unary pattern on 0
• ea7dadd [flow][match] Error on invalid numeric object property literals
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)