Approved libraries

Code components and Code Builder apps can only use the libraries on Praisma's allow-list. Praisma serves the exact pinned files itself. Never add a script tag, a CDN link or an import from a URL, and never paste library code into your source.

The list

three0.186.1, globalTHREE: 3D graphics with WebGL, scenes, meshes, lights, shaders, particles, GLB/glTF loading.

gsap3.13.0, globalgsap: tweens, timelines, staggers and easing. In a code component only the core is available (no ScrollTrigger, since the component lives in its own frame).

lottie5.13.0 (light build), globallottie: plays Lottie JSON animations with the SVG renderer; expressions do not run.

chartjs4.5.1, globalChart: line, bar, pie, doughnut, radar and scatter charts on a canvas, ready to use.

react19.2.3: added automatically for React components; never declare it on a plain-JavaScript component.

In a plain-JavaScript component

Declare the libraries in the definition and use their globals:

{ "type": "sales-chart", "libraries": ["chartjs"], ... } // behavior_js var chart = new Chart(canvas, { type: "bar", data: data }); return function () { chart.destroy(); };

For 3D models, use new THREE.GLTFLoader() with a media prop holding a GLB file from your media library. Set crossOrigin = "anonymous" on WebGL textures.

In React (components and Code Builder apps)

import * as THREE from "three"; import { GLTFLoader } from "three/addons/loaders/GLTFLoader.js"; import { gsap } from "gsap"; import lottie from "lottie-web/build/player/lottie_light"; import Chart from "chart.js/auto";

In an HTML Code Builder project

Reference the vendored file with a relative path; the platform adds it to the build:

<script src="./vendor/three.min.js"></script> <script src="./vendor/gsap.min.js"></script> <script src="./vendor/lottie_light.min.js"></script> <script src="./vendor/chart.umd.js"></script>