Generated banner for Lightweight Charts React Components
Generated logo for Lightweight Charts React Components

Lightweight Charts React Components

GitHubOfficialCreated by ukorvlDistributed by GitHub

  • Skill
  • Tool integration
  • Software development
  • MIT
  • No issues found

From the author

lightweight-charts-react-components recipes for TradingView lightweight-charts in React. Candlestick, line, and area series; volume and indicator panes; realtime WebSocket updates; infinite history on scroll; crosshair OHLC legends and tooltips; trade markers and price lines; synchronized charts; numeric options and yield-curve axes. Use when adding or fixing a financial or trading chart in a React app, or when the user mentions lightweight-charts, TradingView charts in React, or this package.
— the description by ukorvl

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a set of React components and recipes for integrating TradingView's lightweight-charts library into React applications. It simplifies the management of chart lifecycles, series creation, and data updates. The library supports various chart types including candlestick, line, and area series, along with advanced features like real-time WebSocket updates, synchronized charts, and custom tooltips. It is designed to handle complex financial data requirements such as infinite history scrolling, indicator panes, and trade markers while maintaining React's declarative programming model.

What it does

  • Provides React components for rendering TradingView lightweight-charts.
  • Manages chart and series lifecycle, including creation and cleanup.
  • Supports real-time data updates via WebSocket integration.
  • Enables complex UI features like crosshair legends, tooltips, and trade markers.
  • Facilitates synchronized multi-chart layouts and custom axis configurations.
  • Handles infinite history loading and viewport management.

When to use it

  • When building financial or trading dashboards in a React application.
  • When you need to integrate TradingView lightweight-charts with React state.
  • When implementing features like real-time price updates or historical data pagination.
  • When creating complex chart layouts with indicators, volume panes, or synchronized crosshairs.

Advantages

  • Declarative component-based API for chart configuration.
  • Automatic management of chart lifecycle and DOM cleanup.
  • Built-in recipes for common financial charting patterns.
  • Flexible data handling for both static datasets and live streaming updates.

Usage examples

“How do I create a basic line chart using lightweight-charts-react-components?”
The agent provides a code snippet using the Chart and LineSeries components, demonstrating how to pass data and configure container dimensions.
“How can I implement a tooltip that shows OHLC values on hover?”
The agent provides a recipe using onCrosshairMove to track cursor position and map it to the series data, rendering a custom React tooltip.
“How do I handle infinite scrolling for historical data?”
The agent provides a pattern for using a ref-based data store and a loadOlder callback to prepend data to the chart without losing the user's current view.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/github/lightweight-charts-react-components/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip lightweight-charts-react-components.zip -d .agents/skills

Documentation by ukorvl

lightweight-charts-react-components guide

Quick Start

Let the components manage chart and series creation and cleanup. Import components and ref types from lightweight-charts-react-components; import native data, option, and event types from lightweight-charts.

  1. Check versions against the compatibility table below. Read declared ranges from the app's package.json, then the installed versions from the version field of node_modules/<package>/package.json for lightweight-charts-react-components, lightweight-charts, react, and react-dom. If the library is not installed, follow Installation. Ensure chart rendering runs in the browser, within the app's client boundary.

  2. For a basic static chart, start from the minimal chart below. Otherwise, read the reference matching the requested behavior. Adapt its feed and UI; preserve its data contract, component nesting, and API readiness handling.

  3. Choose one data owner: pass the complete dataset through data for React-owned updates, or use reactive={false} and the series API for frequent ticks.

Installation

Install the wrapper together with its lightweight-charts peer dependency, using the project's package manager. React and React DOM must already be installed.

npm install lightweight-charts-react-components lightweight-charts
Minimal chart
import type { LineData, UTCTimestamp } from "lightweight-charts";
import {
  Chart,
  LineSeries,
  TimeScale,
  TimeScaleFitContentTrigger,
} from "lightweight-charts-react-components";

// Data must be sorted ascending by time with unique times (UTC seconds here).
export function SimpleLineChart({ data }: { data: LineData<UTCTimestamp>[] }) {
  return (
    // autoSize follows the container, which needs a nonzero height.
    <Chart
      options={{ autoSize: true }}
      containerProps={{ style: { height: 300, width: "100%" } }}
    >
      <LineSeries data={data} />
      <TimeScale>
        <TimeScaleFitContentTrigger deps={[]} />
      </TimeScale>
    </Chart>
  );
}

Examples and snippets (reference files)

Read the reference matching the user's outcome. Each contains a complete TypeScript recipe, data and integration contracts, reasons for the architecture, failure modes, and acceptance checks. Combine references when a task spans several outcomes; do not load every reference for a simple chart.

User requestReference
WebSocket candles, updating the current bar, stale history, excessive chart rendersMarket data and live updates
Older history on scroll, viewport jumps, symbol/interval changes, late API responsesHistory and range selection
Candles plus volume, moving averages, oscillator panes, independent price scalesPrice, volume, and indicators
OHLC legend, hover details, missing data, tooltip positioningHover legends and tooltips
Executions and signals, stop/target levels, click-to-place price linesTrade markers and price levels
Compare assets with different prices, fixed-baseline returns, toggle comparisonsPerformance comparison
Separate charts that share scrolling, zooming, and a crosshairSynchronized charts
Trading-session shading, pane backgrounds, custom drawing that follows zoomSession overlays and primitives
Options strikes, yield maturities, choosing a numeric or custom horizontal axisNumeric axes and chart types

If no reference matches the request, tell the user that the skill has no recipe for it. Then build the solution from the public components and the upstream lightweight-charts API, applying the Quick Start rules and the edge cases below.

Skill compatibility

The recipes are verified against the reference versions below. These are the tested baseline, not the latest available releases.

If an installed version differs from the reference version, compare it with the compatibility range. Inside the range, recipes apply as written. Outside it, tell the user about the mismatch before writing code, because breaking API changes can affect the recipes, and verify every API the recipe uses against the installed package.

Dependency or environmentReference versionCompatibility range and checks
lightweight-charts-react-components2.6.1Recipe target: >=2.6.1 <3. Other versions require checking installed exports, chart API refs, and reactive data behavior before adapting a recipe.
lightweight-charts5.2.1Declared peer: >=5.0.8 <6.
React and React DOM19.2.6Declared peers: >=18.2 <20. Keep react and react-dom on matching versions and use the application's existing React instance.
Node.js—Package engines: >=18.14.0. The app's build tools can require a newer version.
Module systemESMESM import entry only; there is no CommonJS require entry.
RenderingBrowserCharts need the DOM and canvas. Render them on the client, never during server rendering.

Common edge cases

  • Chart sizing: Put DOM styles on containerProps and give the chart a nonzero height.

  • Required ancestors: Headless chart children need a chart wrapper ancestor. Markers, PriceLine, and SeriesPrimitive belong inside their series; PriceScale, Watermark, and PanePrimitive require a Pane; TimeScaleFitContentTrigger requires a TimeScale.

  • API refs and readiness: Use ref.current?.api() for the native API and containerRef for the div. For Chart, use ChartApiRef<Time, IChartApi>. .api() can initially return null; follow the recipe's readiness step before imperative setup.

  • Viewport resets: To preserve scroll/zoom, keep the chart's key stable and live/history updates out of fit-trigger dependencies. Fit on initial load or a deliberate reset. See range handling.

  • Data updates: Use data for React-owned updates, or reactive={false} and the series API when per-tick React renders are measurably costly. Avoid mixing both. Reactive data is always the complete dataset. With wrapper 2.6.1 and Lightweight Charts 5.2.1, series.data() reconstructs candle and line objects; the wrapper's earlier-item reference comparison therefore sends multi-bar tail updates through setData(), even when React keeps earlier references stable. Keep data immutable, but use the chart-owned reactive={false} recipe and explicit series.update(bar) when incremental writes are required. See live updates.

Source

Adapted from ukorvl/lightweight-charts-react-components at commit 0368191127568e48aef6f7bda2ff3900e8e24756. Original author: ukorvl. The MIT license and all nine reference recipes are retained. Local corrections in live updates reject malformed timestamps and explain the tested versions' reactive-update limitation; session overlays clarifies the primitive update callback. The other seven references and MIT notice are unchanged. This catalog copy adds source attribution and operational boundaries; it does not imply TradingView endorsement.

Recipes generate application code and can change dependencies. Follow the user's requested scope and the host's approval policy. Feed access belongs to the app's separately authorized adapter; keep credentials out of client code. Trade markers are visual annotations, not order execution or server-side alerts. Use synthetic data for local checks and report browser/feed behavior that remains untested.

Files

references/session-overlays-and-primitives.md

Session overlays and primitives

Use this for market-session shading, selected backtest intervals, maintenance windows, or custom annotations that must follow chart scrolling and zooming. The overlay should stay attached to chart coordinates rather than a DOM pixel rectangle captured once.

Choose the narrowest extension

Needed visualImplementationReason
Event on one barMarkersBuilt-in marker layout
Horizontal thresholdPriceLineBuilt-in price conversion and axis label
Background across a panePanePrimitiveIt belongs to the pane, not one series' price scale
Price-dependent drawing, series axis labels, hit testingSeriesPrimitiveNative attachment supplies the owning series
A new data series rendererCustomSeries with an ICustomSeriesPaneView pluginIt participates as a series, including data and autoscaling
New horizontal-axis semanticsCustomChartA renderer is not a horizontal-scale behavior

Recipe: reusable session bands on price and volume panes

Session boundaries are prepared by the application's market-calendar adapter as UTC-second timestamps. Do not hard-code a fixed UTC offset for exchanges that observe daylight saving time. The example shades from from to to between the centers of two loaded timeline observations; it does not extend through half a bar on either side.

This concrete plugin skips bands whose endpoints cannot be converted by timeToCoordinate(). For windows beginning outside loaded history, clip to the loaded timeline in the adapter. If the product needs exact boundaries between bars, provide an explicit boundary-to-coordinate interpolation policy instead of pretending an unknown time maps automatically.

Save this as SessionBands.ts. Inferring the draw target's type from the upstream renderer interface avoids introducing a direct runtime dependency on fancy-canvas. Media coordinate space uses CSS pixels and handles device pixel ratios through the target; bitmap coordinate space would require explicit x/y pixel-ratio conversion.

import type {
  IChartApiBase,
  IPanePrimitive,
  IPanePrimitivePaneView,
  IPrimitivePaneRenderer,
  PaneAttachedParameter,
  Time,
  UTCTimestamp,
} from "lightweight-charts";

export type SessionBand = {
  id: string;
  from: UTCTimestamp;
  to: UTCTimestamp;
  color: string;
};
type DrawTarget = Parameters<IPrimitivePaneRenderer["draw"]>[0];
type Rect = { x: number; width: number; color: string };

export class SessionBands implements IPanePrimitive<Time> {
  private rects: Rect[] = [];
  private requestUpdate: (() => void) | undefined;
  private readonly views: IPanePrimitivePaneView[];

  constructor(
    private readonly chart: IChartApiBase<Time>,
    private bands: SessionBand[]
  ) {
    this.views = [
      {
        zOrder: () => "bottom", // Shading remains behind candles and volume.
        renderer: () => ({ draw: target => this.draw(target) }),
      },
    ];
  }

  attached({ requestUpdate }: PaneAttachedParameter<Time>) {
    this.requestUpdate = requestUpdate;
  }

  detached() {
    this.requestUpdate = undefined;
  }

  setBands(bands: SessionBand[]) {
    this.bands = bands;
    this.requestUpdate?.(); // External plugin mutations need a redraw request.
  }

  updateAllViews() {
    const scale = this.chart.timeScale();
    this.rects = this.bands.flatMap(band => {
      const from = scale.timeToCoordinate(band.from);
      const to = scale.timeToCoordinate(band.to);
      if (from === null || to === null) return [];
      return [{ x: Math.min(from, to), width: Math.abs(to - from), color: band.color }];
    });
  }

  paneViews() {
    return this.views;
  }

  private draw(target: DrawTarget) {
    target.useMediaCoordinateSpace(({ context, mediaSize }) => {
      context.save();
      for (const rect of this.rects) {
        context.fillStyle = rect.color;
        context.fillRect(rect.x, 0, rect.width, mediaSize.height);
      }
      context.restore();
    });
  }
}

Save the following as SessionChart.tsx. candles and volume share the same normalized ascending UTC-second grid. A stable bands array preserves the render callback's identity. A new array intentionally recreates the primitives with the new session definition.

import { useCallback, useState } from "react";
import type { CandlestickData, HistogramData, UTCTimestamp } from "lightweight-charts";
import {
  CandlestickSeries,
  Chart,
  HistogramSeries,
  Pane,
  PanePrimitive,
  TimeScale,
  TimeScaleFitContentTrigger,
  type RenderPanePrimitive,
} from "lightweight-charts-react-components";
import { SessionBands, type SessionBand } from "./SessionBands";

