Skip to content

Third Party Engines

Pode supports the use of third-party view engines, for example you could use the EPS or PSHTML template engines. To do this you'll need to supply a scriptblock to the Set-PodeViewEngine function which tells Pode how use the third-party engine to render views.

This custom scriptblock will be supplied with two arguments:

  1. $path: The path to the file that needs generating using your chosen template engine
  2. $data: Any data that was supplied to the Write-PodeViewResponse function

EPS

If you were to use the EPS engine, and already have the module installed, then the following server example would work for views and static content:

# import the EPS module
Import-Module -Name EPS

Start-PodeServer {
    Add-PodeEndpoint -Address * -Port 8080 -Protocol Http

    # set the engine to use and render EPS files
    # (could be index.eps, or for content scripts.css.eps)
    Set-PodeViewEngine -Type EPS -ScriptBlock {
        param($path, $data)
        $template = Get-Content -Path $path -Raw -Force

        if ($null -eq $data) {
            return (Invoke-EpsTemplate -Template $template)
        }
        else {
            return (Invoke-EpsTemplate -Template $template -Binding $data)
        }
    }

    # render the index.eps view
    Add-PodeRoute -Method Get -Path '/' -ScriptBlock {
        Write-PodeViewResponse -Path 'index'
    }
}

The following example structure could be used for the views and static content:

/views
    index.eps
/public
    styles/main.css.eps
    scripts/main.js.eps

PSHTML

If you were to use PSHTML engine, and already have the module installed, then the following server example would work for views and static content:

# import the PSHTML module
Import-Module -Name PSHTML

Start-PodeServer {
    Add-PodeEndpoint -Address * -Port 8080 -Protocol Http

    # set the engine to use and render PSHTML (which are just ps1) files
    # (could be index.ps1, or for content scripts.css.ps1)
    Set-PodeViewEngine -Type PSHTML -Extension PS1 -ScriptBlock {
        param($path, $data)
        return [string](. $path $data)
    }

    # render the index.eps view
    Add-PodeRoute -Method Get -Path '/' -ScriptBlock {
        Write-PodeViewResponse -Path 'index'
    }
}

The following example structure could be used for the views and static content:

/views
    index.ps1
/public
    styles/main.css.ps1
    scripts/main.js.ps1
Back to top