Eslint reports stream types as syntax error

Question

In cases where I use a stream. https://flowtype.org/

// @flow
var foo = (str: string) => {
  return str;
};

and Eslint together, Eslint reports an unexpected token on str: string.

Is there a way to force Eslint to ignore (or recognize) stream types and not report errors?

Answer 1

As Hamlet mentioned, there is eslint-plugin-flowtype that will do a few things:

• Add syntax support for the stream (and future JavaScript syntax) via babel-eslint
• eslint

docs.