Mithril is a modern client-side JavaScript framework for building Single Page Applications. It's small (< 10kb gzip), fast and provides routing and XHR utilities out of the box.

Download size Mithril (9.5kb) Vue + Vue-Router + Vuex + fetch (40kb) React + React-Router + Redux + fetch (64kb) Angular (135kb) Performance Mithril (6.4ms) Vue (9.8ms) React (12.1ms) Angular (11.5ms)

Mithril is used by companies like Vimeo and Nike, and open source platforms like Lichess.

If you are an experienced developer and want to know how Mithril compares to other frameworks, see the framework comparison page.

Mithril supports IE11, Firefox ESR, and the last two versions of Firefox, Edge, Safari, and Chrome. No polyfills required.

Looking for the v1 docs? Click here.

An easy way to try out Mithril is to include it from a CDN and follow this tutorial. It'll cover the majority of the API surface (including routing and XHR) but it'll only take 10 minutes.

Let's create an HTML file to follow along:

<body> <script src="https://unpkg.com/mithril/mithril.js"></script> <script> var root = document.body // your code goes here! </script> </body>

To make things simpler you can fork this pen which already has the latest version of mithril loaded.

See the Pen Mithril Scaffold by Pat Cavit (@tivac) on CodePen.

Mithril is also loaded onto this page already, so you can start poking at the m object in the developer console right away if you'd like!

Let's start as small as we can: render some text on screen. Copy the code below into your file (and by copy, I mean type it out - you'll learn better)

var root = document.body m.render(root, "Hello world")

Now, let's change the text to something else. Add this line of code under the previous one:

m.render(root, "My first app")

As you can see, you use the same code to both create and update HTML. Mithril automatically figures out the most efficient way of updating the text, rather than blindly recreating it from scratch.

See the Pen Mithril Hello World by Pat Cavit (@tivac) on CodePen.

Let's wrap our text in an <h1> tag.

m.render(root, m("h1", "My first app"))

The m() function can be used to describe any HTML structure you want. So if you need to add a class to the <h1> :

m("h1", {class: "title"}, "My first app")

If you want to have multiple elements:

[ m("h1", {class: "title"}, "My first app"), m("button", "A button"), ]

And so on:

m("main", [ m("h1", {class: "title"}, "My first app"), m("button", "A button"), ])

See the Pen Simple Mithril Example by Pat Cavit (@tivac) on CodePen.

Note: If you prefer <html> syntax, it's possible to use it via a Babel plugin.

// HTML syntax via Babel's JSX plugin <main> <h1 class="title">My first app</h1> <button>A button</button> </main>

A Mithril component is just an object with a view function. Here's the code above as a component:

var Hello = { view: function() { return m("main", [ m("h1", {class: "title"}, "My first app"), m("button", "A button"), ]) } }

To activate the component, we use m.mount .

m.mount(root, Hello)

As you would expect, doing so creates this markup:

<main> <h1 class="title">My first app</h1> <button>A button</button> </main>

The m.mount function is similar to m.render , but instead of rendering some HTML only once, it activates Mithril's auto-redrawing system. To understand what that means, let's add some events:

var count = 0 // added a variable var Hello = { view: function() { return m("main", [ m("h1", {class: "title"}, "My first app"), // changed the next line m("button", {onclick: function() {count++}}, count + " clicks"), ]) } } m.mount(root, Hello)

We defined an onclick event on the button, which increments a variable count (which was declared at the top). We are now also rendering the value of that variable in the button label.

You can now update the label of the button by clicking the button. Since we used m.mount , you don't need to manually call m.render to apply the changes in the count variable to the HTML; Mithril does it for you.

If you're wondering about performance, it turns out Mithril is very fast at rendering updates, because it only touches the parts of the DOM it absolutely needs to. So in our example above, when you click the button, the text in it is the only part of the DOM Mithril actually updates.

See the Pen Mithril Component Example by Pat Cavit (@tivac) on CodePen.

Routing just means going from one screen to another in an application with several screens.

Let's add a splash page that appears before our click counter. First we create a component for it:

var Splash = { view: function() { return m("a", {href: "#!/hello"}, "Enter!") } }

As you can see, this component simply renders a link to #!/hello . The #! part is known as a hashbang, and it's a common convention used in Single Page Applications to indicate that the stuff after it (the /hello part) is a route path.

Now that we're going to have more than one screen, we use m.route instead of m.mount .

m.route(root, "/splash", { "/splash": Splash, "/hello": Hello, })

The m.route function still has the same auto-redrawing functionality that m.mount does, and it also enables URL awareness; in other words, it lets Mithril know what to do when it sees a #! in the URL.

The "/splash" right after root means that's the default route, i.e. if the hashbang in the URL doesn't point to one of the defined routes ( /splash and /hello , in our case), then Mithril redirects to the default route. So if you open the page in a browser and your URL is https://localhost , then you get redirected to https://localhost/#!/splash .

Also, as you would expect, clicking on the link on the splash page takes you to the click counter screen we created earlier. Notice that now your URL will point to https://localhost/#!/hello . You can navigate back and forth to the splash page using the browser's back and next button.

See the Pen Mithril Routing Example by Pat Cavit (@tivac) on CodePen.

Basically, XHR is just a way to talk to a server.

Let's change our click counter to make it save data on a server. For the server, we'll use REM, a mock REST API designed for toy apps like this tutorial.

First we create a function that calls m.request . The url specifies an endpoint that represents a resource, the method specifies the type of action we're taking (typically the PUT method upserts), body is the payload that we're sending to the endpoint and withCredentials means to enable cookies (a requirement for the REM API to work)

var count = 0 var increment = function() { m.request({ method: "PUT", url: "//rem-rest-api.herokuapp.com/api/tutorial/1", body: {count: count + 1}, withCredentials: true, }) .then(function(data) { count = parseInt(data.count) }) }

Calling the increment function upserts an object {count: 1} to the /api/tutorial/1 endpoint. This endpoint returns an object with the same count value that was sent to it. Notice that the count variable is only updated after the request completes, and it's updated with the response value from the server now.

Let's replace the event handler in the component to call the increment function instead of incrementing the count variable directly:

var Hello = { view: function() { return m("main", [ m("h1", {class: "title"}, "My first app"), m("button", {onclick: increment}, count + " clicks"), ]) } }

Clicking the button should now update the count.

See the Pen Mithril XHR Example by Isiah Meadows (@isiahmeadows) on CodePen.

We covered how to create and update HTML, how to create components, routes for a Single Page Application, and interacted with a server via XHR.

This should be enough to get you started writing the frontend for a real application. Now that you are comfortable with the basics of the Mithril API, be sure to check out the simple application tutorial, which walks you through building a realistic application.

License: MIT. © Leo Horie.