Successor: @pond-ts/charts (canvas React charts on pond-ts, by the original author)

I wrote react-timeseries-charts while I was at ESnet, and I'm opening this so anyone who lands here has a pointer to where the work went.

react-timeseries-charts hasn't had a release since 0.16.1 (May 2019), it depends on Pond.js 0.8/0.9 which is likewise unmaintained, and it renders through SVG/DOM, which is the ceiling most of the open performance issues here run into. Typescript support was always marginal.

The successor is [@pond-ts/charts](https://github.com/pond-ts/pond/tree/main/packages/charts). It has a very similar API (ChartContainer → ChartRow → layers → YAxis etc), is rebuilt on a canvas data plane, reads a [pond-ts](https://github.com/pond-ts/pond) TimeSeries or streaming LiveSeries directly (Pond-ts is fully rewritten, highly optimized replacement for pondjs). Line, area, band, bar, scatter, box plot, candlestick and heat-map layers; time, value and category axes; cursors, selection, pan/zoom, annotations; trading-time axes. Full Typescript support. It should do most of what react-timeseries-charts does and a lot more, with much better performance.

npm: @pond-ts/charts (peers on pond-ts, @pond-ts/react, React 18+)
docs: https://pond-ts.org/docs/charts/
Walkthrough: https://pond-ts.org/docs/learn-charts
Large-series rendering guide: https://pond-ts.org/docs/how-to-guides/rendering-large-series

It is pre-1.0, MIT, and actively maintained. It is not an ESnet project and I'm not speaking for ESnet. This is the original author pointing at the continuation.

Ask for the maintainers: a one-paragraph note at the top of the README (I'll open a PR with exactly that), and/or archiving this repository with the pointer in the description. Migration questions are welcome as issues on the pond-ts repo.

Review the repository README and description alongside the linked @pond-ts/charts documentation. Confirm whether the maintainers want a successor note at the top of the README, repository archiving with a description pointer, or both; done means the chosen pointer is accurate and clearly directs users to the maintained project.

Written by the indexing model from the issue text.