stereobooster / type-o-rama Goto Github PK

244.0 13.0 6.0 125 KB

👾 JS type systems interportability

typescript jsdoc json-schema flow graphql-schema elm closure-compiler purescript

type-o-rama's Issues

Who uses Flow:

There is a tool for going from TypeScript -> F# (Fable) https://github.com/fable-compiler/ts2fable

Can we add this to the chart?

https://transform.tools/. Is it former transform.now.sh?

there are no decoder generators 📦, like for Elm Json.Decoders or TypeScript proxies. UPD tried to use io-ts for this, but starting from version 1.0 io-ts dropped Flow support
flow-typed install is frustrating
workflow around creating signatures is frustrating. You can generate definitions with flow gen-flow-files or flow-typed create-stub or you can create dinitions from TypeScript with flowgen, but it is so much effort to donate those signatures to flow-typed repo
type errors can be really obscure and give no clue about what is wrong. Examples of how it supposed to be: BetterErrors for Reason or Elm
there is no tool which can convert Flow signatures to Closure JSDoc to use in Google Closure Compiler with advanced mode
For type definitions distributed with packages to be picked up automatically, you need to include node_modules in analysis, which makes process painfully slow.

Language	Library	Counter	TodoMVC	hnpwa	code spliting	SSR	Runtime exceptions	Promise
Elm	built-in	+	+	+	no until 0.19	no until 0.19	+	Use Task instead of Promise
TypeScript	elm-ts	+	+		maybe	maybe	+
BuckleScript	bucklescript-tea	+			maybe	maybe	+	repromise, vow
PureScript	pux	+	+		I suspect not			aff-promise
Clojure	larch
Fable	fable-arch