Build and dev-server tooling

SAP's UI5 Web Components documentation ships the components as ES6 modules across npm packages, with no CDN, and has the app import and bundle only what it uses through whichever ES6-capable bundler it already runs, naming Vite as the starting point when there is no existing choice.

Not covered: It stops at the packages themselves: the documentation has the app's own bundler do the build, not UI5 Tooling@ui5/clicliThe UI5 Tooling command line for project setup, the local dev server and the build, which defines a UI5 project's shape and its two extension points, custom middleware and custom tasks.sap official, ui5's dev server or custom-task extension points. ui5-tooling-modulesui5-tooling-modulesbuild-toolA set of UI5 tooling extensions that load and convert plain npm packages into UI5 AMD-like modules, so the UI5 module loader can consume them.community org, ui5, a UI5-door project that states Web Components for this capability, runs the other way — loading @ui5/webcomponents packages into a UI5-Tooling build rather than building a Web Components app.