Kaiya App Libraries

When Kaiya generates an App, the generated code can call on third-party JavaScript libraries such as a mapping library, a charting library, a rich text editor. Under Settings → Intelligence → Kaiya & AI → Kaiya App Libraries, admins can register those libraries so generated Apps can actually load them at runtime.

A common set of npm libraries is already bundled with each Tellius release, so you don't need to upload those. This page is for anything beyond that set: custom libraries specific to your organization's apps, or ones not covered by the default bundle.

Libraries uploaded here are stored on the Tellius CDN and shared across three places at once — the Kaiya Apps preview, Settings, and the TSX generator. One upload covers all three; you don't register a library separately per surface.

The libraries list

Registered libraries appear in a list on this page. Before anything is uploaded, the area reads No libraries configured yet.

From the list you can enable a library, disable it, or remove it. Disabling is the safer first step when you suspect a library is causing problems, since it leaves the files in place.

Uploading a library

Click Upload library. It expects a UMD JavaScript bundle plus any companion assets it needs, so generated apps can reference the library at runtime.The dialog has two parts: a file drop zone and a name field.

Drag files onto the drop zone, or click it to browse. The limits are 20 files per library, 5 MB each, and the accepted types are .js, .css, fonts, images, and .map.

A library is usually more than one file, so upload everything it needs in a single go. The dialog spells out what each file type is for:

File type	Extension	When you need it
JavaScript bundle	.js	Required. The UMD build of the library. This is what registers the global names that generated apps reference at runtime.
Stylesheet	.css	Needed only when the library ships visual styles — chart themes, editor toolbars, map controls. Without it, components still render but appear unstyled.
Fonts	.woff, .woff2, .ttf, .otf, .eot	Include only when the stylesheet calls for custom typography, such as an icon font. Otherwise glyphs fall back to system fonts.
Images & icons	.png, .jpg, .svg, .gif, .webp	Include any icons, sprites, or illustrations the library or its stylesheet loads at runtime.
Source maps	.map	Optional. Helps when debugging the library in browser devtools, and safe to skip in production.

The UMD build requirement is the part worth getting right. UMD (Universal Module Definition) is the build format that exposes the library under a global name rather than requiring an import statement. A library published only as an ESM or CommonJS build won't register correctly here. Most libraries ship a UMD file in their dist folder, often named something like library.umd.js or library.min.js.

Library name

Type a name in the Library name field. This appears in the libraries list and in app build logs.

Click Upload library to register it, or Cancel to discard. The Upload library button stays inactive until you have both attached at least one file and entered a name.