Have users find fable bindings more easily

[humhei]

Using fake and appveyor ci to collect test-compile fs files Something like appveyor artifacts, But collect test-compile files named with build-version to github repository

So i can reference them directly This will make issue and pull request more clearly Take a look on https://github.com/fable-compiler/ts2fable/pull/164 If you agree with me, I will create a repository under fable-compile

How do you think about this? @alfonsogarciacaro @ctaggart

[alfonsogarciacaro]

That'd be awesome! We talked in the past about automating the publishing of bindings for popular JS libraries. It'll be also very good if we could annotate the bindings with the version of the TS declaration file used.

Please go ahead and create a new repository, just tell me if you have problems. Or we could also use the fable-import repository.

[humhei]

Thanks for @StachuDotNet 's awesome suggestion #166

• [x] Collect fs files to git repository Collect test-compile fs files to https://github.com/fable-compiler/ts2fable-exports

• [ ] Automatic README generation to https://github.com/fable-compiler/ts2fable-exports ----Struture like below

ts2fable compiled file	npm package	npm package version
React.fs	react	16.2.0

• [ ] Interact with the awesome domin definitelyfable.org