GeezerVison is showing tanstack.com — TanStack Config

Config

The package-maintenance contract behind TanStack.

TanStack Config collects the lint, build, monorepo, preview, versioning, and publishing conventions used to keep a large open-source package family moving together.

Docs

package maintenance

configuration surface

eslint.config.js

explicit

maintained by

@tanstack/eslint-config

$ pnpm lint

resulting contract

flat config · shared rules

823.7Ktotal downloads 12,349weekly downloads 402GitHub stars

Consumer boundary

The tarball is the product. Source is only its input.

Consumers receive exports, JavaScript, declarations, metadata, and documentation—not your repository. The conventions keep that package boundary reviewable and use package checks such as publint before a release reaches npm.

package x-ray

src/index.tssource

tests/index.test.tstest only

tsdown.config.tsbuild only

package.jsonpublished metadata

README.mdpublished docs

Build inputs and release machinery stay visible to maintainers.

affected task graph

changed package

router-core

lint · test · build

react-router

lint · test · build

start

lint · test · build

Nx affected + task cache

pkg-pr-new preview

Monorepo economics

A pull request should pay only for what it can affect.

Nx connects package dependencies to affected lint, test, and build tasks, then reuses cached work. pkg-pr-new closes the feedback loop by turning a pull request into packages maintainers can install before merging.

Release trust

Release intent is reviewed. Publish credentials are temporary.

Changesets record package-level release intent in the pull request. The release workflow turns that intent into versions and changelogs, while npm trusted publishing can exchange GitHub’s OIDC identity for short-lived publish access with provenance.