//build.sbt
// ...
val scalaJsAsAsset = settingKey[Boolean]("Include scalaJs as an sbt-web asset of app_common")
// ...
commands += Command.command("backendDev")("set app_common/scalaJsAsAsset := true; ~app_lrbcol/reStart" :: _)
// ...
lazy val app_common =
// ...
.settings(
// ...
scalaJsAsAsset := insideCI.value,
scalaJSProjects := Seq(app_js),
Assets / WebKeys.packagePrefix := "public/",
Assets / pipelineStages := {
val asAsset = scalaJsAsAsset.value
println("Evaluating pipelineStages, scalaJsAsAsset = " + asAsset)
(if (asAsset) Seq(scalaJSPipeline) else Nil) ++
(if (insideCI.value) Seq(digest, gzip) else Nil)
}
)
ws.onerror callback which accepts Event object. I cannot pattern match Event and trying to cast it to ErrorEvent causes errors. Maybe there's some other way of extracting some meaningful message in this callback?ws.onerror = (e: Event) => {
val msg: String = ???
}
Hi, I'm trying to understanding how to skip publishing of scala-js artifacts. The configuration seems simple, I am adding skip.in(publish) := true to my commonJsSettings
however, when i go to try and run unit tests with this setting, i get immediate failures in the build. If I remove this setting, I get linking failures (which I expect).
https://github.com/bitcoin-s/bitcoin-s/pull/2731/commits/ba54261346b6c679ec198762585c4674bcb894f9
You can see the test case in this commit as well, which is BCryptoTest that does not have any external dependencies on the bitcoin-s project (just scalatest)
skip.in(publish) := true setting? This seems entirely irrelevant to getting a unit test to pass
JSExportTopLevel and JSExportAll to a case class and JSExportTopLevel to an object containing a function. I can call the one function that seems to return an instance of such a case class in the browser. However, the returned value is obfuscated in js, so I can't get reliably a hold on the object properties. How can I make it better accessible from plain javascript (not using scalajs in the browser :-/)?
@sjrd thanks! I created these two classes
@JSExportTopLevel("DsItemQueryParser")
object ItemQueryParser {
@JSExport
def parse(input: String): Either[ParseFailure, ItemQuery] =
...
}
@JSExportAll@JSExportTopLevel("ParseFailure")
final case class ParseFailure(
input: String,
failedAt: Int,
messages: Nel[ParseFailure.Message]
) {
def render: String = {
val items = messages.map(_.msg).toList.mkString(", ")
s"Failed to read input near $failedAt: $input\nDetails: $items"
}
}I then use the fullOptJS task to create a js file that I add to the html page. In the browser console I find this:
Kj, Lj where I was guessing that this comes from some obfuscation/minifying process…
.x() and .y() one of them says "Left" or "Right". Does this mean the Either is encoded that way? Should I create rather a custom type?
Either. Then the debugger shows me the case class fields as "fields" (unsure about correct js term, but it's not a function, I can "directly" access them in js). Still looks strange when a NonEmptyList is used or an Option. But I can now keep discovering further :) thank you!
scala.List/Array in case classes which get translated into an object with properties, but these are not very usable – once finding out about the js native variants e.g. scala.scalajs.js.Array things look much better now. I was not aware of these, because I first set Crossproject.Pure where I don't have access.
not found: https://repo1.maven.org/maven2/org/scoverage/scalac-scoverage-runtime_sjs1.5_2.13/1.4.1/scalac-scoverage-runtime_sjs1.5_2.13-1.4.1.pom
sjs1.5_2.13 part, which maybe should be sjs1_2.13
What's the state of the art in scala.js wrt building reactive (in the rxjs sense) frontend applications? Is everyone just going with a Scala.js/React wrapper library and calling it a day, or has there been any movement on the native Scala.js framework/library front?
Having spent the last couple of years working with TypeScript on the frontend I've grown to appreciate the amazing JS interop and tooling, but otherwise really miss the power of Scala/Scala.js.
3 replies
Hello all. So I'm wondering if there are exceptions Scalajs Try doesn't catch ?
On my test it doesn't appear to catch index out of bound exception. Or for something like this:
import scala.util._
val a = Try {
"aaa".split(" ")(2)
}
val b = Try {
Integer.parseInt("aaa")
}b will work but a will crash the program.
@hejfelix it's working really well so far, add this to your plugins.sbt:
addSbtPlugin("ch.epfl.lamp" % "sbt-dotty" % "0.5.3")
addSbtPlugin("org.scala-js" % "sbt-scalajs" % "1.5.0")In build.sbt set the scala version:
scalaVersion := "3.0.0-RC1"And everything should be good to go. Whenever a new RC is released you need to check if new plugin versions have been released.
