New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VSCode highlights error but binary don't #442
Comments
is the file saved? as for why it tried to use 0.183: that's the version bundled with the extension. I'm guessing you hadn't run yarn yet, so node_modules/.bin/flow and node_modules/flow-bin/SHASUM256.txt didn't exist, so it fell back to the built-in version. since your pathToFlow is using the node module anyway, I'd suggest using useNPMPackagedFlow. |
@romanlex that sounds like a different issue, please open a new one. but 0.133 is two years old (54 versions behind) so we can't really support that anymore. |
I'm having a version conflict between VScode extension and npm package. An error is highlighted in the editor:
but it's not picked up by the binary:
Here's the logs from the Output console:
And here's my folder's config:
I can't reproduce it anymore, but at some point I managed to get this error in the Output console:
My guess is that VScode is using Flow (0.183.0) somehow, picking up the error, whereas running flow doesn't. Any ideas how to further debug this?
The text was updated successfully, but these errors were encountered: