Skip to main content
Have a Wasp app in production? 🐝 We'll send you some swag! πŸ‘•
This is documentation for Wasp 0.17.0, which is no longer actively maintained.
For up-to-date documentation, see the latest version (0.20.0).
Version: 0.17.0

Server Config

You can configure the behavior of the server via the server field of app declaration:

  • JavaScript
  • TypeScript
main.wasp
appMyApp{
title: "My app",
// ...
server: {
setupFn: import{ mySetupFunction }from"@src/myServerSetupCode.js",
middlewareConfigFn: import{ myMiddlewareConfigFn }from"@src/myServerSetupCode.js"
}
}

Setup Function​

Adding a Custom Route​

As an example, adding a custom route would look something like:

  • JavaScript
  • TypeScript
src/myServerSetupCode.ts
exportconstmySetupFunction=async({ app })=>{
addCustomRoute(app)
}

functionaddCustomRoute(app){
app.get('/customRoute',(_req, res)=>{
res.send('I am a custom route')
})
}

Storing Some Values for Later Use​

In case you want to store some values for later use, or to be accessed by the Operations you do that in the setupFn function.

Dummy example of such function and its usage:

  • JavaScript
  • TypeScript
src/myServerSetupCode.js
let someResource =undefined

exportconstmySetupFunction=async()=>{
// Let's pretend functions setUpSomeResource and startSomeCronJob
// are implemented below or imported from another file.
someResource =awaitsetUpSomeResource()
startSomeCronJob()
}

exportconstgetSomeResource=()=> someResource
src/queries.js
import{ getSomeResource }from'./myServerSetupCode.js'

...

exportconstsomeQuery=async(args, context)=>{
const someResource =getSomeResource()
returnqueryDataFromSomeResource(args, someResource)
}
note

The recommended way is to put the variable in the same module where you defined the setup function and then expose additional functions for reading those values, which you can then import directly from Operations and use.

This effectively turns your module into a singleton whose construction is performed on server start.

Read more about server setup function below.

Middleware Config Function​

You can configure the global middleware via the middlewareConfigFn. This will modify the middleware stack for all operations and APIs.

Read more about middleware config function below.

API Reference​

  • JavaScript
  • TypeScript
main.wasp
appMyApp{
title: "My app",
// ...
server: {
setupFn: import{ mySetupFunction }from"@src/myServerSetupCode.js",
middlewareConfigFn: import{ myMiddlewareConfigFn }from"@src/myServerSetupCode.js"
}
}

app.server is a dictionary with the following fields:

  • setupFn: ExtImport​

    setupFn declares a function that will be executed on server start. This function is expected to be async and will be awaited before the server starts accepting any requests.

    It allows you to do any custom setup, e.g. setting up additional database/websockets or starting cron/scheduled jobs.

    The setupFn function receives the express.Application and the http.Server instances as part of its context. They can be useful for setting up any custom server logic.

    • JavaScript
    • TypeScript
    src/myServerSetupCode.js
    exportconstmySetupFunction=async()=>{
    awaitsetUpSomeResource()
    }
  • middlewareConfigFn: ExtImport​

    The import statement to an Express middleware config function. This is a global modification affecting all operations and APIs. See more in the configuring middleware section.

AltStyle γ«γ‚ˆγ£γ¦ε€‰ζ›γ•γ‚ŒγŸγƒšγƒΌγ‚Έ (->γ‚ͺγƒͺγ‚ΈγƒŠγƒ«) /