To other library authors that even consider supporting scala.js: do it EARLY! backporting later is not hard, but it's. so. much. work.
-
It's really not that difficult, just very long - there's tons of details to take care of. The one truly problematic thing is that, in scala.js world, you can find out at runtime that your dependencies weren't set properly, and the error message is scarier than it is helpful.
Code-side or build-side? JavaScript dependencies, knowing little about them, scare me. Not sure if a better understanding would cure that...
-
-
Well, in my case, I don't *have* JS dependencies, it's 100% Scala, just compiled to JS. Honestly, if you're looking to port some of your libs to scala.js, it's really not that hard - daunting, but surprisingly easy.
-
It sounds like something the
@ParisScalaUG would be delighted to organise a hackaton for, and something for which a hackaton would actually be useful.@ValentinKasas, what do you think? - Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.