Getting Started with Scala.js and Vite

In this first tutorial, we learn how to get started with Scala.js and Vite. We use Vite to provide live-reloading of the Scala.js application in the browser for development. We also configure it to build a minimal bundle for production.

Going through this tutorial will make sure you understand the basic building blocks. If you prefer to skip this step and directly write Scala.js code, you may jump to Getting Started with Scala.js and Laminar.

If you prefer to look at the end result for this tutorial directly, checkout the scalajs-vite-end-state branch instead of creating everything from scratch.


Make sure to install the prerequisites before continuing further.

Vite template

We bootstrap our setup using the vanilla Vite template. Navigate to a directory where you store projects, and run the command

$ npm create [email protected]

Choose a project name (we choose livechart). Select the “Vanilla” framework and the “JavaScript” variant. Our output gives:

$ npm create [email protected]
Need to install the following packages:
  [email protected]
Ok to proceed? (y)
✔ Project name: … livechart
✔ Select a framework: › Vanilla
✔ Select a variant: › JavaScript

Scaffolding project in .../livechart...

Done. Now run:

  cd livechart
  npm install
  npm run dev

As instructed, we follow up with

$ cd livechart
$ npm install
$ npm run dev

  VITE v4.1.4  ready in 156 ms

  ➜  Local:   http://localhost:5173/
  ➜  Network: use --host to expose
  ➜  press h to show help

Open the provided URL to see the running JavaScript-based hello world.

Exploring the template

In the generated folder, we find the following relevant files:

  • index.html: the main web page; it contains a <script type=module src="/main.js"> referencing the main JavaScript entry point.
  • main.js: the main JavaScript entry point; it sets up some DOM elements, and sets up a counter for a button.
  • counter.js: it implements a counter functionality for a button.
  • package.json: the config file for npm, the JavaScript package manager and build orchestrator.

Remarkably, there is no vite.config.js file, which would be the configuration for Vite itself. Vite gives a decent experience out of the box, without any configuration.

Live changes

One of the main selling points of Vite is its ability to automatically refresh the browser upon file changes. Open the file main.js and change the content of the <h1> element:

     <a href="" target="_blank">
       <img src="${javascriptLogo}" class="logo vanilla" alt="JavaScript logo" />
-    <h1>Hello Vite!</h1>
+    <h1>Hello Scala.js!</h1>
     <div class="card">
       <button id="counter" type="button"></button>

Observe that the page automatically and instantaneously refreshes to show the changes.

Introducing Scala.js

We use sbt as a build tool for Scala and Scala.js. We set it up as follows.

In the subdirectory livechart/project/, we add two files: and plugins.sbt.

  • project/ set the version of sbt
  • project/plugins.sbt: declare sbt plugins; in this case, only sbt-scalajs
addSbtPlugin("org.scala-js" % "sbt-scalajs" % "1.16.0")

At the root of our livechart/ project, we add one file: build.sbt.

  • build.sbt: the main sbt build
import org.scalajs.linker.interface.ModuleSplitStyle

