If you have questions about implementation details, help or support, then please use our dedicated community forum at GitHub Discussions PLEASE NOTE: If you choose to instead open an issue for your question, your issue will be immediately closed and redirected to the forum.

If you have found what you think is a bug, please file an issue. PLEASE NOTE: Issues that are identified as implementation questions or non-issues will be immediately closed and redirected to GitHub Discussions

If you are here to suggest a feature, first create an issue if it does not already exist. From there, we will discuss use-cases for the feature and then finally discuss how it could be implemented.

If you have been assigned to fix an issue or develop a new feature, please follow these steps to get started:

• Fork this repository.

• Install dependencies

  pnpm install

  • We use pnpm v9 for package management (run in case of pnpm-related issues).

    corepack enable && corepack prepare

  • We use nvm to manage node versions - please make sure to use the version mentioned in .nvmrc

    nvm use

• Build all packages.

  pnpm build:all

• Run development server.

  pnpm run watch

• Implement your changes and tests to files in the src/ directory and corresponding test files.

• Document your changes in the appropriate doc page.

• Git stage your required changes and commit (see below commit guidelines).

• Submit PR for review.

The documentations for all the TanStack projects are hosted on tanstack.com, which is a TanStack Start application (https://github.com/TanStack/tanstack.com). You need to run this app locally to preview your changes in the TanStack/virtual docs.

You can follow these steps to set up the docs for local development:

1. Make a new directory called tanstack.

mkdir tanstack

2. Enter that directory and clone the TanStack/virtual and TanStack/tanstack.com repos.

cd tanstack
git clone git@github.com:TanStack/virtual.git
# We probably don't need all the branches and commit history
# from the `tanstack.com` repo, so let's just create a shallow
# clone of the latest version of the `main` branch.
# Read more about shallow clones here:
# https://github.blog/2020-12-21-get-up-to-speed-with-partial-clone-and-shallow-clone/#user-content-shallow-clones
git clone git@github.com:TanStack/tanstack.com.git --depth=1 --single-branch --branch=main

tanstack/
   |
   +-- virtual/ (<-- this directory cannot be called anything else!)
   |
   +-- tanstack.com/

3. Enter the tanstack/tanstack.com directory, install the dependencies and run the app in dev mode:

cd tanstack.com
pnpm i
# The app will run on https://localhost:3000 by default
pnpm dev

4. Now you can visit http://localhost:3000/virtual/latest/docs/overview in the browser and see the changes you make in TanStack/virtual/docs there.

You can see the whole process in the screen capture below:

• Make sure you've installed the dependencies in the repo's root directory.

  pnpm install

• If you want to run the example against your local changes, run below in the repo's root directory. Otherwise, it will be run against the latest TanStack Virtual release.

  pnpm run watch

• Run below in the selected examples' directory.

  pnpm run dev

If you want to run an example without installing dependencies for the whole repo, just follow instructions from the example's README.md file. It will be then run against the latest TanStack Virtual release.

You can use Gitpod (An Online Open Source VS Code like IDE which is free for Open Source) for developing online. With a single click it will start a workspace and automatically:

• clone the TanStack/virtual repo.

• install all the dependencies in / and /docs.

• run below in the root(/) to Auto-build files.

  npm start

• run below in /docs.

  npm run dev

This repo uses Changesets to automate releases. If your PR should release a new package version (patch, minor, or major), please run run pnpm changeset and commit the file. If needed, changeset descriptions can be more descriptive, and will be included in the changelog. If your PR affects docs, examples, styles, etc., you probably don't need to generate a changeset.

Maintainers merge pull requests by squashing all commits and editing the commit message if necessary using the GitHub user interface.

Use an appropriate commit type. Be especially careful with breaking changes.

For each new commit added to main, a GitHub Workflow is triggered which runs the Changesets Action. This generates a preview PR showing the impact of all changesets. When this PR is merged, the package will be published to NPM.