Use sbt-web-scalajs v1.0.1 and scalajs-scripts v1.0.0.

vmunier commented 8 years ago

Changes from sbt-web-scalajs:

build.sbt uses the scalaJSPipeline task, which runs scalaJSDev in dev mode, runs scalaJSProd otherwise. The plugin is in dev mode when the user executes one of the devCommands, which are run, compile and re-start. devCommands can be extended/overridden to contain different dev commands. More info in the README.md: https://github.com/vmunier/sbt-web-scalajs/tree/e14dc902cecefdf418c77c336166fdee7ce8f0e7#settings-and-tasks
The plugin watches files from the Scala.js projects and thus aggregating the client projects in server is not needed for continuous compilation anymore. compile in Compile <<= (compile in Compile) dependsOn scalaJSPipeline triggers scalaJSPipeline when using continuous compilation. If a task has to be run on all projects, e.g. clean or test on all projects, it's good practice to use the root project: scalajs-spa-tutorial/clean.

Changes from scalajs-scripts:

Drop the Play dependency
No more implicit Environment parameter, a resourceExists parameter is required from all the Twirl templates instead.

Let me know if you have any questions.

vmunier commented 8 years ago

I am not sure why travis ci is failing, it's probably worth retrying the build.

nremond commented 7 years ago

I guess this PR can be closed, no?

vmunier commented 7 years ago

Sure, looks like the upgrade to sbt-web-scalajs and scalajs-scripts has been made as part of this commit 179d4f1b.

ochrons / scalajs-spa-tutorial