Skip to content
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.

No linting or autocomplete happening #158

Open
krainboltgreene opened this issue Mar 11, 2017 · 8 comments
Open

No linting or autocomplete happening #158

krainboltgreene opened this issue Mar 11, 2017 · 8 comments

Comments

@krainboltgreene
Copy link

  • I have a .flowconfig:
[ignore]
.*/node_modules/.*
<PROJECT_ROOT>/transpiled/.*

[include]
./source/

[libs]
flow-typed

[options]
all=true
  • I have it pointing to my flow binary:
"linter-flow":
  enableAll: true
  executablePath: "./node_modules/.bin/flow"

However, I still can't get it to actually give me errors.

@Arcanemagus
Copy link
Member

Does it work if you specify the full path to flow? I'm not entirely sure relative paths like that will work.

@krainboltgreene
Copy link
Author

If a full path works it would be a non-starter for me since I don't do global installs :(

@KingScooty
Copy link

This isn't working for me either.

@AStaroverov
Copy link

and for me

@AStaroverov
Copy link

I try check work of this module for me and how i understand linter-flow correct work (provideLinter create correct messages), but i don`t see ui messages

@AStaroverov
Copy link

I have Linter version 2, but this package use spec for 1 version. Can this be a problem?

@hmeerlo
Copy link

hmeerlo commented May 16, 2017

Absolute path doesn't solve it for me. I was not very happy with Nuclide, so looking for an alternative.

@idan
Copy link

idan commented May 18, 2017

Following the suggestions in #67, had originally setup with ./node_modules/.bin/flow, I'm still getting errors from the linter, despite the binary definitely being present.

2017-05-18 at 15 26

Absolute path does make it work, but that isn't a real solution, since i don't have flow globally installed.

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

6 participants