export function SessionChart({
  candles,
  volume,
  bands,
}: {
  candles: CandlestickData<UTCTimestamp>[];
  volume: HistogramData<UTCTimestamp>[];
  bands: SessionBand[];
}) {
  const [showBands, setShowBands] = useState(true);
  const renderBands = useCallback<RenderPanePrimitive>(
    ({ chart }) => new SessionBands(chart, bands),
    [bands]
  );

  return (
    <section>
      <button onClick={() => setShowBands(value => !value)}>
        {showBands ? "Hide sessions" : "Show sessions"}
      </button>
      <Chart options={{ autoSize: true }} containerProps={{ style: { height: 450 } }}>
        <Pane stretchFactor={3}>
          <CandlestickSeries data={candles} />
          {/* Each invocation constructs a separate attachment instance. */}
          {showBands && <PanePrimitive render={renderBands} />}
        </Pane>
        <Pane stretchFactor={1}>
          <HistogramSeries data={volume} options={{ priceFormat: { type: "volume" } }} />
          {showBands && <PanePrimitive render={renderBands} />}
        </Pane>
        <TimeScale>
          <TimeScaleFitContentTrigger deps={[]} />
        </TimeScale>
      </Chart>
    </section>
  );
}

PanePrimitive requires a Pane ancestor; it throws outside one. A primitive can be passed as plugin or created with render, not both. The render factory receives initialized { chart, pane }; it is useful when construction needs those APIs. The wrapper attaches it and detaches it on unmount.

Identity and updating choices

The wrapper uses plugin ?? render identity as the attachment identity. A new plugin object or callback detaches the previous instance and attaches a new one. Do not inline a new factory on every pointer move or tick. The recipe memoizes it by the session definition, so intentional definition changes recreate it. Do not reuse one stateful plugin instance across two panes/charts: its attached state and redraw callback belong to one attachment.

For frequent changes, create a stable plugin and call its own setBands() method through an application-owned instance or ref. The wrapper's primitive ref exposes the upstream interface, not custom methods; keep the concrete plugin typed in application code when calling those methods. setBands() above requests a redraw; changing a class field without that request need not repaint immediately.

Compute coordinates in updateAllViews(), then draw the cached views. Upstream invokes this during relevant chart updates, so scrolling/zooming refreshes the geometry. Do not calculate x once in a React effect and retain it through zoom. If the plugin subscribes to external events, unsubscribe in detached() using the same handler identity. This recipe has no custom event subscriptions.

Series-specific drawings and custom-series boundaries

For a vertical event line with a time-axis label, use a SeriesPrimitive under the target series. Implement ISeriesPrimitive.updateAllViews() to recalculate and cache chart.timeScale().timeToCoordinate(time), or delegate that work to a pane view's own update() method. Lightweight Charts invokes the primitive's updateAllViews() callback during chart updates. Return one IPrimitivePaneView whose renderer fills a full-height rectangle in bitmap coordinate space (scale x and width by horizontalPixelRatio), plus one ISeriesPrimitiveAxisView from timeAxisViews() for the label. Format the label explicitly for UTC timestamps or business dates; .toString() on a BusinessDay object does not give a useful date. The SeriesPrimitive render factory receives { chart, series }; use the series API for price conversion when drawing price-dependent shapes.

For grouped volume bars or a genuinely new plot type, use CustomSeries with a plugin implementing upstream ICustomSeriesPaneView. The plugin supplies renderer, update, priceValueBuilder, isWhitespace, and defaultOptions. The price-value builder must include all values that should participate in autoscaling. Keep custom payloads in customValues and preserve the custom data shape when updating. CustomSeries requires a plugin instance; CustomChart instead changes the horizontal scale and is a different extension.

Acceptance checks

  • Pan, zoom, resize, and change device pixel ratio: bands remain attached to the intended bars and fill only their owning pane.

  • Toggle sessions on/off repeatedly and change the bands array. Old attachments disappear and no stale background persists.

  • Test missing/off-history endpoints and zero-width intervals against the stated clipping policy. Verify daylight-saving changes in the calendar adapter.

  • For an external plugin update, call setBands() and verify it repaints without requiring the user to move the chart. Confirm each pane has its own instance.

Requirements and compatibility

Written for: GitHub Copilot

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs Node.js

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
ukorvl
Publisher
GitHub (Official)
Distributed by
GitHub
Source
github/awesome-copilot · skills/lightweight-charts-react-components · commit 797337f
Licence
MIT License (redistribution allowed)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by ukorvl or GitHub.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download lightweight-charts-react-components.zip