This is a simple example application showing how you can integrate a Play project with a Scala.js project.
The application contains three directories:
example-server
Play application (server side)example-client
Scala.js application (client side)example-shared
Scala code that you want to share between the server and the client
$ sbt
> run
$ open http://localhost:9000
The application uses the sbt-play-scalajs sbt plugin and the play-scalajs-scripts library.
- Run your application like a regular Play app
compile
simply triggers the Scala.js compilationrun
triggers the Scala.js fastOptJS command on page refresh~compile
,~run
, continuous compilation is also availablestart
,stage
anddist
generate the optimised javascriptplayscalajs.html.scripts
selects the optimised javascript file when the application runs in prod mode (start
,stage
,dist
).
- Source maps
- Open your browser dev tool to set breakpoints or to see the guilty line of code when an exception is thrown
- Source Maps is disabled in production by default to prevent your users from seeing the source files. But it can easily be enabled in production too by setting
emitSourceMaps in fullOptJS := true
in the Scala.js projects.
$ sbt eclipse
- Inside Eclipse,
File/Import/General/Existing project...
, choose the root folder. Uncheck the last two checkboxes to only import exampleClient, exampleServer and one exampleShared, clickFinish
.
In IntelliJ, File/Import Project...
, choose the root folder, Import project from external model/SBT/Finish
.
Make sure you use the IntelliJ Scala Plugin v1.3.3 or higher. There are known issues with prior versions of the plugin.
$ heroku create -n
creates an app and prints its name.- Set the
herokuAppName
inbuild.sbt
with the name of the application you created. $ sbt stage deployHeroku
This example uses the sbt-heroku plugin to deploy to Heroku.