Looking for maintainers

[charliedowler]

Hi Flow users,

I'm looking for a maintainer for this project, after a couple of years using Flow on side projects and maintaining (I use that word loosely) gulp-flowtype I've found myself struggling to keep it up to the standards I believe it should be.

I'm no longer actively using Flow and don't have the time to keep up with Flow's releases, let me know if you're interested in contributing/taking ownership of this project.

Cheers,
Charlie

[aikar]

@charliedowler

I think if you set flow as a peerdep instead of a dep that would help a lot, to not need to even update this much.

Can you least change it to a peerdep?

[bluepnume]

Second on that, having flow as a peer-dependency would be really helpful, until a new maintainer is found.

[aikar]

I did fork it for now to update this for anyone who needs:

aikar@64d8326

[charliedowler]

Hi people,

Would you be able to test master against a project you're currently running gulp-flowtype against. I've merged in @aikar's changes and will do a release very soon if I get the all clear.

Cheers,
Charlie

cc: @bluepnume

[fk-hb]

Hi,
I tested master with the peerDependency. I got UNMET PEER DEPENDENCY warning, but at least it worked.

[aikar]

@fk-hb yarn add flow to your project.

You have it in your folder from previous build, but if you wiped out node_modules, you would have a broken build.