On Wednesday, November 23, 2016 at 9:35:21 PM UTC, Noah Hall wrote: > > The canoncial server-side Elm example is the take-home, > https://github.com/noredink/take-home, written by me. AFAIK it is > still the only full stack-Elm application. It also lists good reasons > as to not take that approach and why it should be avoided at all > costs. > > If you want to render code on the server side, you can use > https://github.com/eeue56/elm-server-side-renderer/ which is also > written by me. While it's labelled a work in progress, we use it for > our production tests at NoRedInk and have been doing so for a while > now. > > You'll need to set up a port to pull the generated string out, but > it's trivial bit of work to do with the elm-server-side-renderer > project. Just take a look at how something like elm-test pulls values > out through a port.
Thanks man, that sounds interesting. There doesn't appear to be a huge amount of javascript involved, so I guess that makes it fairly portable as to which javascript engine it can be run on? -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
