Add servant-client-ghcjs to hackage and stackage

[tysonzero]

Title, it would be convenient to be able to install it from Hackage/Stackage. I'm assuming the current recommended way to install it is via Github?

[phadej]

Yes, currently from GitHub

[tysonzero]

Alright will do, any ETA on when it will be on hackage / stackage etc.?

[alpmestan]

Were we not stuck on CI for servant-client-ghcjs?

[phadej]

Hmm, shouldn't -ghcjs package be buildable with normal GHC too (at least with small amount of CPP?) That would be good start

…

Sent from my iPhone

On 9 Apr 2018, at 10.45, Alp Mestanogullari ***@***.***> wrote: Were we not stuck on CI for servant-client-ghcjs? — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[ElvishJerricco]

If you're using the ghcjs-dom for all browser calls and not the JS FFI, you don't need to do anything to build with GHC. It will automatically fallback to the jsaddle backend.

[arianvp]

Oh that would be interesting. @FPtje do you know about the ghcjs-dom package?
We could at least use it to make servant-client-ghcjs run on GHC and run the unit tests. A more noble goal would be to merge servant-client and servant-client-ghcjs but that would be a next step.

[FPtje]

I do, yeah. I've refrained from using it because its jsaddle dependency is a rather bulky one.

By the way, I'm sure we can make servant-client-ghcjs build with ghc, but that might give the false impression that it also actually works with ghc. That might be technically possible with jsaddle, but I reckon it still wouldn't be desirable because servant-client would be the right choice anyway. To get it to work on CI I'd recommend trying to get the ghcjs compiler to work.

[ElvishJerricco]

I would recommend getting this to work via jsaddle. The ability to run reflex-dom apps via GHC+jsaddle is critical to my productivity with it. Dev cycles are literally an order of magnitude faster when you can :r in GHCi instead of waiting on GHCJS's slow compile times. When building frontends with GHC+jsaddle, it would be far more desirable to be able to use the same client library, knowing that it's using the same browser API that the GHCJS app will be using.

[roberth]

@ElvishJerricco are you looking for this? servant-client-jsaddle.

If anyone wants to move it into this repo, I'd be all for it.

[alpmestan]

Sorry, I somehow missed this. Yes we could certainly move it under haskell-servant. Still interested?

[roberth]

@alpmestan See #1018

[phadej]

I migrated servant-jsaddle to own repository, I consider the two remaining issues haskell-servant/servant-jsaddle#2 and haskell-servant/servant-jsaddle#1 blocking the release.

Closing this issue in favour of the other two.

[tysonzero]

I don't see how those issues address servant-client-ghcjs being on hackage/stackage.

Currently whenever I upgrade our stack I have to figure out what servant-* versions are being pulled from hackage and find a compatible git commit to pull servant-client-ghcjs from so that they co-operate. It's a pretty huge PITA.