sjrd on 0.6.x
Remove dead code: specific coll… Adapt the signature of `js.Arra… Merge pull request #3554 from s… (compare)
sjrd on master
Fix analyzer cycle detection to… Add toString methods to analyze… Do not provide linked ClassInfo… and 1 more (compare)
sjrd on master
Remove Logger.success It is un… Make level helpers final Clean-up ScalaConsoleLogger cod… and 1 more (compare)
Compileis important to specify the appropriate configuration. The
Testconfiguration uses a different file/artifact name.
It looks like exporting an object under a namespace (
x.y.myObject) is deprecated when done via
@JSExportTopLevel. Is there a workaround in 1.0 if that's really what I want to do?
(For context, I'm writing an AWS Lambda function that will be deployable via either JVM or JS. It'd be nice to have a common entrypoint for both platforms…
com.bpholt.my.great.Function should theoretically work, if supported, I think?)
TypeError: $g is undefined
scala-es-module.jswill be evaluated before the contents of that snippet are executed, and in particular before
window.__ScalaJSEnvis assigned. This is due to how ES modules are evaluated: all their dependencies are evaluated before the module's code starts to execute.
Hey guys, has anyone figured out how to make npm packages out of scala.js cross builds? @sjrd recommended me to ask here for help on this Github issue for my project: marianogappa/ostinato#9
Ostinato is the only chess library written in Scala that works in the browser (http://marianogappa.github.io/ostinato-examples/convert.html) and it's quite successful. Would anyone be able to help me make it approachable to the JS community? Cheers :)
@martijnhoekstra Thanks for confirming that suspicion. I never did serious work with JS before, just knew there was a huge ecosystem out there and hoped I could leverage from the scala side. For other purposes I'll need to add a REST API over the scala DB API anyway, so I can reuse that.
Anyone, the other part of my question has to do with refactoring of current scala typeclasses for integration/allocation across scala and scala.js for a coherent typeclass-based architecture. I would like to use scala.js typeclasses to drive a generic lightweight browser/editor for tabular data from my API. I think can move non-DB-oriented elements to separate typeclasses over the same set of non-DB-oriented types, make those shared, and keep the DB-oriented elements scala only. Are there any special potential issues or helps with such an approach that I should be aware of? Many thanks!