For pure projects, provide way to use only single publish artifact about sbt-crossproject HOT 3 CLOSED

Sorry, this has been debated long ago in Scala.js core. There's no guarantee that the class files produced through Scala.js are workable on the JVM. Plus, even if the sources are the same, the metadata aren't. Scala.js doesn't guarantee anything here.

Given the lack of guarantee, sbt-crossproject is not going to allow this easily. It will be too easy for users to shoot themselves in the foot.

If your particular build and sources happen to produce the same class files, and you're willing to bet that this will remain true in the future, you can figure out how to hack your build to do it (not using sbt-crossproject, then, but your own mechanism). I am not going to give hints on how to do that, because I don't want to be blamed if and when things go wrong with that approach.

from sbt-crossproject.

Are there any links to that discussion? I thought surely this must have been discussed or I completely misunderstood the issue but I couldn't find the discussions.

So why does ScalaJS generate class files in the first place if it doesn't use them? Is it just a side-effect of generating the sjsir files? What part of the process generates the class files and how could/would that be different than regular JVM project?

from sbt-crossproject.

Those discussions are really old. They date back from the first year of Scala.js. I'm on vacation with only a mobile phone, so I can't really look them up at the moment. You can try in the oldest closed issues of the core Scala.js repo.

from sbt-crossproject.