Latest version of flow-typed cli can't run "flow-typed install"

Do you want to request a feature or report a bug? Bug

What is the current behavior? I’m currently running an older version of flow-typed and whenever I install a new dep I would run flow-typed install and it would update all my defs for me.

But for my colleagues who are just getting started with flow, who install the latest version of flow-typed aren’t able to run this command, they can run flow-typed install dep@version though. Below is a screen grab of errors they get

If the current behavior is a bug, please provide the steps to reproduce.

yarn global add flow-typed
# go into a project
flow-typed install

What is the expected behavior? It should scan package.json and install new/update lib defs

Local Environment Information

System:
  OS: macOS 11.1
  CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
  Memory: 378.20 MB / 16.00 GB
  Shell: 5.8 - /bin/zsh
 Binaries:
  Node: 14.15.1 - /usr/local/bin/node
  Yarn: 1.22.10 - /usr/local/bin/yarn
  npm: 6.14.10 - /usr/local/bin/npm
 Managers:
  Homebrew: 2.7.0 - /usr/local/bin/brew
  pip3: 19.2.3 - /usr/bin/pip3
  RubyGems: 3.0.3 - /usr/bin/gem
 Utilities:
  Make: 3.81 - /usr/bin/make
  GCC: 4.2.1 - /usr/bin/gcc
  Git: 2.23.0 - /usr/local/bin/git
  Clang: 1200.0.32.28 - /usr/bin/clang
 Servers:
  Apache: 2.4.46 - /usr/sbin/apachectl
 SDKs:
  iOS SDK:
   Platforms: iOS 14.3, DriverKit 20.2, macOS 11.1, tvOS 14.3, watchOS 7.2
 IDEs:
  Nano: 2.0.6 - /usr/bin/nano
  VSCode: 1.52.1 - /usr/local/bin/code
  Vim: 8.2 - /usr/bin/vim
  Xcode: 12.3/12C33 - /usr/bin/xcodebuild
 Languages:
  Bash: 3.2.57 - /bin/bash
  Java: 14.0.2 - /usr/bin/javac
  Perl: 5.28.2 - /usr/bin/perl
  PHP: 7.3.24 - /usr/bin/php
  Python: 2.7.16 - /usr/bin/python
  Python3: 3.8.2 - /usr/bin/python3
  Ruby: 2.6.3 - /usr/bin/ruby
 Databases:
  MongoDB: 4.4.0 - /usr/local/bin/mongo
  SQLite: 3.32.3 - /usr/bin/sqlite3
 Browsers:
  Chrome: 87.0.4280.88
  Safari: 14.0.2
 Monorepos:
  Yarn Workspaces: 1.22.10

[ticky]

I’m seeing this too, it seems to be related to having flow-bin in a package.json with a semver expression like this: ^0.100.0. If I change that to just 0.100.0 it works fine.

It also seems to happen on 3.2.0, so isn’t specifically the latest version’s problem. I haven’t had a chance to test more versions.

[Brianzchen]

Hi all, update that I’ve found the issue and created a PR. I will subsequently raise an issue with the semver project regarding patches breaking this project.