Browser bundle
Sigma ships a standalone UMD bundle (sigma.min.js) for usage without a package manager, typically through a CDN:
<script src="https://cdnjs.cloudflare.com/ajax/libs/sigma.js/4.0.0-beta.3/sigma.min.js"></script>It exposes a single global: Sigma, the same class as the npm package’s default export. That class also carries,
as static properties, basically everything the npm package exports, each thing kind of at the right place:
- The values exported by the main
sigmaentrypoint sit directly on the class:Sigma.Camera,Sigma.DEFAULT_STYLES,Sigma.DEFAULT_CAMERA_STATE, etc. - The subpath entrypoints (
sigma/rendering,sigma/utils, etc.) sit on namespaces of the same name:Sigma.rendering,Sigma.utils, etc.
For instance, drawing edges as curves uses pathCurved from sigma/rendering:
// ESMimport { pathCurved } from "sigma/rendering";
// Browser bundleconst { pathCurved } = Sigma.rendering;The definitive list is the bundle’s entrypoint itself, which is short and readable:
packages/sigma/src/index-bundle.ts.
The symbols themselves are documented in the API reference.
Limitations
- Type-only exports (interfaces, type aliases) do not exist at runtime, so they have no browser bundle counterpart.
- The bundle includes the whole library. For production applications where size matters, prefer the npm package, so your bundler can tree-shake unused code.