VSCode highlights error but binary don't

[josemigallas]

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:

yarn flow spec/javascripts/Stats/applications_table.spec.js
yarn run v1.22.19
$ /Users/user/projects/3scale/porta/node_modules/.bin/flow spec/javascripts/Stats/applications_table.spec.js
No errors!

Here's the logs from the Output console:

[Info  - 12:01:07 PM - porta/.flowconfig] Found flow using option `pathToFlow`
[Info  - 12:01:10 PM - porta/.flowconfig] Using flow '/Users/user/projects/3scale/porta/node_modules/.bin/flow' (v0.152.0)

And here's my folder's config:

{
  "flow.useBundledFlow": false,
  "flow.useNPMPackagedFlow": false,
  "flow.pathToFlow": "${workspaceFolder}/node_modules/.bin/flow",
}

I can't reproduce it anymore, but at some point I managed to get this error in the Output console:

[Info  - 11:51:24 AM - porta/.flowconfig] restarting client
[Info  - 11:51:24 AM - porta/.flowconfig] Unable to verify SHASUM256.txt.sign:
ENOENT: no such file or directory, open '/Users/user/projects/3scale/porta/node_modules/flow-bin/SHASUM256.txt.sign'
[Info  - 11:51:24 AM - porta/.flowconfig] Found flow using option `useNPMPackagedFlow`
[Info  - 11:51:24 AM - porta/.flowconfig] Using flow '/Users/user/projects/3scale/porta/node_modules/flow-bin/flow-osx-v0.152.0/flow' (v0.152.0)
Flow: the running server is a newer version of Flow (0.183.0) than the LSP (0.152.0)LSP is exiting. Hopefully the IDE will start an LSP with the same binary as the server[Error - 11:51:33 AM] Connection to server got closed. Server will not be restarted.

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?

[mroch]

is the file saved? yarn flow checks what's on disk, but vscode checks the unsaved file as you type.

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]

I can confirm this issue but another case

• VScode doesn't highlight errors
• binary show many errors

Flow ver: 0.133
Flowtype extension: 2.2.0

  "flow.pathToFlow": "${workspaceFolder}/client/node_modules/.bin/flow",
  "flow.useBundledFlow": false,

I see errors in log with "flow.trace.server": "verbose" but error not highlighted in VScode

[mroch]

@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.

[romanlex]

@mroch I open new issues #446
and I think what problem really exists