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)
test. When I enable the scala-js plugin in the sbt file it also adds it's own tests to the
testcommand as it was (testing only scala code).
crossProjectto build, in fact, 2 projects: one for the JVM and one for JS.
scalajs-stubsin the jvm dependencies :/
one could get both the 3 and 2.13 versions in the classpath through transitive dependencies, leading to bad issues.
scala-js-dom aside, is this a concern for libraries that are cross published for 2.13 and 3.0.0 with the same codebase (not scalaVersion-specific)? If so, what would the symptoms be, the usual binary incompatibility errors like "non-existent method"?
libraryDependencies += "org.scala-js" %%% "scalajs-dom" % "1.1.0", not found: /home/rich/.ivy2/localorg.scala-js/scalajs-dom_sjs1_3/1.1.0/ivys/ivy.xml [error] not found: https://repo1.maven.org/maven2/org/scala-js/scalajs-dom_sjs1_3/1.1.0/scalajs-dom_sjs1_3-1.1.0.pom
@Rich2 scalajs-dom is not published for Scala 3, but it works fine with using a 2.13 version.
Which version of SBT are you using?
("org.scala-js" %%% "scalajs-dom" % "1.1.0").cross(CrossVersion.for3Use2_13)
Should get you there then :)
scalajs-dom is not published for JVM - is that the cause?
Or something in the build errors?