Flow-for-vscode: {"flow.useNPMPackagedFlow": true} broke everything in vscode 1.30

Created on 17 Dec 2018  路  10Comments  路  Source: flowtype/flow-for-vscode

It seems that with the last 1.30 november update of vscode, the flow extension is broken if you set the flow.useNPMPackagedFlow option to true.
Worked in 1.29.1 without trouble

MacOs Sierra.

Most helpful comment

I've reset settings to default and now it indeed works.

Here the output:

[2018-12-23T09:25:37.050Z] [INFO] flow - Path to Flow: d:\Work\Project\project.portal\node_modules\.bin\flow.cmd
Launching Flow server for d:\Work\Project\project.portal
Spawned flow server (pid=16676)
Logs will go to C:\Users\serjl\AppData\Local\Temp\flow\dzCzBWorkzBZelenkazBzZelenka.portal.log
Monitor logs will go to C:\Users\serjl\AppData\Local\Temp\flow\dzCzBWorkzBZelenkazBzZelenka.portal.monitor_log
[Info  - 11:26:05 AM] Starting Flow server

All 10 comments

This is likely fixed with 1.0 which came out today

As of vscode 1.30 I'm getting Output: Could not find a .flowconfig in rootPath in a project using subdirectories that was working prior to the update. My "flow.useNPMPackagedFlow" setting is set to false.

MacOs Mojave.

I wonder does 1.0 works for anyone at all? Windows 10, it does just nothing. Literally. Extensions do not start, no errors, no logs. Nothing.

Indeed, version 1.0 does not show types and does not flag errors while editing. I am using VSCode 1.30.1 in Linux. I had to install version v0.8.5.

FWIW, for me it works fine with flow.useNPMPackagedFlow.

macOS Mojave: 10.14.2
VS Code: 1.30.1
flow-for-vscode: 1.0.0

For me it partially works (https://github.com/flowtype/flow-for-vscode/issues/300) when flow.useNPMPackagedFlow _not_ used. With flow.useNPMPackagedFlow it even doesn't appear in Output panel. Windows 10

With flow.useNPMPackagedFlow it even doesn't appear in Output panel. Windows 10

@ArmorDarks share your vscode output (flow) logs with following settings

flow.useNPMPackagedFlow: true,
flow.pathToFlow: "flow",

Make sure you open javascript file to start plugin (otherwise flow will not show up in output panel dropdown).

@colinrcummings check this issue

I've reset settings to default and now it indeed works.

Here the output:

[2018-12-23T09:25:37.050Z] [INFO] flow - Path to Flow: d:\Work\Project\project.portal\node_modules\.bin\flow.cmd
Launching Flow server for d:\Work\Project\project.portal
Spawned flow server (pid=16676)
Logs will go to C:\Users\serjl\AppData\Local\Temp\flow\dzCzBWorkzBZelenkazBzZelenka.portal.log
Monitor logs will go to C:\Users\serjl\AppData\Local\Temp\flow\dzCzBWorkzBZelenkazBzZelenka.portal.monitor_log
[Info  - 11:26:05 AM] Starting Flow server

Try v1.1.0.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

thymikee picture thymikee  路  6Comments

sgronblo picture sgronblo  路  6Comments

rattrayalex-stripe picture rattrayalex-stripe  路  4Comments

yurtaev picture yurtaev  路  3Comments

booboothefool picture booboothefool  路  4Comments