flow-typed: "Invalid Version: undefined" semver on version 3.x flow-typed
Do you want to request a feature or report a bug? bug
What is the current behavior? after running yarn flow-typed install
UNCAUGHT ERROR: TypeError: Invalid Version: undefined
at new SemVer (/path/project/node_modules/flow-typed/node_modules/semver/classes/semver.js:22:13)
error Command failed with exit code 1.
If the current behavior is a bug, please provide the steps to reproduce.
- Install Fresh CRA
- install flow-bin flow-typed
- run yarn flow init
- run yarn flow-typed install
What is the expected behavior?
- should generate the flow-typed directory
If this is a feature request, what is motivation or use case for changing the behavior?
Local Environment Information
If this issue is specific to the CLI, provide the results of running npx envinfo from the command line in a GitHub gist.
kubuntu: 19.04 node: 10.18.1 flow-typed: 3.1.0 flow-bin: 0.122.0
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 30
- Comments: 21 (7 by maintainers)
Commits related to this issue
- Use yarn resolutions to upgrade flow-typed see this issue for why https://github.com/flow-typed/flow-typed/issues/3809#issuecomment-625591194 — committed to careerfairsystems/nexpo-web by adriangoransson 4 years ago
- 依存関係の更新 flow-typed install が error になるのを修正 https://github.com/flow-typed/flow-typed/issues/3809#issuecomment-664853465 — committed to kkeisuke/plantuml-editor by kkeisuke 4 years ago
- Catching up to master Squashed commit of the following: commit 5cb3f48b50ba142dab07ff8d3533dcc668382109 Merge: 09e5b6a e3bb793 Author: alangibson <alan.gibson@gmail.com> Date: Sat Oct 30 13:07:15 ... — committed to alangibson/powerplantuml by alangibson 3 years ago
You can also pin using yarn resolutions in package.json.
https://classic.yarnpkg.com/en/docs/selective-version-resolutions/#toc-how-to-use-it
This is almost certainly due to this bug.
I’m still seeing the same error with
v3.2.0So far I’ve seen downgrading flow-typed (if one can) to v2.6.2 which uses an earlier major semver version, or manually pinning semver to a known good version in
yarn.locksuch as:Should be fixed as of
v3.2.1Please comment if not.
Is there an alternative workaround for those who don’t use yarn?
It looks like the “bug” from semver isn’t going to be fixed.
how do you run “flow-typed install” it still gives me the error
Also running into this and is a blocker for me upgrading from v2 -> v3 of flow-typed
Should be fixed as of
v3.2.0Please comment if not.