-
Notifications
You must be signed in to change notification settings - Fork 159
Add support for scala.js runtime #184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for scala.js runtime #184
Conversation
Ready to merge? |
RDY, I tested it locally and scala.js works perfectly. |
Would be great to have scripted tests execute on Travis, I will fix that |
OK |
Some time ago we discussed on Gitter and here about adding In Play! Framework Twirl module they went this way: playframework/twirl@104128a (look at |
Can you please explain what you mean? I think I don't undertand, do you mean adding addSbtPlugin in build? That doesn't solve the problem at all, as operator %%% used in that context has completly different meaning than operator used in user project (eg. different versions) |
We talked about using: OrgScoverage %%% ScalacRuntimeArtifact % coverageScalacPluginVersion.value, instead of OrgScoverage %% (ScalacRuntimeArtifact + optionalScalaJsSuffix(libraryDependencies.value)) % coverageScalacPluginVersion.value, |
Yes, but that approach would still require pulling in sbt-scalajs plugin. I checked its source code and there is nothing we could reuse, everything depends on hardcoded scala.js binary version. |
Hi @sjrd can you please confirm if such approach should support future version of scala.js? Or how we could improve that without adding sbt-scalajs to dependencies? |
It will work as long as we're in the 0.6.x series. When we switch to the 1.x.y series, the binary _sjs version will be only the major version, so |
No description provided.