onedevatlasBeta
Browse the atlas
AllCAPUI5ABAPBTP
SampleSampletypeA worked example you read or clone. Evidence: it demonstrates, it never provides.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →Reference

ui5-cap-serverside-rendering-demo

The demo project the ui5-cap-serverside-rendering-plugin README points to: a CAP bookshop whose Books list and detail views sit in srv/views and reach the browser already filled with data.

db/schema.cds extends Books with the plugin's ServerSideRendering aspect and annotates it @(ServerSideRenderingType:'view'), and srv/cat-service.cds exposes it read-only through CatalogService. The two files under srv/views are ordinary UI5 XML with Handlebars where the bindings would be: {{#each Books}} around a StandardListItem titled {{title}} - {{ID}}, so what the server returns is the markup itself. On the app side, a TypeScript freestyle app under app/serverside-rendering ships no list or detail view of its own: its manifest sets routerClass to be.wl.serversiderendering.library.ServerSideRouter and gives each route a url such as /odata/v4/catalog/Books({id})/content, and the controller navigates by reading the ID the list item wrote into the DOM as CustomData. That router class is not in the repository: the app's package.json depends on the npm package be.wl.serversiderendering.library for it.

GitHub4 ★

Facts

Last push

Where it sits

Lives in
CAP
Add-on to
@sap/cds@sap/cdsartifactThe CAP Node.js runtime, which compiles the CDS model, serves the services declared in it, answers generic requests before any handler runs, and loads every cds-plugin.
Serves
UI5
Flavors
UI5 /Freestyle
Runs
Cloud Foundry
Requires
ui5-cap-serverside-rendering-pluginui5-cap-serverside-rendering-pluginartifactThe server half of what the project shows: the ServerSideRendering aspect applied to Books and the handler that fills the views kept in srv/views.@sap/cds@sap/cdsartifactThe CAP Node.js runtime the project's service runs on.cds-plugin-ui5cds-plugin-ui5artifactServes the UI5 CLI project under app/, an npm workspace of the CAP project, from the CDS server's own port — the address the app README gives for opening it.@sap/cds-dk@sap/cds-dkartifactcds watch, the command the README gives for running the project.
Optional
@cap-js/sqlite@cap-js/sqliteartifactThe database the project reads db/data/my.bookshop-Books.csv into while it is run locally.

Who is behind it

Wouter LemaireWouter LemairePersonMaintains this
In the atlas: maintains 25, contributes to 39, wrote 12@lemaiwomaintainer

Before choosing this

Signals

LicenceNo licenseNeither the package manifest nor the repository tree declares a licence

Without a licence the default is all rights reserved. Ask the maintainer, or check for terms stated elsewhere, before depending on it.

Conditions

PracticalFunctional boundary

As a deployment template it stops at the service: the mta.yaml has one module, gen/srv on the Node.js buildpack, and no HTML5 repository or router module for the app.

What it declares

Every artifact

Type
Sample
Origin
Independently maintained
Use as
A reference
Runtime
Node.js
Runs on
Cloud Foundry

As a sample

Type declarations
declared
Form
does not say

Tasks this contributes to1Beta

Integrated frontend dev server1
Serve a UI5 CLI project from the CAP server while developingA UI5 app that is a UI5 CLI project, its framework resources resolved and its middlewares configured by ui5.yaml, is reachable on the CDS server's own port while the services are running, with no second server and no proxy in front.Covers, under conditionsworked example
What it does

