Please provide Windows binaries

[StoneCypher]

There's a whole lot of Windows developers out there who would love to use this too, and who will contribute based on it.

[basarat]

+1

[reflog]

+1

[Cellule]

+1

[romseguy]

+1

[joshy]

+1

[kolo]

+1

[alexeibs]

+1

[juanka881]

I need this! +1

[juliankrispel]

+1

[bakesteve]

@lefessan any chance of an updated build? really need to grab this commit if appveyor support is a possibility - that'd be ace!

[StoneCypher]

It would be great for an official build, because people like sindresorhus don't want to merge third party binaries (with good cause,) and are maintaining the binary packages that actually get invoked by the various toolchains out there.

An official build is meaningfully different than an identical third party build.

[mathieumg]

:+1: +1

[popopome]

+1

[vladimir-rovensky]

+1

[nadavov]

+1

[johnman]

+1

[StoneCypher]

So that's (counting +1 and :+1:) 32 so far.

Guess I'm gonna plus my own thing because I want to start a running tally by example.

+1 = 33.

[cskrov]

+1 (34)

[bakesteve]

+1 (35) ps if any of the flow folks fancy giving an update here, or a preference on people registering their interest (watch this PR, uservoice, etc) that'd be great.. unfortunately no experience at all in ocaml, so cant really offer up any help on a PR with code (rather than +1s) , but be more than happy to jump in and help where we can (testing, appveyor CI setup, etc)

[boschni]

+1 because our teams are working on mixed environments and we cannot afford to use unsupported tools.

[mgamperl]

+1 (37)

[malonecj]

+1 (38)

[Draggha]

+1 (39)

[nekitozzz]

+1 (40)

[dead-claudia]

Could this be fixed by using js_of_ocaml to port it to Node?

[maciek-codes]

+1 (41)

[Flaise]

As though the developers don't already know how much interest there is in Windows support: +1 (Meaning of life, the universe, and everything)

Just had to do it.

[StoneCypher]

@Flaise - amazingly, they don't.

[dead-claudia]

Um... They realize. It's just there are specific things extremely difficult to port IIRC, and it's not quite as high priority as fully addressing ES6 support, given projects like Cygwin. On Mar 23, 2015 2:42 PM, "John Haugeland" notifications@github.com wrote:

@Flaise https://github.com/Flaise - amazingly, they don't.

— Reply to this email directly or view it on GitHub https://github.com/facebook/flow/issues/6#issuecomment-85137536.

[xvik]

+1 (43)

[StoneCypher]

@impinball - a port is already present in this thread. All it needs is to be adopted.

[bakesteve]

Yep, we are using that already, and it works. But it is now significantly behind. Also having a non official build is meaningful (as mentioned above) ie for flow-bin on npm

[StoneCypher]

@spicyj You asked which thread. This one

[giltig]

+1 (44)

[Jaecen]

+1 (45)

[newtack]

+1 (46)

[AdriVanHoudt]

+1 (47)

[db]

+1 (48)

[seiyria]

+1

[n1ghtmare]

+1

[Cellule]

@lefessan would it be possible to share the work you've done to port flow back in November ? The version you made does work, but it is getting old now and it would be nice if others could contribute to the port.

[mohanr]

Is a WIndows binary available ? We have a big AngularJS application and developers are adding code too fast. My office machine is WIndows 7.

[StoneCypher]

@mohanr - not currently. That's why we're making a tally of how many people need it.

[Cellule]

@mohanr there was a port done back in November 2014. You can find it here http://www.ocamlpro.com/pub/ocpwin/flow-builds/ However, in my case, this is not an option because it's lacking features that were implemented in the master branch a few weeks after that.

[ranuser99]

+1

[jdaley]

+1 (51)

[smonev]

+1 (52)

[Ciantic]

+1 (53)

[PixnBits]

+1 (54)

[webuniverseio]

@lefessan, I'm also interested if it is possible to share the work you've done to port flow back in November? If community will get the idea where to start we can try to update flow ourselves. Thank you. cc @Cellule