COMS Micro-Frontends 1.1.2

The URLs to all static assets have the structure /{component}/{version}/{asset*}, e.g., /tef-coms/v2/tef-coms.js.

{component} is the name of the custom element (equals the name of the npm package), i.e., tef-coms or tef-coms4cs.

{version} is either a SemVer-compliant full version, e.g., v2.0.0 or v3.0.0-beta.1. Or it is an unspecific version, e.g., v2 or v2.1 or latest, which is redirected to the highest matching specific version (http status code 302), if available, first matching stable versions, second matching prerelease versions. When referring to static assets, e.g, in an html <script> tag, please make sure to refer to major versions only, e.g., /tef-coms/v2/tef-coms.js, to automatically update to new patch and minor versions.

The previously used URLs /v2/tef-coms.js and /4cs/v1/tef-coms4cs.js are deprecated. They are redirected to their new equivalents (http status code 301). For performance reasons, of course, it is recommended to no longer use them.

All static assets are configured to be cached by the browser or any other cache for 1 hour (see cache-control headers). With the exception of the develop environment where caching is disabled.

In addition to static assets, there are npm packages available, e.g., npm install tef-coms --registry https://art02.sg.de.pri.o2.com/artifactory/api/npm/npm/. So far, this is only useful for Typescript projects looking for type information. In production, however, please directly load the micro-frontends with a <script> tag.

tef-coms

COMS micro-frontend for customers.

latest | v2 | v2.16.4 | v2.16.3 | v2.16.2 | v2.16.1 | v2.16.0 | v2.15.3 | v2.15.1

tef-coms4cs

COMS micro-frontend for customer service.

latest | v1 | v1.13.1 | v1.13.0 | v1.12.2 | v1.12.0 | v1.11.0