chore:Update ESLint and remove unused code

.github/workflows/autofix.yaml

@@ -0,0 +1,31 @@
+name: autofix.ci # needed to securely identify the workflow
+
+on:
+  pull_request:
+  push:
+    branches: [main]
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.event.number || github.ref }}
+  cancel-in-progress: true
+
+permissions:
+  contents: read
+
+jobs:
+  autofix:
+    name: autofix
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v5.0.0
+        with:
+          fetch-depth: 0
+      - name: Setup Tools
+        uses: tanstack/config/.github/setup@main
+      - name: Fix formatting
+        run: pnpm format
+      - name: Apply fixes
+        uses: autofix-ci/action@635ffb0c9798bd160680f18fd73371e355b85f27
+        with:
+          commit-message: 'ci: apply automated fixes'

.github/workflows/pr.yaml

@@ -8,17 +8,12 @@ jobs:
     name: PR
     runs-on: ubuntu-latest
     steps:
-      - name: Git Checkout
-        uses: actions/checkout@v4
-      - name: Setup pnpm
-        uses: pnpm/action-setup@v4
-      - name: Setup Node
-        uses: actions/setup-node@v4
+      - name: Checkout
+        uses: actions/checkout@v5.0.0
         with:
-          node-version-file: .nvmrc
-          cache: pnpm
-      - name: Install Packages
-        run: pnpm install --frozen-lockfile
+          fetch-depth: 0
+      - name: Setup Tools
+        uses: tanstack/config/.github/setup@main
       - name: Run Lint
         run: pnpm lint
       - name: Run Build

.gitignore

@@ -1,7 +1,7 @@
 node_modules
 package-lock.json
 yarn.lock
-convex/generated
+drizzle/migrations
 
 .tanstack
 .DS_Store

.nvmrc

@@ -1 +1 @@
-v20.15.0
+v20.19.6

.prettierignore

@@ -3,8 +3,6 @@
 **/public
 pnpm-lock.yaml
 routeTree.gen.ts
-convex/_generated
-convex/README.md
 src/blog/tanstack-db-0.1-the-embedded-client-database-for-tanstack-query.md
 .content-collections
 .claude

AGENTS.md

@@ -72,3 +72,94 @@ loader: async ({ deps }) => {
 ```
 
 This ensures the loader only re-runs when the specific dependencies change, not when unrelated search params (like `expanded`, `viewMode`, etc.) change.
+
+### Loaders Are Isomorphic
+
+**Loaders in TanStack Start/Router are isomorphic and cannot call server logic unless via a call to a server function.**
+
+Loaders run on both the server and client, so they cannot directly access server-only APIs (like file system, database connections, etc.). To perform server-side operations, loaders must call server functions (e.g., TanStack server functions created via `createServerFn()`, Convex queries/mutations, API routes, or other server functions).
+
+❌ **Bad:**
+
+```typescript
+loader: async () => {
+  // This won't work - direct server API access
+  const data = await fs.readFile('data.json')
+  return { data }
+}
+```
+
+✅ **Good:**
+
+```typescript
+loader: async () => {
+  // Call a server function instead (TanStack server function or Convex)
+  // TanStack server functions created via createServerFn() can be called directly
+  const data = await serverFn({ data: { id: '123' } })
+  // or
+  const data = await convex.query(api.data.getData)
+  return { data }
+}
+```
+
+## Server-Only Code and Environment Shaking
+
+### TanStack Start Environment Shaking
+
+**TanStack Start performs environment shaking - any code not referenced by a `createServerFn` handler is stripped from the client build.**
+
+This means:
+
+- Server-only code (database, file system, etc.) is automatically excluded from client bundles
+- Only code inside `createServerFn` handlers is included in server bundles
+- Code outside handlers is included in both server and client bundles
+
+### Importing Server Functions
+
+**Server functions wrapped in `createServerFn` can be safely imported statically in route files.**
+
+❌ **Bad - Dynamic imports in component code:**
+
+```typescript
+// In a route component
+const rolesQuery = useQuery({
+  queryFn: async () => {
+    const { listRoles } = await import('~/utils/roles.server')
+    return listRoles({ data: {} })
+  },
+})
+```
+
+This causes bundler issues because dynamic imports can't be properly tree-shaken, potentially pulling server-only code (like `Buffer`, `drizzle`, `postgres`) into the client bundle.
+
+✅ **Good - Static imports:**
+
+```typescript
+// At the top of the route file
+import { listRoles } from '~/utils/roles.server'
+
+// In component code
+const rolesQuery = useQuery({
+  queryFn: async () => {
+    return listRoles({ data: {} })
+  },
+})
+```
+
+Since `listRoles` is wrapped in `createServerFn`, TanStack Start will properly handle environment shaking and exclude server-only dependencies from the client bundle.
+
+### Rules for Server-Only Imports
+
+1. **Server functions** (`createServerFn` wrappers) can be imported statically anywhere
+2. **Direct server-only code** (database clients, file system, etc.) must ONLY be imported:
+   - Inside `createServerFn` handlers
+   - In separate server-only files (e.g., `*.server.ts`)
+   - Never use dynamic imports (`await import()`) for server-only code in component code
+
+## Development & Build Commands
+
+### Use `build` for Testing Build Output
+
+**The `dev` command does not end - it runs indefinitely in watch mode.**
+
+When agents need to test build output or verify that the project builds successfully, use the `build` command instead of `dev`. The `build` command will complete and exit, making it suitable for automated testing and verification.

agents/tasks/tanstack-com-task-list.md

@@ -60,7 +60,7 @@
   - Status: Backlog
   - Notes:
     - Route: `src/routes/state-of-tanstack.tsx`.
-    - Include growth charts (npm downloads: reuse `NpmStatsChart.tsx` or embed portions of `stats/npm`), GitHub stars, contributors, dependents (available via Convex aggregation already powering `OpenSourceStats`).
+    - Include growth charts (npm downloads: reuse `NpmStatsChart.tsx` (in git history) or embed portions of `stats/npm`), GitHub stars, contributors, dependents (available via Convex aggregation already powering `OpenSourceStats`).
       - Community stats: Discord members (needs server function), newsletter subscribers (manual or vendor API), X/Twitter followers (manual or API), repository contributors (Convex or GitHub GraphQL on server).
     - Ecosystem counts: partners (derive from `src/utils/partners.tsx`), plugins/tools (manual list or content collection).
     - CTA to GitHub org.

content-collections.ts

@@ -12,11 +12,17 @@ const posts = defineCollection({
   }),
   transform: ({ content, ...post }) => {
     const frontMatter = extractFrontMatter(content)
+
+    // Extract header image (first image after frontmatter)
+    const headerImageMatch = content.match(/!\[([^\]]*)\]\(([^)]+)\)/)
+    const headerImage = headerImageMatch ? headerImageMatch[2] : undefined
+
     return {
       ...post,
       slug: post._meta.path,
       excerpt: frontMatter.excerpt,
       description: frontMatter.data.description,
+      headerImage,
       content,
     }
   },