Build(deps): Bump flow-parser from 0.173.0 to 0.174.1

[dependabot]

Bumps flow-parser from 0.173.0 to 0.174.1.

Release notes

Sourced from flow-parser's releases.

v0.174.1

Fix crash when Flow receives duplicate file deletion notifications introduced in v0.174.

v0.174.0

Likely to cause new Flow errors:

• Flow now detects sketchy null errors that arise via optional chaining, and which involve opaque types, type aliases, or generics.
• Fixed an issue that caused us to previously miss some errors when the type involved was an intersection.

New Features:

• Access from a union of exact objects, on a property that is on one but not all of the objects, now results in the type of that property or void, instead of an error.
• Add type checking support for logical assignment operators.

Notable bug fixes:

• Fix a crash when using the default file watcher (dfind) on Windows if an [include] directory doesn't exist.
• Do not attempt to unify the type of a declare function that comes after a function declaration of the same name (try-Flow).
• Improve wording of class-extends errors (try-Flow).
• Don't report this-in-exported-function for functions with a this parameter.

Misc:

• Added --list-files flag to status and check commands. This will dump a list of files that contain errors instead of the error messages.
• The default file watcher (dfind) now logs to a .dfind_log file alongside the .log and .monitor_log files.
• Changed the way Flow computes coverage for type parameters with uncovered upper bounds. Previously, a type parameter was always considered covered when it appeared in a function signature, class declaration, or type alias, even if the type parameter's upper bound was any. With this change, such type parameters are now considered to be uncovered. This results in Flow now computing a lower coverage percentage on modules where this pattern is present or that import types from other modules that use this pattern.

Changelog

Sourced from flow-parser's changelog.

0.174.1

Fix crash when Flow receives duplicate file deletion notifications introduced in v0.174.

0.174.0

Likely to cause new Flow errors:

• Flow now detects sketchy null errors that arise via optional chaining, and which involve opaque types, type aliases, or generics.
• Fixed an issue that caused us to previously miss some errors when the type involved was an intersection.

New Features:

• Access from a union of exact objects, on a property that is on one but not all of the objects, now results in the type of that property or void, instead of an error.
• Add type checking support for logical assignment operators.

Notable bug fixes:

• Fix a crash when using the default file watcher (dfind) on Windows if an [include] directory doesn't exist.
• Do not attempt to unify the type of a declare function that comes after a function declaration of the same name (try-Flow).
• Improve wording of class-extends errors (try-Flow).
• Don't report this-in-exported-function for functions with a this parameter.

Misc:

• Added --list-files flag to status and check commands. This will dump a list of files that contain errors instead of the error messages.
• The default file watcher (dfind) now logs to a .dfind_log file alongside the .log and .monitor_log files.
• Changed the way Flow computes coverage for type parameters with uncovered upper bounds. Previously, a type parameter was always considered covered when it appeared in a function signature, class declaration, or type alias, even if the type parameter's upper bound was any. With this change, such type parameters are now considered to be uncovered. This results in Flow now computing a lower coverage percentage on modules where this pattern is present or that import types from other modules that use this pattern.

Commits

• af85b52 v0.174.1
• f92ff4a Fix calc_old_modules for files which never existed
• 6a07f4d v0.174.0
• 97c50d0 add --list-files
• 2580441 handle race when shutting down server
• 18e84fe fix uncaught dfind exception
• 01e0961 use lwt_ppx in dfind
• 01daabf log file watcher pid
• b19c2e0 [new-env] raise EInvalidDeclaration errors
• 051b2a8 [new-env] restore predicate function sanity check
• 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 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)

[fisker]

@dependabot squash and merge