Skip to content
This repository has been archived by the owner on Jul 16, 2019. It is now read-only.

flow-versions No suitable flow found on disk #79

Open
rssfrncs opened this issue May 23, 2018 · 4 comments
Open

flow-versions No suitable flow found on disk #79

rssfrncs opened this issue May 23, 2018 · 4 comments

Comments

@rssfrncs
Copy link

Running Windows 10, flow-for-vscode with flow.useLSP enabled.

Flow output results in "No suitable flow found on disk" and attempts to download from Github, which fails on my system but that is due to our corporate proxy.

The issue is why does it fail to find flow on disk when it is installed both locally and globally via Yarn?

@wchargin
Copy link

wchargin commented Jun 2, 2018

I was hitting the same error. I solved it by adding --try-flow-bin to
the language server invocation, which causes the language server to use
the locally installed version of Flow in the project’s node_modules
directory.

@jbachhardie
Copy link

I've looked into this a little bit and I think it's adm-zip introducing a bug in Windows in a recent version which makes the downloaded flow version fail to extract.

@kumarharsh
Copy link

See jbachhardie/vscode-flow-ls#3

@ArmorDarks
Copy link

This issue happens because on Windows it tries to write with the wrong path:

C:\Users\serjl\AppData\Roaming\Flow\bin\0.81.0\Users\serjl\AppData\Roaming\Flow\bin\0.81.0

Note the recurring path portion.

Related issue flow/flow-for-vscode#273

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants