Sourcemap Explorer
Stack · npm package

@xata.io/client

Xata.io SDK for TypeScript and JavaScript

latest 0.30.1· Apache-2.0· 4,377 versions publishedView on npm

About

Xata.io SDK for TypeScript and JavaScript

Live mirror of the GitHub README. Updated whenever the repo's default branch changes.

[!IMPORTANT]

Xata Lite was permanently retired on February 28, 2026. This repository is a public archive.

The new Xata Platform offers managed Postgres with copy-on-write branching, direct SQL access, and unlimited scale.

Quick facts

Latest version0.30.1
LicenseApache-2.0
Repositorygithub.com/xataio/client-ts
Homepagexata.io/docs/sdk/getting-started
Installnpm install @xata.io/client
Direct dependencies0
Peer dependenciestypescript

Common pairings

Packages this one expects to find in the same project. Each is also a Sourcemap Explorer detection target.

typescript

How Sourcemap Explorer detects @xata.io/client

We catch @xata.io/client from two complementary signals: bundled source paths and the embedded package.json. Modern bundlers (webpack, Vite, esbuild, Rollup, Turbopack) preserve the original node_modules/@xata.io/client/ paths inside the JavaScript sourcemap's sources[] array — that's the canonical signal. When the matching package.json is also captured in sourcesContent[], we read the exact version field — patch number included. No regex guessing, no version inference.

  1. 1

    Confirm the site exposes sourcemaps

    In DevTools Network, check the response headers of any application script for `SourceMap` or `X-SourceMap`. Failing that, fetch the script's last 4 KB and look for a `//# sourceMappingURL=` comment.

  2. 2

    Find the package in the bundle

    Open DevTools → Network → reload. Click any application script and look at its sourcemap. Inside, search `sources[]` for entries matching `node_modules/@xata.io/client/` — every match confirms the package is bundled. The matching `sourcesContent[i]` for `node_modules/@xata.io/client/package.json` gives you the exact installed version.

  3. 3

    Read the version directly from package.json

    Run `jq -r '. as $m | $m.sources | to_entries[] | select(.value | endswith("node_modules/@xata.io/client/package.json")) | $m.sourcesContent[.key] | fromjson | .version' bundle.js.map`. Sourcemap Explorer automates the same query in the popup.

Recent versions

Version
Released
0.1.0
—
0.1.1
—
0.1.2
—
0.1.3
—
0.1.4
—
0.1.5
—
0.2.2
—
0.3.0
—

FAQ

What is @xata.io/client used for?

Xata.io SDK for TypeScript and JavaScript

How can I tell if a website is using @xata.io/client?

Open the page in Chrome with the Sourcemap Explorer extension installed and read the Stack tab. We catch `@xata.io/client` from two complementary signals: `node_modules/@xata.io/client/` paths inside the JavaScript sourcemap, and the embedded `package.json` we read for exact-version detection. Without the extension you can do the same lookup manually in DevTools — the steps are listed in the "How Sourcemap Explorer detects" section above.

What is the latest version of @xata.io/client?

0.30.1, as published on the npm registry. The "Recent versions" table on this page lists the most recent 8 releases with their release dates. Sourcemap Explorer reports the version actually bundled into a site, which can lag the latest release by months on real-world deployments.

Where can I read more?

Project homepage: https://xata.io/docs/sdk/getting-started. Source code: https://github.com/xataio/client-ts. Published on npm: https://www.npmjs.com/package/@xata.io/client. Licensed as Apache-2.0.

Detected by Sourcemap Explorer

When a bundle ships sourcemaps, we read the embedded package.json for @xata.io/client and report the precise version. Without sourcemaps, an import / require in the page's scripts is enough to flag it.

Install free on Chrome