Flowtype 0.30 adds support for Windows
flowtype.org
Flowtype 0.30 adds support for Windows
1–10 of 18 posts
Re: Flowtype 0.30 adds support for Windows
#2Hi HN, just wanted to let you know that the Flow team is watching this thread and is happy to respond to any questions that you have :)
Re: Flowtype 0.30 adds support for Windows
#3Hi HN, just wanted to let you know that the Flow team is watching this thread and is happy to respond to any questions that you have :)
Any update on support for using TypeScript definition files with Flow? It doesn't seem as though the team is still watching the issue on Github: https://github.com/facebook/flow/issues/7
Re: Flowtype 0.30 adds support for Windows
#4Hi HN, just wanted to let you know that the Flow team is watching this thread and is happy to respond to any questions that you have :)
Any update on support for using TypeScript definition files with Flow? It doesn't seem as though the team is still watching the issue on Github: https://github.com/facebook/flow/issues/7
We've actually been discussing going the other way with a conversion tool for package publishers. Flow has a more sound type system and it's easier to downgrade than upgrade.
The next few months should hopefully start seeing a lot of new tools for managing and publishing types within the community. It would be great to see more adoption from package owners themselves.
Re: Flowtype 0.30 adds support for Windows
#5Earlier quoted context omitted.
Any update on support for using TypeScript definition files with Flow? It doesn't seem as though the team is still watching the issue on Github: https://github.com/facebook/flow/issues/7
We've actually been discussing going the other way with a conversion tool for package publishers. Flow has a more sound type system and it's easier to downgrade than upgrade. The next few months should hopefully start seeing a lot of new tools for managing and publishing types within the community. It would be great to see more adoption from package owners themselves.
> conversion tool for package publishers
I'm not sure I understand how that's different from just supporting TypeScript definitions. Couldn't the conversion tool just be built into Flow so that it works transparently for the user? Or are you saying human intervention is required?
> Flow has a more sound type system
Can you elaborate? What are the features of Flow that aren't present in TypeScript and would result in lossy conversion?
Re: Flowtype 0.30 adds support for Windows
#6Earlier quoted context omitted.
We've actually been discussing going the other way with a conversion tool for package publishers. Flow has a more sound type system and it's easier to downgrade than upgrade. The next few months should hopefully start seeing a lot of new tools for managing and publishing types within the community. It would be great to see more adoption from package owners themselves.
> conversion tool for package publishers I'm not sure I understand how that's different from just supporting TypeScript definitions. Couldn't the conversion tool just be built into Flow so that it works transparently for the user? Or are you saying human intervention is required? > Flow has a more sound type system Can you elaborate? What are the features of Flow that aren't present in TypeScript and would result in…
It's not a trivial task for either Flow or TypeScript to support definitions of one another.
We've attempted to build a TS => Flow conversion tool, but it's much harder to go in that direction because you have less guarantees.
You aren't going to find a lot of "features" that either one supports that the other does not. However, many of TypeScript's implementations of the same features are less strict even with all of the strict flags on.
Here's an example that came up just last week: https://gist.github.com/thejameskyle/24a4e32be4899419e53eec6... (Note: This is not a bug in TypeScript, it's a design decision)
Because Flow is more strict than TypeScript it's much easier to convert from Flow definitions to TypeScript definitions.
Re: Flowtype 0.30 adds support for Windows
#7Hi HN, just wanted to let you know that the Flow team is watching this thread and is happy to respond to any questions that you have :)
Are there any IDEs or code editors on Windows which leverage Flow at the moment?
Re: Flowtype 0.30 adds support for Windows
#8Earlier quoted context omitted.
Any update on support for using TypeScript definition files with Flow? It doesn't seem as though the team is still watching the issue on Github: https://github.com/facebook/flow/issues/7
We've actually been discussing going the other way with a conversion tool for package publishers. Flow has a more sound type system and it's easier to downgrade than upgrade. The next few months should hopefully start seeing a lot of new tools for managing and publishing types within the community. It would be great to see more adoption from package owners themselves.
I very much doubt many package publishers will do this. Most users (if not all) that ask for TypeScript definition files support are doing so because they want to take advantage of DefinitelyTyped / @types going forward. However, any tools that can help us write once and use in both Flow and TypeScript will definitely be well received.
Re: Flowtype 0.30 adds support for Windows
#9Am I correct in saying that the Hack and Flow typecheckers share a lot of code? If so, does this mean that Hack typechecking on Windows could be next?
Re: Flowtype 0.30 adds support for Windows
#10Hi HN, just wanted to let you know that the Flow team is watching this thread and is happy to respond to any questions that you have :)
Are there any IDEs or code editors on Windows which leverage Flow at the moment?
Try Atom+Nuclide. With Flow now supported on Windows, it might work.