Skip to content

Upgrade Flow to 0.329.0 - #3845

Open
mwiencek wants to merge 8 commits into
metabrainz:masterfrom
mwiencek:flow-0.329.0
Open

Upgrade Flow to 0.329.0#3845
mwiencek wants to merge 8 commits into
metabrainz:masterfrom
mwiencek:flow-0.329.0

Conversation

@mwiencek

Copy link
Copy Markdown
Member

Problem

Flow is outdated. I've been having issues with the previous version using up all of my system's memory and crashing.

Solution

Upgrades Flow to the latest version.

AI usage

None.

Testing

Just ./node_modules/.bin/flow.

https://github.com/facebook/flow/releases/tag/v0.329.0

The main breaking change affecting us is "Flow will error on legacy variance
syntax in library definition files."

The flow-typed/environment libdefs are not updated in flow-typed repository
yet, but there appear to be fixed copies maintained separately in the Flow
repository, which I've copied here:
https://github.com/facebook/flow/tree/main/evals/flow-typed/environment

These have a copyright header referencing a nonexistent LICENSE file which I'll
fix in the next commit.

The rest of the libdefs I updated by hand.
The files as synced from the flow-typed command did not contain any copyright
header. The ones I copied from
https://github.com/facebook/flow/tree/main/evals/flow-typed/environment in the
previous commit do. This adds their license to the same directory.
https://flow.org/en/docs/tools/eslint/ now recommends flow-eslint.

eslint-plugin-ft-flow requires hermes-eslint as a peer dependency, but this
only causes a warning when running `yarn`. The plugin itself seems to work
fine.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

1 participant