Skip to main content
Version: 0.14.0

Wasp Language (.wasp)

Wasp language (what you write in .wasp files) is a declarative, statically typed, domain-specific language (DSL).

It is a quite simple language, closer to JSON, CSS or SQL than to e.g. Javascript or Python, since it is not a general programming language, but more of a configuration language.

It is pretty intuitive to learn (there isn't much to learn really!) and you can probably do just fine without reading this page and learning from the rest of the docs as you go, but if you want a bit more formal definition and deeper understanding of how it works, then read on!


The central point of Wasp language are declarations, and Wasp code is at the end just a bunch of declarations, each of them describing a part of your web app.

app MyApp {
title: "My app"

route RootRoute { path: "/", to: DashboardPage }

page DashboardPage {
component: import { DashboardPage } from "@src/Dashboard.jsx"

In the example above we described a web app via three declarations: app MyApp { ... }, route RootRoute { ... } and page DashboardPage { ... }.

Syntax for writing a declaration is <declaration_type> <declaration_name> <declaration_body>, where:

  • <declaration_type> is one of the declaration types offered by Wasp (app, route, ...)
  • <declaration_name> is an identifier chosen by you to name this specific declaration
  • <declaration_body> is the value/definition of the declaration itself, which has to match the specific declaration body type expected by the chosen declaration type.

So, for app declaration above, we have:

  • declaration type app
  • declaration name MyApp (we could have used any other identifier, like foobar, foo_bar, or hi3Ho)
  • declaration body { title: "My app" }, which is a dictionary with field title that has string value. Type of this dictionary is in line with the declaration body type of the app declaration type. If we provided something else, e.g. changed title to little, we would get a type error from Wasp compiler since that does not match the expected type of the declaration body for app.

Each declaration has a meaning behind it that describes how your web app should behave and function.

All the other types in Wasp language (primitive types (string, number), composite types (dict, list), enum types (DbSystem), ...) are used to define the declaration bodies.

Complete List of Wasp Types

Wasp's type system can be divided into two main categories of types: fundamental types and domain types.

While fundamental types are here to be basic building blocks of a language and are very similar to what you would see in other popular languages, domain types are what make Wasp special, as they model the concepts of a web app like page, route and similar.

  • Fundamental types (source of truth)
    • Primitive types
      • string ("foo", "they said: \"hi\"")
      • bool (true, false)
      • number (12, 14.5)
      • declaration reference (name of existing declaration: TaskPage, updateTask)
      • ExtImport (external import) (import Foo from "@src/bar.js", import { Smth } from "@src/a/b.js")
        • The path has to start with "@src". The rest is relative to the src directory.
        • Import has to be a default import import Foo or a single named import import { Foo }.
      • json ({=json { a: 5, b: ["hi"] } json=})
    • Composite types
      • dict (dictionary) ({ a: 5, b: "foo" })
      • list ([1, 2, 3])
      • tuple ((1, "bar"), (2, 4, true))
        • Tuples can be of size 2, 3 and 4.
  • Domain types (source of truth)
    • Declaration types
      • action
      • api
      • apiNamespace
      • app
      • job
      • page
      • query
      • route
      • crud
    • Enum types
      • DbSystem
      • HttpMethod
      • JobExecutor
      • EmailProvider
    • Models from the schema.prisma file
      • You can reference models defined in the schema.prisma file in your Wasp file by using the model name e.g. Task.

You can find more details about each of the domain types, both regarding their body types and what they mean, in the corresponding doc pages covering their features.