A CAP project with the UI5 CLI app as an npm workspace under app/* and cds-plugin-ui5 as a devDependency. Its app README gives the address as http://localhost:4004/be.wl.serversiderendering/index.html after starting the CAP project, and be.wl.serversiderendering is the metadata/name in that project's ui5.yaml, so the mount path the plugin derives is visible in a running setup.

Conditions

The CAP project is started first and the app is opened on its port, as the app README instructs

Remaining work

Nothing in the repository sets the mount path or the middleware list beyond what the app's own ui5.yaml configures, and the pair of versions above is the one it pins.

All options on the Integrated frontend dev server page →

Connections5

Download
ui5-cap-serverside-rendering-demo connectionsui5-cap-serverside-rendering-demoNEEDS→ needs4needs declared The CAP Node.js runtime the project's service runs on. ui5-cap-serverside-rendering-demo — package.json, dependencies: https://raw.githubusercontent.com/lemaiwo/ui5-cap-serverside-rendering-demo/main/package.json@sap/cdsneeds declared `cds watch`, the command the README gives for running the project. ui5-cap-serverside-rendering-demo — README, Next Steps: https://github.com/lemaiwo/ui5-cap-serverside-rendering-demo ui5-cap-serverside-rendering-demo — package.json, devDependencies: https://raw.githubusercontent.com/lemaiwo/ui5-cap-serverside-rendering-demo/main/package.json@sap/cds-dkneeds declared Serves the UI5 CLI project under `app/`, an npm workspace of the CAP project, from the CDS server's own port — the address the app README gives for opening it. ui5-cap-serverside-rendering-demo — package.json, devDependencies: https://raw.githubusercontent.com/lemaiwo/ui5-cap-serverside-rendering-demo/main/package.json ui5-cap-serverside-rendering-demo — app/serverside-rendering README, starting the app: https://raw.githubusercontent.com/lemaiwo/ui5-cap-serverside-rendering-demo/main/app/serverside-rendering/README.mdcds-plugin-ui5needs declared The server half of what the project shows: the `ServerSideRendering` aspect applied to `Books` and the handler that fills the views kept in `srv/views`. ui5-cap-serverside-rendering-demo — db/schema.cds: https://raw.githubusercontent.com/lemaiwo/ui5-cap-serverside-rendering-demo/main/db/schema.cds ui5-cap-serverside-rendering-demo — package.json, dependencies: https://raw.githubusercontent.com/lemaiwo/ui5-cap-serverside-rendering-demo/main/package.json ui5-cap-serverside-rendering-plugin — README, Example: https://raw.githubusercontent.com/lemaiwo/ui5-cap-serverside-rendering-plugin/main/README.mdui5-cap-serverside-rendering-plugin→ optionally needs1optionally needs declared If: the project is run locally rather than deployed The database the project reads `db/data/my.bookshop-Books.csv` into while it is run locally. ui5-cap-serverside-rendering-demo — package.json, devDependencies: https://raw.githubusercontent.com/lemaiwo/ui5-cap-serverside-rendering-demo/main/package.json@cap-js/sqliteif

README

quoted from lemaiwo/ui5-cap-serverside-rendering-demo, read
lemaiwo/ui5-cap-serverside-rendering-demo/README.mdOn GitHub

Getting Started

Welcome to your new project.

It contains these folders and files, following our recommended project layout:

File or FolderPurpose
app/content for UI frontends goes here
db/your domain models and data go here
srv/your service models and code go here
package.jsonproject metadata and configuration
readme.mdthis getting started guide
excerpt, no licence read, read the rest, on GitHub

Details

Sources3
GitHub APIdiscovered herechecked
github.com/lemaiwo/ui5-cap-serverside-rendering-demotree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
runtimesnode
deploymentCloud Foundry
discovered viaGitHub API
first seen in the atlas
ecosystem and domaincap, ui-and-frontend-bridge
Flavors1
UI5 / Freestyle
“|**App Generator**<br>@sap/generator-fiori-freestyle|” — ui5-cap-serverside-rendering-demo — app/serverside-rendering README, application detailschecked
History in the atlas1
  1. First seen.
For your agent
Ref
artifact:lemaiwo-ui5-cap-serverside-rendering-demo
JSON
/artifacts/lemaiwo-ui5-cap-serverside-rendering-demo.json
MCP
Connecting an agent