{"full_name":"tradingview/lightweight-charts","owner":"tradingview","name":"lightweight-charts","shard":"1","url":"https://github.com/tradingview/lightweight-charts","description":"Performant financial charts built with HTML5 canvas","homepage":"https://www.tradingview.com/lightweight-charts/","topics":["financial-charting-library","charting-library","html5-charts","canvas","typescript","charting","charts","finance","javascript"],"tag_pages":["canvas","charting-library","charts","finance","javascript","typescript"],"language":"TypeScript","license":"Apache-2.0","avatar":"https://avatars.githubusercontent.com/u/7644688?v=4","created_at":"2019-05-24T14:41:49Z","pushed_at":"2026-11-13T13:24:59Z","metrics":{"stars":17862,"forks":2713,"watchers":203,"issues":1191,"prs":696,"releases":51,"issues_open":100,"issues_closed":1091,"prs_open":5,"prs_closed":119,"prs_merged":572,"discussions":213},"growth":{"day":{"stars":6,"forks":4,"base_day":"2026-11-15"}},"history":{"dates":["2026-11-10","2026-11-11","2026-11-12","2026-11-13","2026-11-14","2026-11-15","2026-11-16"],"stars":[17836,17837,17841,17842,17850,17856,17862],"forks":[2699,2703,2704,2706,2706,2709,2713],"watchers":[null,205,205,205,203,203,203],"issues_open":[null,102,101,101,100,100,100],"prs_open":[null,12,7,5,5,5,5]},"boards":{},"same_owner":[],"issues":[{"number":621,"title":"Price scale API to get/set price range","comments":20,"created_at":"2020-11-16T18:15:55Z"},{"number":699,"title":"Add option to do not connect a line/area between data gap","comments":13,"created_at":"2021-02-11T00:45:06Z"},{"number":1933,"title":"When adding a small amount of data and subscribing using subscribeVisibleTimeRangeChange, the graph crashes.","comments":10,"created_at":"2025-07-30T12:16:46Z"},{"number":944,"title":"Refactor hovering/hit test system API","comments":10,"created_at":"2021-12-17T16:21:32Z"},{"number":1875,"title":"[👾] setData Causes Visible Range Jumps and Disrupts Smooth Scrolling in Lightweight Charts","comments":9,"created_at":"2025-04-28T02:26:40Z"},{"number":1990,"title":"Series Markers misaligned on new bar","comments":7,"created_at":"2025-10-15T14:58:34Z"},{"number":1380,"title":"Width problem and persian prices","comments":7,"created_at":"2023-06-18T12:21:01Z"},{"number":1747,"title":"Chart is getting hidden if resized too small ","comments":6,"created_at":"2024-12-01T19:09:37Z"}],"discussions":[{"number":2177,"title":"HTS for Mac: a read-only Korean/US stock workspace for macOS built on Lightweight Charts","comments":0,"category":"Show and tell","created_at":"2026-10-28T00:45:07Z"},{"number":2109,"title":"Request for clarification on commercial use and attribution requirements for Lightweight Charts 5.2","comments":0,"category":"Q&A","created_at":"2026-07-28T10:09:10Z"},{"number":2093,"title":"Adjusting the price scale","comments":1,"category":"Q&A","created_at":"2026-06-06T14:33:10Z"},{"number":2091,"title":"CandleKit — all-in-one toolkit: drawing tools, indicators, replay engine, measurement ruler, multi-pane sync, broker integration (MIT)","comments":0,"category":"Show and tell","created_at":"2026-06-05T08:13:36Z"},{"number":2089,"title":"TV Logo Disabling Procedures","comments":0,"category":"General","created_at":"2026-05-04T14:41:57Z"},{"number":2078,"title":"Custom marker shape (✕ cross) for loss trades — is it possible?","comments":2,"category":"Q&A","created_at":"2026-04-17T00:59:39Z"},{"number":2074,"title":"SuiBets — Using Lightweight Charts for Crypto Sports Betting Platform","comments":0,"category":"Show and tell","created_at":"2026-04-03T01:22:42Z"},{"number":2056,"title":"How to make panes separators look the same?","comments":1,"category":"General","created_at":"2026-01-27T20:08:26Z"}],"latest_release":{"name":"v5.3.0","tag":"v5.3.0","published_at":"2026-11-10T14:47:38Z","body":"**Enhancements**\r\n\r\n- Added `hitTestTolerance` option to `PriceLineOptions`, which controls how many pixels beyond a price line's stroke still count as a hit when hovering. This was previously fixed at 7px, so closely stacked price lines could register hovers for their neighbours. The default stays at `7`, matching the previous behaviour, and the name matches the series-level `hitTestTolerance` option. (PR [#2081](https://github.com/tradingview/lightweight-charts/pull/2081), fixes [#1610](https://github.com/tradingview/lightweight-charts/issues/1610), contributed by [@sahil-tandon](https://github.com/sahil-tandon))\r\n- Improved curved line rendering (`LineType.Curved`) by replacing the Catmull-Rom interpolation with the Fritsch-Carlson monotone algorithm. The curve no longer overshoots the values of neighbouring points, so flat sections stay flat without spikes. Curved lines will look slightly different from previous versions. (PR [#2108](https://github.com/tradingview/lightweight-charts/pull/2108), fixes [#1680](https://github.com/tradingview/lightweight-charts/issues/1680), contributed by [@edew](https://github.com/edew))\r\n\r\n**Bug Fixes**\r\n\r\n- Business day strings must now be in the zero-padded `YYYY-MM-DD` format in all builds. The production build previously skipped the format check that the development build performs, and the browser parsed strings such as `'2024-1-5'`, `'2024/01/05'` or `'Jan 5 2024'` as local time. For users in timezones ahead of UTC, these points were plotted one day early. Such strings now throw an error in all builds, as they already did in development builds. If your data uses these formats, zero-pad it to `'YYYY-MM-DD'` or pass a `BusinessDay` object (`{ year, month, day }`) instead. (PR [#2189](https://github.com/tradingview/lightweight-charts/pull/2189))\r\n- Fixed `series.update(item, true)` (historical update) overwriting the next bar when the series had no bar at the target time, for example when that time was a whitespace item or only existed because another series had a bar there. The new bar is now inserted at the target time, and a whitespace update at such a time no longer removes the next bar. (PR [#2194](https://github.com/tradingview/lightweight-charts/pull/2194))\r\n- Fixed the time scale jumping when new bars are added while the user is dragging the chart. (PR [#2157](https://github.com/tradingview/lightweight-charts/pull/2157), fixes [#1521](https://github.com/tradingview/lightweight-charts/issues/1521))\r\n- Fixed animated time scale scrolls (`scrollToRealTime()`, `scrollToPosition(x, true)`) stopping one frame short of their target. The final position varied between runs and, if the first animation frame arrived after the whole duration (for example in a background tab), the view didn't move at all. Kinetic scrolling had the same final-frame skip. (PR [#2174](https://github.com/tradingview/lightweight-charts/pull/2174))\r\n- Fixed `setVisibleLogicalRange()` and `setVisibleRange()` collapsing the requested range when zoomed in to fewer bars than the minimum visible bars count (only possible with an increased `maxBarSpacing`). (PR [#2155](https://github.com/tradingview/lightweight-charts/pull/2155), fixes [#1924](https://github.com/tradingview/lightweight-charts/issues/1924), contributed by [@komagic](https://github.com/komagic))\r\n- Fixed the chart becoming empty, with `getVisibleLogicalRange()` returning `null`. This happened when `setData()` was called twice with identical times on the only series, and then a second series was added and `setData()` was called again. (PR [#2158](https://github.com/tradingview/lightweight-charts/pull/2158), fixes [#2154](https://github.com/tradingview/lightweight-charts/issues/2154), contributed by [@YodHeVauHe](https://github.com/YodHeVauHe))\r\n- Fixed a series not being drawn when all of its visible values were equal and very large (around `1e15` and above). The range extension used to keep the price scale usable was smaller than the floating-point spacing ","is_prerelease":false},"readme":true,"readme_zh":false,"news":[],"stale":false,"snapshot_at":"2026-11-16T09:23:14Z","history_start":"2026-09-06"}