lazy val livechart ="."))
  .enablePlugins(ScalaJSPlugin) // Enable the Scala.js plugin in this project
    scalaVersion := "3.2.2",

    // Tell Scala.js that this is an application with a main method
    scalaJSUseMainModuleInitializer := true,

    /* Configure Scala.js to emit modules in the optimal way to
     * connect to Vite's incremental reload.
     * - emit ECMAScript modules
     * - emit as many small modules as possible for classes in the "livechart" package
     * - emit as few (large) modules as possible for all other classes
     *   (in particular, for the standard library)
    scalaJSLinkerConfig ~= {

    /* Depend on the scalajs-dom library.
     * It provides static types for the browser DOM APIs.
    libraryDependencies += "org.scala-js" %%% "scalajs-dom" % "2.4.0",

Finally, we write the following content in the file src/main/scala/livechart/LiveChart.scala:

package livechart

import scala.scalajs.js
import scala.scalajs.js.annotation.*

import org.scalajs.dom

// import javascriptLogo from "/javascript.svg"
@js.native @JSImport("/javascript.svg", JSImport.Default)
val javascriptLogo: String = js.native

def LiveChart(): Unit =
  dom.document.querySelector("#app").innerHTML = s"""
      <a href="" target="_blank">
        <img src="/vite.svg" class="logo" alt="Vite logo" />
      <a href="" target="_blank">
        <img src="$javascriptLogo" class="logo vanilla" alt="JavaScript logo" />
      <h1>Hello Scala.js!</h1>
      <div class="card">
        <button id="counter" type="button"></button>
      <p class="read-the-docs">
        Click on the Vite logo to learn more

end LiveChart

def setupCounter(element: dom.Element): Unit =
  var counter = 0

  def setCounter(count: Int): Unit =
    counter = count
    element.innerHTML = s"count is $counter"

  element.addEventListener("click", e => setCounter(counter + 1))
end setupCounter

Note that the above is not idiomatic Scala, but rather a direct translation of the Vite template code into Scala.js. We will see in the next tutorial how to use Laminar to write it more idiomatically.

For the most part, the Scala.js version uses straightforward Scala syntax corresponding to the original JavaScript code. The definition of javascriptLogo deserves some explanation.

We translated it from the JavaScript import

import javascriptLogo from "/javascript.svg"

which is actually a shorthand for

import { default as javascriptLogo } from "/javascript.svg"

Many bundlers, Vite included, treat imports with asset files such as .svg as pseudo-modules whose default import is the file path to the corresponding asset in the processed bundle. Further down, we use it as the value for the src attribute an <img> tag. Read more about this mechanism in the Vite documentation on static asset handling.

The translation in Scala.js reads as

@js.native @JSImport("/javascript.svg", JSImport.Default)
val javascriptLogo: String = js.native

The @js.native annotation tells Scala.js that javascriptLogo is provided externally by JavaScript. The @JSImport("/javascript.svg", JSImport.Default) is the translation of the default import from the /javascript.svg pseudo-module. Since it represents a file path, we declare javascriptLogo as a String.

The = js.native is a Scala.js idiosyncrasy: we need a concrete value to satisfy the Scala typechecker. In an ideal world, it would not be required.

We can now build the Scala.js project by opening a new console, and entering sbt:

$ sbt
sbt:livechart> ~fastLinkJS

The fastLinkJS task produces the .js outputs from the Scala.js command. The ~ prefix instructs sbt to re-run that task every time a source file changes.

There is one thing left to change: replace the hand-written JavaScript code with our Scala.js application. We use the @scala-js/vite-plugin-scalajs plugin to link Vite and Scala.js with minimal configuration. We install it in the dev-dependencies with:

$ npm install -D @scala-js/[email protected]

and instruct Vite to use it with the following configuration in a new file vite.config.js:

import { defineConfig } from "vite";
import scalaJSPlugin from "@scala-js/vite-plugin-scalajs";

export default defineConfig({
  plugins: [scalaJSPlugin()],

Finally, open the file main.js, remove almost everything to leave only the following two lines:

import './style.css'
import 'scalajs:main.js'

When we import a URI starting with scalajs:, vite-plugin-scalajs resolves it to point to the output directory of Scala.js’ fastLinkJS task.

You may have to stop and restart the npm run dev process, so that Vite picks up the newly created configuration file. Vite will refresh the browser with our updated “Hello Scala.js!” message.

Live changes with Scala.js

Earlier, we noticed how changing the JavaScript files caused Vite to immediately refresh the browser. Is that also the case if we change the Scala source files?

Indeed it is. Let us change the message to

       <a href="" target="_blank">
         <img src="/javascript.svg" class="logo vanilla" alt="JavaScript logo" />
-      <h1>Hello Scala.js!</h1>
+      <h1>Hello Scala.js and Vite!</h1>
       <div class="card">
         <button id="counter" type="button"></button>

Once we save, we notice that the browser refreshes with the updated message.

There are two things happening behind the scenes:

  1. The ~fastLinkJS task in sbt notices that a .scala file has changed, and therefore rebuilds the .js output.
  2. The npm run dev process with Vite notices that a .js file imported from /main.js has changed, and triggers a refresh with the updated files.

All these steps are incremental. When we change a single Scala file, only that one gets recompiled by the Scala incremental compiler. Then, only the affected small .js modules produced by fastLinkJS are regenerated. Finally, Vite only reloads those small .js files that were touched. This ensures that the development cycle remains as short as possible.

Production build

The fastLinkJS task of sbt and the npm run dev task of Vite are optimized for incremental development. For production, we want to perform more optimizations on the Scala.js side and bundle minimized files with npm run build. We stop Vite with Ctrl+C and launch the following instead:

$ npm run build

> [email protected] build
> vite build

vite v4.1.4 building for production...
[info] welcome to sbt 1.8.0 (Temurin Java 1.8.0_362)
[info] Full optimizing .../livechart/target/scala-3.2.2/livechart-opt
✓ 11 modules transformed.
dist/index.html                       0.45 kB
dist/assets/javascript-8dac5379.svg   1.00 kB
dist/assets/index-48a8825f.css        1.24 kB │ gzip: 0.65 kB
dist/assets/index-3c83baa6.js        28.84 kB │ gzip: 6.97 kB

Since the built website uses an ECMAScript module, we need to serve it through an HTTP server to visualize it. We can use Vite’s preview mode for that purpose, as we can run it without any additional dependency:

$ npm run preview

> [email protected] preview
> vite preview

  ➜  Local:   http://localhost:4173/
  ➜  Network: use --host to expose

Navigate to the mentioned URL to see your website.


In this tutorial, we saw how to configure Scala.js with Vite from the ground up using @scala-js/vite-plugin-scalajs. We used sbt as our build tool, but the same effect can be achieved with any other Scala build tool, such as Mill or scala-cli.

Our setup features the following properties:

  • Development mode with live reloading: changing Scala source files automatically triggers recompilation and browser refresh.
  • Production mode taking the fully optimized output of Scala.js and producing a unique .js file.

In our next tutorial about Laminar, we will learn how to write UIs in idiomatic Scala code.