Play Framework with Scala.js
This is a simple example application showing how you can integrate a Play project with a Scala.js project.
The application contains three directories:
serverPlay application (server side)
clientScala.js application (client side)
sharedScala code that you want to share between the server and the client
Run the application
$ sbt > run $ open http://localhost:9000
- Run your application like a regular Play app
compilesimply triggers the Scala.js compilation
runtriggers the Scala.js fastOptJS command on page refresh
~run, continuous compilation is also available
- 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 := truein the Scala.js projects.
$ sbt eclipse
- Inside Eclipse,
File/Import/General/Existing project..., choose the root folder. Uncheck the second and the last checkboxes to only import client, server and one shared, click
In IntelliJ, open Project wizard, select
Import Project, choose the root folder and click
Import project from external model option, choose
SBT project and click
Next. Select additional import options and click
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 -ncreates an app and prints its name.
- Set the
build.sbtwith the name of the application you created.
$ sbt stage deployHeroku
This example uses the sbt-heroku plugin to deploy to Heroku.