Vela, our next-generation charting platform, is live at vela.luxalgo.com.
LuxAlgo

Requirements

Browser support, Content-Security-Policy rules, build tooling, bundle sizes, and backend interfaces for Vela Pro.

View as Markdown

Vela Pro runs entirely in the browser and installs as standard npm packages built from your repository clone. Before starting, verify your target browsers, build toolchain, and the data and backend interfaces your application will supply.

Browser support

The renderer in Vela's open-source core draws with WebGL2 and falls back to Canvas 2D automatically when WebGL2 is unavailable. Two workspace and chart options control backend selection:

OptionDefaultBehavior
nativeBackend'auto'Uses WebGL2 when supported and falls back to Canvas 2D otherwise. Pass 'canvas2d' or 'webgl2' to force a specific renderer.
maxWebglCells8Switches all cells in a multi-chart grid to Canvas 2D once cell count exceeds this limit, avoiding browser WebGL context exhaustion. An explicit nativeBackend value overrides this threshold.

The UI kit requires browsers with CSS color-mix() support, specifically Chrome 111+, Edge 111+, Firefox 113+, and Safari 16.2+ (see Writing a component). The installation and examples in this section were verified in Microsoft Edge 157. Test across every browser your product targets.

By default, workspace layouts and module state persist in localStorage.

Web Workers and Content-Security-Policy

By default, Vela Pro executes each chart's Pine Script® studies inside a dedicated Web Worker so compute-heavy scripts do not block main-thread rendering. Because the worker bundle is inlined in the package and spawned from a Blob URL, you do not need to host a separate worker asset, while any Content-Security-Policy header must permit worker-src blob:.

If worker-src blob: is blocked by CSP, the chart still renders candles, the browser console logs Creating a worker from 'blob:...' violates the following Content Security Policy directive, and scripts produce no plots. When your CSP cannot allow blob: workers, switch the Pine Script® engine to main-thread execution:

import { enableVelaPro } from '@luxalgo/vela-pro';

enableVelaPro({ pineEngine: { engine: 'inprocess' } });

In 'inprocess' mode, scripts execute on the UI thread and heavy calculations block interaction while running. The Pine code editor spawns its language worker from a Blob URL the same way and exposes a workerUrl option for strict CSP policies, documented in Pine code editor.

Build tooling

RequirementNotes
Node.js and npmRequired to build the repository clone and install tarballs. Verified with Node.js 24.18 and npm 11.16 (packages declare no engines constraint).
ES module bundlerModule packages publish ES modules only, and all packages resolve entry points via package.json exports maps. Verified with Vite 8 and Next.js 16.
TypeScript (optional)Type declarations ship inside every package. Configure moduleResolution to an exports-aware mode such as bundler (verified with TypeScript 6.0 and 7.0).
UI framework (optional)Workspaces mount into any DOM element. Integration guides cover React, Next.js, and Vue.

In a Vite production build of the Quickstart setup, the initial entry bundle is approximately 4.1 MB uncompressed (1.1 MB gzipped). The Pine code editor splits into separate chunks totaling roughly 4.6 MB uncompressed, loaded on demand only when a user opens the editor panel.

Data and backend services

Vela Pro executes rendering, charting logic, and UI state in the browser while delegating market feeds, persistence, and order routing to your services. Without custom backends configured, Vela Pro runs locally against localStorage and a simulated paper trading account.

Service interfacePurposeDefault behavior until connected
Data providerHistorical candles, symbol resolution, and live bar updates. See Data connectivity and Custom data providers.Develop against the core's built-in public providers (Binance, Coinbase, Hyperliquid).
Order-flow feedSupplies per-bar bid/ask slices to the Footprint chart type and order-flow indicators. See Footprint data.Footprint charts draw no cells, and order-flow indicators are omitted from the indicator menu.
Market depthSupplies order books and trade tape streams to the Order Book module. See Quotes and market depth.The Order Book panel displays "No order book".
Server-side storagePersists layouts, drawings, watchlists, alerts, and journal entries on your backend. See Server-side storage.Saved in localStorage within the current browser.
Broker integrationRoutes live orders, positions, and fills for the Trading module. See Broker integration.Trading runs against the built-in PaperBroker simulation account.
Calendar sourceSupplies economic releases, earnings, and corporate events to the Calendar module. See Calendar.The Calendar panel renders empty.

Cloning and building Vela Pro also requires an active developer seat on your commercial license, covered in Repository access.

On this page