tpmjs/packages/db
Ajax Davis e84eda7525 refactor: rename exportName to name across entire codebase
- Database: Migrate column export_name to name in tools table
- Prisma schema: Update Tool model to use name field
- Sync routes: Update keyword and changes sync to use name
- Railway executor: Update API endpoints to use name parameter
- API routes: Update all tool routes to use name field
- Web app: Update all pages and components
- Playground: Update tool loader and sidebar
- create-basic-tools: Update types and generators
- Scripts: Update sync and test scripts

Database migration was done via direct SQL:
  ALTER TABLE tools RENAME COLUMN export_name TO name;

The unique constraint remains on (package_id, name).

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-12-17 17:19:21 +10:00
..
prisma refactor: rename exportName to name across entire codebase 2025-12-17 17:19:21 +10:00
src feat(db): create database package with Prisma schema for NPM registry 2025-11-28 02:07:39 +10:00
.env.example feat(db): create database package with Prisma schema for NPM registry 2025-11-28 02:07:39 +10:00
check-tool.js fix: update API route to use catch-all pattern for clean URLs 2025-11-29 22:57:54 +10:00
check-tool.mjs fix: update dependency cruiser config to allow TypeScript path aliases and workspace packages 2025-11-30 01:55:51 +10:00
package.json feat: upgrade to AI SDK v6 beta and Zod v4 to fix tool schema errors 2025-11-30 19:14:01 +10:00
README.md feat(db): create database package with Prisma schema for NPM registry 2025-11-28 02:07:39 +10:00
sync-single-tool.mjs fix: update dependency cruiser config to allow TypeScript path aliases and workspace packages 2025-11-30 01:55:51 +10:00
test-query.mjs fix(ci): skip lefthook install when .git directory missing 2025-11-29 13:51:05 +10:00
tsconfig.json feat(db): create database package with Prisma schema for NPM registry 2025-11-28 02:07:39 +10:00

@tpmjs/db

Database package for TPMJS NPM Registry. Provides Prisma ORM setup and database client for storing tool metadata.

Setup

1. Create Neon Database

  1. Go to https://neon.tech/
  2. Create a new project
  3. Copy the connection string

2. Configure Environment

cp .env.example .env
# Edit .env and add your DATABASE_URL

3. Run Migrations

pnpm db:migrate
pnpm db:seed

Usage

import { prisma } from '@tpmjs/db';

// Query tools
const tools = await prisma.tool.findMany({
  where: {
    category: 'web-scraping',
    isOfficial: true,
  },
  orderBy: {
    qualityScore: 'desc',
  },
  take: 10,
});

// Update sync checkpoint
await prisma.syncCheckpoint.update({
  where: { source: 'changes-feed' },
  data: {
    checkpoint: {
      sequence: '12345',
      lastProcessed: new Date().toISOString(),
    },
  },
});

Scripts

  • pnpm db:generate - Generate Prisma client
  • pnpm db:push - Push schema to database (for development)
  • pnpm db:migrate - Create and run migrations (for production)
  • pnpm db:studio - Open Prisma Studio GUI
  • pnpm db:seed - Seed initial data

Schema

Tool

Stores NPM packages with TPMJS metadata from their package.json.

SyncCheckpoint

Tracks progress of sync workers (changes feed, keyword search, metrics).

SyncLog

Audit trail of all sync operations.