A validation toolkit for Markdown and Standard Schema — built for Astro, Next.js, and modern frameworks.
FieldTest is a framework-agnostic TypeScript validation toolkit that brings order to content chaos. Whether you're building with Astro, Next.js, or any modern framework, FieldTest ensures your markdown content and frontmatter data is consistent, valid, and production-ready.
- 🚫 No more runtime content errors — Catch validation issues at build time
- 🔄 Framework agnostic — Works seamlessly with Astro, Next.js, Remix, SvelteKit, and more
- 📋 Standard Schema compliant — Built on Standard Schema v1 for maximum interoperability
- ⚡ Performance first — <50ms validation per document, handles 5000+ files efficiently
- 🛠️ Developer friendly — Excellent TypeScript support with comprehensive error messages
- 🔧 Zero config — Works out of the box, customizable when you need it
fieldtest/
├── packages/
│ ├── core/ # Core markdown processing
│ ├── validate/ # Validation utilities
│ ├── registry/ # Schema registry
│ ├── shared/ # Common utilities and types
│ ├── examples/ # Example implementations
│ └── integrations/
│ └── mcp/
│ └── fieldtest-mcp-server/ # MCP server for AI workflows
├── grit-plugins/ # Biome GritQL linting plugins
├── docs/ # Documentation
│ ├── guides/ # How-to guides
│ ├── reference/ # API reference
│ └── explainers/ # Conceptual articles
├── scripts/ # Build and utility scripts
└── biome.json # Biome configuration
✨ Content Validation — Validate markdown files against custom schemas with detailed error reporting
🎯 Standard Schema — Built on Standard Schema for interoperability
🏗️ Framework Integration — Works seamlessly with Astro, Next.js, and other modern frameworks
📚 Schema Registry — Reuse and manage validation schemas across projects
🔄 Markdown Processing — Parse and serialize markdown with frontmatter
🤖 AI Workflows — Model Context Protocol (MCP) server for AI-powered content validation
🛠️ Biome Plugins — Custom GritQL linting rules for migration assistance and best practices
npm install @watthem/fieldtest
# or
pnpm add @watthem/fieldtest
# or
yarn add @watthem/fieldtestRequirements: Node.js 18+ | Works with any package manager
- Define your content schema:
import type { StandardSchemaV1 } from '@watthem/fieldtest';
const blogSchema: StandardSchemaV1 = {
version: '1',
name: 'blog-post',
fields: {
title: { type: 'string', required: true },
author: { type: 'string', required: true },
published: { type: 'boolean', required: true },
tags: { type: 'string', array: true },
publishedAt: { type: 'date', required: false }
}
};- Validate your markdown content:
import { loadUserSchema, validateWithSchema } from '@watthem/fieldtest';
const schema = loadUserSchema(blogSchema);
const markdown = `---
title: "Getting Started with FieldTest"
author: "Jane Developer"
published: true
tags: ["typescript", "validation", "markdown"]
---
# Getting Started
This post shows how easy it is to validate content with FieldTest!
`;
const result = validateWithSchema(markdown, schema);
if (result.valid) {
console.log('✓ Content validated successfully!');
// Your content is safe to use
} else {
console.error('❌ Validation failed:');
result.errors.forEach(error => {
console.error(` • ${error.field}: ${error.message}`);
});
}That's it! You're now validating content like a pro. 🎆
FieldTest works seamlessly with your favorite framework:
// src/content/config.ts
import { defineCollection } from 'astro:content';
import { loadUserSchema, validateWithSchema } from '@watthem/fieldtest';
const blog = defineCollection({
type: 'content',
schema: (z) => z.object({
title: z.string(),
author: z.string(),
publishedAt: z.date()
}).refine((data) => {
// Add FieldTest validation on top of Zod
const result = validateWithSchema(
generateMarkdown(data),
loadUserSchema(blogSchema)
);
return result.valid;
})
});// Validate content in getStaticProps, generateStaticParams, or API routes
import { validateWithSchema, loadUserSchema } from '@watthem/fieldtest';
import fs from 'fs';
export async function generateStaticParams() {
const schema = loadUserSchema(blogSchema);
const posts = fs.readdirSync('./content');
return posts.map(post => {
const content = fs.readFileSync(`./content/${post}`, 'utf-8');
const result = validateWithSchema(content, schema);
if (!result.valid) {
throw new Error(`Invalid post ${post}: ${result.errors.map(e => e.message).join(', ')}`);
}
return { slug: post.replace('.md', '') };
});
}// Works with Remix, SvelteKit, Nuxt, Solid, and more!
import { validateWithSchema } from '@watthem/fieldtest';
// Universal validation that works anywhere
const isValid = validateWithSchema(content, schema).valid;Skip writing schemas for common use cases:
import { getBuiltInSchema } from '@watthem/fieldtest';
// Pre-built schemas for common content types
const blogSchema = getBuiltInSchema('blog-post');
const docsSchema = getBuiltInSchema('documentation');
const marketingSchema = getBuiltInSchema('marketing-copy');FieldTest includes custom GritQL plugins for Biome to help with migration and best practices:
// biome.json
{
"plugins": [
"./node_modules/@watthem/fieldtest/grit-plugins/fieldtest-migration.grit",
"./node_modules/@watthem/fieldtest/grit-plugins/schema-usage.grit"
]
}- ⚙️ Migration Helper — Detects legacy imports and types
- ✓ Schema Validation — Ensures validation results are checked
- 🎨 Code Quality — Flags non-standard patterns
// AI-powered content validation and generation
import { MCPServer } from '@watthem/fieldtest/mcp';
const server = new MCPServer({
schemas: [blogSchema, docsSchema],
aiValidation: true
});FieldTest has comprehensive documentation to get you started:
- 🚀 Getting Started — Quick installation and first steps
- 📚 API Reference — Complete function and type documentation
- 🎯 Framework Guides — Astro, Next.js, and more
- 📝 Schema Validation Guide — Creating and using schemas
- 💫 Examples — Real-world use cases and patterns
We welcome contributions! FieldTest is open source and built by the community.
# Clone and setup
git clone https://github.com/watthem/fieldtest.git
cd fieldtest
pnpm install
# Start development
pnpm dev # Watch mode for all packages
pnpm test # Run tests
pnpm lint # Check code quality- 🐛 Report bugs or request features via GitHub Issues
- 📝 Improve documentation — Fix typos, add examples, clarify concepts
- 🛠️ Add features — New schema types, framework integrations, utilities
- 📺 Create examples — Show how to use FieldTest in different scenarios
- 🔌 Build integrations — Plugins for editors, build tools, or frameworks
Check out our Contributing Guide for detailed guidelines.
Upgrading from FKit or legacy @fieldtest/* packages? We've got you covered:
# Update package.json
npm uninstall @fieldtest/core @fieldtest/validate @fieldtest/registry
npm install @watthem/fieldtest
# Update imports (TypeScript/JavaScript)
find . -name "*.ts" -o -name "*.tsx" -o -name "*.js" | xargs sed -i 's/@fieldtest\/[a-zA-Z-]*/@watthem\/fieldtest/g'
find . -name "*.ts" -o -name "*.tsx" -o -name "*.js" | xargs sed -i 's/FkitDocument/FieldTestDocument/g'📝 Complete Migration Guide — Detailed migration steps and breaking changes
Join the FieldTest community:
- 🐛 GitHub Issues — Bug reports and feature requests
- 💬 GitHub Discussions — Questions, ideas, and showcase
- 🐦 Twitter — Updates and announcements
- 📧 Email — Direct contact for partnerships or support
MIT License © 2024 Matthew Hendricks
Free to use in personal and commercial projects. See LICENSE for details.
FieldTest stands on the shoulders of giants:
- 📦 Standard Schema — Universal validation interface
- ⚛️ TypeScript — Type-safe development experience
- 📦 pnpm + Turborepo — Fast, reliable monorepo management
- 🤖 Biome — Fast formatting and linting
- ⚡ Vitest — Blazing fast unit testing
Ready to validate your content like a pro?