Compatibility and supported scope
What the runtime supports, and how to tell implemented APIs from legacy declarations.
The runtime covers real, everyday charting workflows, and its browser namespace is LumenChartingLibrary. This page explains how to tell what's supported.
Reading the API reference
The API reference sorts types into three kinds:
- Facades the runtime actually implements.
- Interfaces that your app implements.
- Types that exist only in the declarations for compatibility.
A signature in a declaration file doesn't mean there's a broker connection, an external cloud service or a full indicator catalog behind it.
To see what your loaded runtime supports, call widget.getAllFeatures(), widget.supportedChartTypes() and widget.getStudiesList(). The catalogs in these docs list the tools and indicators the runtime includes. If someone passes an unsupported input, treat it as an error. Don't quietly swap in a different feature.
Who handles what
| Capability | Handled by |
|---|---|
| Historical and realtime bars | Your datafeed |
| Chart rendering and supported tools | The chart runtime |
| Layout storage and access control | Your adapter and backend |
| Order ticket, account manager and on-chart orders | The trading runtime, after loadTrading() |
| Placing broker orders | Your broker adapter (drawings and annotations don't place orders) |
| Pine worker and editor | Optional assets that you turn on |
| Pine cloud publishing and alerts | Providers you configure (drawing Pine locally is not cloud delivery) |
| Layouts saved by other chart libraries | Not guaranteed to work with this runtime's formats |
Release identity
The legacy version() string tells you which version line the runtime is compatible with. To identify the exact files you shipped, use the manifest digest shown on the releases page. Always ship the wrapper, iframe, styles and worker together.
The demo uses sample data and stores things in your browser only. It makes no promises about market data uptime, financial accuracy or saving to a server.