web-abap2UI5

Functionality

• Downporting with abaplint
• Transpiling to JS with abaplint/transpiler
• Running on Node.js with open-abap
• Service exposing via express-icf-shim

Tasks

Downport & Transpile

npm run init
npm run build

Run Unit Tests

npm run unit

Run Webservice

npm run express

Webpack Build Strategy

1. Clone repositories into /src/
2. Downport /src/ into /downport/
3. Transpile with express-icf-shim into /output/
4. Webpack backend + database into folder build

npm run webpack:build

The bundle contains no static frontend copy: at runtime app/web.mjs initializes the transpiled backend, issues an in-memory HTTP GET against it (the same z2ui5_cl_http_handler GET that serves real systems, including the sap.ui.require.preload of the complete current UI5 frontend) and document.writes the returned page. Frontend and backend are therefore always the versions cloned that day. The backend's Content-Security-Policy meta tag is stripped from the written page — it is designed for server-served deployments (no unsafe-eval/wasm-unsafe-eval) and would break the wasm/eval-based in-browser runtime while protecting nothing here.

Test the build locally (webpack-dev-server HMR does not work with the document.write boot):

npm run serve:build

Demo

Backend Running in Browser https://abap2ui5.github.io/web-abap2UI5-build/

CI

The build_web workflow runs daily: it clones abap2UI5 and the top-level apps of samples, runs downport, transpile, unit tests and the webpack build, and deploys the result to web-abap2UI5-build (GitHub Pages). Note: GitHub disables scheduled workflows after 60 days without repository activity — re-enable it under Actions if the demo stops updating.

@abaplint/cli is pinned to the version used by abap2UI5 itself, since the downport result must pass the same syntax check.

Limitations & Todo

• Samples in subfolders of the samples repository (system samples, launchpad samples) are excluded — they require a real SAP system and cannot be transpiled
• A known upstream @abaplint/transpiler issue makes check_on_init( ) always false in the transpiled backend (interface attributes read through an interface-typed reference resolve to a missing JS property), so backend-built view XML may not be returned even though the roundtrip succeeds

Credits

• abaplint, open-abap, express-icf-shim, webpacking by larshp