Written by Huifer, solo developer and maintainer of TanStack Ship. I keep a short upgrade notebook for every charting dependency in my templates, because the charts my customers see — revenue lines, usage bars, retention curves — are the first thing a churned user screenshots. A silent renderer change in a charting library is the kind of bug you only notice after a support ticket.
Verified sources: TanStack · TanStack Charts · TanStack Charts on GitHub ·
@tanstack/react-charts1.3.0 on npm · web.dev · Cloudflare DevelopersLast updated: 2026-11-06
@tanstack/react-charts 1.3.0 is published on the npm registry under the package name @tanstack/react-charts, and the registry record points its source at the official git+https://github.com/TanStack/charts.git repository. The verified record confirms the version exists and where it comes from; this guide explains how to upgrade it safely and how to confirm what you already have installed — because the registry facts I reviewed do not include a feature changelog, a publish date, or a quote, so I will not invent those here.
TL;DR
- Measured:
@tanstack/react-charts@1.3.0is published on npm; the registry entry lists the package and points togit+https://github.com/TanStack/charts.git.- Measured: the maintained source lives at the official TanStack/charts repository on GitHub.
- Measured: the registry facts I used contain no feature list, release date, or maintainer quote — so this article describes verification and upgrade steps, not new features.
- Estimated: treat any charting-library bump as requiring a re-render check of your existing charts, because a charting dependency affects dashboards and reports.
- User-provided: none — every fact above comes from the public npm record or the official repository, not from a customer or a dashboard.
Short answer:
@tanstack/react-charts1.3.0 is a published release of TanStack's React charting library on npm. The registry record confirms the version and its official source repository; it does not include a feature list, so verify new behaviour against the official release notes before upgrading.
TanStack React Charts 1.3.0: What's New and How to Upgrade
This guide is for two people. First, the developer who has @tanstack/react-charts pinned in a lockfile and just got an upgrade ticket. Second, the founder evaluating a SaaS starting point who wants to know whether the charting layer in a template is actually maintained or a hand-rolled SVG that nobody owns. If you are in the first group, jump to the upgrade checklist. If you are in the second, read Which template capability this release supports and skip the rest.
Everything below is anchored to the npm registry record for @tanstack/react-charts@1.3.0 and the official repository. Where the record is silent, I say so instead of filling the gap from memory.
What the npm Registry Record Actually Confirms
The single source of truth for "did 1.3.0 ship, and from where?" is the published registry metadata. Here is what it proves.
The package and its official source
| Registry field | Value in @tanstack/react-charts@1.3.0 |
|---|---|
| Package | @tanstack/react-charts |
| Version | 1.3.0 |
| Source repository | git+https://github.com/TanStack/charts.git |
| Official page | registry.npmjs.org/@tanstack/react-charts/1.3.0 |
| Upstream org | TanStack on GitHub |
That table is the whole of what the registry facts I was given confirm. The repository field is the important one operationally: a version published by the official TanStack/charts org is the same source line you would review on GitHub, which is what makes an upgrade auditable.
What the record does not contain
I want to be specific about the gap, because "release guide" usually implies a feature list and I am deliberately not writing one:
- No feature changelog. The facts file's README excerpt is empty, so there is no documented list of what changed in 1.3.0 in the source I reviewed.
- No publish timestamp. Unlike releases where the registry payload carries a publish time, the facts I used did not include one, so I will not state a date.
- No maintainer quote or benchmark. Nothing in the record supports a performance or migration claim.
If you need the actual delta, the authoritative place is the TanStack/charts repository's release notes and the official Charts docs. I link those rather than paraphrase them, because paraphrasing an empty record would mean inventing it.
What's New in 1.3.0 — and What the Record Does Not Say
Why I'm not listing features from memory
A charting release can change axis behaviour, tooltip rendering, or the headless core that the React wrapper depends on. Any of those would matter to your app. But the verified facts for 1.3.0 do not describe them, and the rule for this article is strict: anchor every release claim in the facts file; never invent release details. So the honest "what's new" answer is: the registry confirms 1.3.0 exists and where it comes from; it does not document the feature delta in the record I was given.
Where to find the real changelog
To learn what actually changed, go to the source, not a summary:
- Open the official
@tanstack/react-charts1.3.0 record on npm and read the version's own metadata. - Open the TanStack/charts releases page on GitHub for the tagged notes.
- Read the TanStack Charts documentation for any API or prop changes referenced in the notes.
Treat those three as the canonical references. Anything else — including this article — is a verification aid, not the changelog.
How to Upgrade @tanstack/react-charts to 1.3.0
You do not need a feature list to upgrade safely. You need to know what you have, change it in one commit, and re-render your charts.
Step 1 — Check your currently installed version
Before bumping, confirm what is actually resolved in your tree:
# What version of the charting package is installed right now?
npm ls @tanstack/react-charts
# Or read it straight from node_modules
node -p "require('@tanstack/react-charts/package.json').version"
# Show whether a newer version is available
npm outdated @tanstack/react-charts
If npm ls shows a version you did not expect (a transitive pin from another package, for example), that is the thing to resolve before the bump, not after.
Step 2 — Bump the package in one commit
Change the version, then commit the lockfile with it. A version that lives in package.json but not in the lockfile is not an upgrade:
{
"dependencies": {
"@tanstack/react-charts": "1.3.0"
}
}
After editing, reinstall so the lockfile catches up, then re-run the check from Step 1 to confirm the tree now resolves 1.3.0:
npm install
npm ls @tanstack/react-charts
If your project depends on a headless core that the React wrapper sits on top of, bump that in the same commit too — but only after the official notes confirm the exact compatible version. The registry facts I reviewed did not state a companion package version, so I am not asserting one here.
Step 3 — Re-render your charts before shipping
A charting bump is one of the few upgrades where "it compiles" is not "it works." Re-render the charts your users actually see — dashboards, billing reports, admin screens — and confirm axes, tooltips, and legends look right. If you want this to run without a human eyeballing it, a tiny pre-deploy guard catches a missing or unexpected version:
// scripts/check-charts-version.ts — run in CI before a deploy
import { readFileSync } from 'node:fs'
const pkg = JSON.parse(readFileSync('package.json', 'utf8'))
const installed = pkg.dependencies?.['@tanstack/react-charts']
if (installed !== '1.3.0') {
console.error('Expected @tanstack/react-charts 1.3.0, found:', installed)
process.exit(1)
}
console.log('@tanstack/react-charts aligned:', installed)
Which Template Capability This Release Supports
A charting layer is not a feature you bolt on at the end — it is the surface your users stare at when they ask "is the business doing okay?" The buyer question this release informs is concrete: does the template you are evaluating ship a maintained, source-auditable charting library, or a hand-rolled SVG that nobody owns?
Three things separate a real charting setup from a bespoke one, and they are exactly what a versioned, officially-sourced package like @tanstack/react-charts gives you: the source is traceable to the official TanStack/charts repository, the upgrade path is a single auditable version bump rather than a fork, and the behaviour is documented in the official Charts docs instead of living in one engineer's head.
That is why, when I see which SaaS templates ship a maintained charting layer, the data-visualization row is one I check early: a template that ships a charting dependency with no clear upgrade story, or a bespoke chart nobody maintains, will cost more in the first month than it saves at purchase. To see a coherent setup in a finished app, browse the templates and check how the charts are wired before anything else. The caveat: a well-versioned upstream library does not by itself prove version discipline in a product built on top of it.
Limitations and Disclosure
Claim types used here. Measured means read directly from the npm registry record or the official repository field. Estimated means my judgment about upgrade risk. User-provided means nothing: no metric in this article came from a customer, a dashboard, or a third party. Calculated and proxy claims do not appear, because the record I reviewed carried no numbers to calculate or proxy from.
What I did not do. I did not describe new features, performance gains, or migration steps for 1.3.0, because the registry facts I was given contain no changelog, date, or quote to anchor them in. I also did not benchmark anything, because there is no documented behaviour change in the record to benchmark. If the maintainers shipped a change the registry payload does not surface, this guide will not show it — check the TanStack/charts repository for the source diff and release notes.
Disclosure. I maintain TanStack Ship, and the templates linked above are my own products. I have no material connection to any third party named in this article, and this post is not a substitute for reading the official release notes.
Conclusion and Next Step
@tanstack/react-charts 1.3.0 is a real, source-auditable release on npm: the registry confirms the version and its official origin, even though the record I reviewed does not document the feature delta. Upgrade it the same careful way you would any charting dependency — confirm what you have, bump it in one commit with the lockfile, and re-render your charts before you ship.
Next step: see which SaaS templates ship a maintained charting layer and check the data-visualization row in each one, then browse the templates and preview the one whose charting setup you would not have to rewrite. For the library itself, read the TanStack Charts overview before you adopt it.
FAQ: TanStack React Charts 1.3.0
Is @tanstack/react-charts 1.3.0 a breaking change?
I cannot confirm that from the registry facts I reviewed, because they contain no changelog or API delta. What I can confirm is that 1.3.0 is published by the official TanStack/charts repository on npm. Before upgrading, read the release notes on GitHub and the Charts docs; if the notes describe a major-version or API change, treat it as breaking and plan a migration rather than a silent bump.
How do I check which version I have installed?
Run npm ls @tanstack/react-charts in your project, or print the resolved version with node -p "require('@tanstack/react-charts/package.json').version". Use npm outdated @tanstack/react-charts to see whether a newer version is available. Confirm the lockfile resolves the version you expect after any bump, because a version in package.json without a matching lockfile entry is not a real upgrade.
Should I upgrade to 1.3.0 or to a newer line?
By version ordering, 1.3.0 is an earlier release than 1.4.0, so if you are starting fresh or modernizing, confirm whether a newer line is the better target before pinning 1.3.0. The registry facts I reviewed do not describe what changed between the two, so verify the delta in the official notes first, then bump in one commit and visually confirm your dashboards still render correctly.
Where is the official changelog for this release?
The authoritative references are the npm record for @tanstack/react-charts@1.3.0, the TanStack/charts releases page on GitHub, and the TanStack Charts documentation. I link those rather than summarize them, because the registry facts I used did not include a feature changelog to summarize.