Developer workflow tools for Payload CMS 29

Lint Payload CMS projects with the official ESLint rules, or with Biome and Oxlint. Check component imports in your editor and test without a running CMS.

Stateful test emulator of the Payload collection REST API with seeded data

Editor support for Payload component paths, with import checks and autocomplete

Governance checks and ESLint rules for Payload project structure, access code and hooks

Manifest, linter and Payload block generator for a design system's components

Automated code transforms that move a Payload project past breaking changes

Idempotent seed runner that fills a Payload database with ordered, cross-referenced content

Agent skill that enforces generated, paired Payload database migrations and gates destructive changes

Shared lint, test and quality configs that keep Payload projects consistent

Oxlint rules that flag risky Payload Local API calls before code review

Biome lint rules that catch risky Payload Local API calls before code review

CLI and terminal UI to create and manage multi-tenant Payload sites from one backend

Shared ESLint 9 flat configs for Node, React, Next.js and Payload projects

Reusable Cursor coding-agent rules for Bun, commits, TypeScript and clean code

Type-safe factory functions that build Payload field configs with less boilerplate

Readiness check that runs a Payload collection query to confirm the database responds

Static linter that flags access control and security mistakes

Reusable end-to-end testing helpers with a page object base and auth fixtures

Config guardrails and DTO helpers that keep Payload API responses consistent

Helpers for extracting IDs, resolving documents and composing field validators

Collections, globals, email templates and utilities for common Payload site builds

About these packages

Developer workflow tools help while you write and test Payload code. Some lint your project or autocomplete component import paths in the editor. Others stand in for the REST API in tests.

What these tools cover

  • Official ESLint rules and a shared flat config for Payload projects
  • The official TypeScript plugin that checks component import paths
  • The official codemod for moving a Payload 3 project to the Payload 4 beta
  • Biome and Oxlint rules that flag risky Local API calls
  • Emulator, an offline stand-in for the REST API in tests
  • Shared configs and governance checks such as Ploaness and Airness

Choosing dev workflow tools

Add the official ESLint config and rules first. They come from the Payload team and check Payload-specific patterns. Add the TypeScript plugin if your editor does not resolve component import paths. If you already use Biome or Oxlint, their community rules flag risky Local API calls before review. Airness audits access rules and security settings. Pick Emulator when frontend tests should run without a real CMS. To move a Payload 3 project to the Payload 4 beta, start with the official codemod among the CLI tools. Review its diff, then follow the migration guide for anything it cannot change.

Frequently asked questions

How do I upgrade Payload to a new major version?

Follow Payload's migration guide for the version you move to, and work through it on a branch. To try the Payload 4 beta on a Payload 3 project, start with the official codemod. Review its diff and fix the rest by hand.

Can I test Payload code without a running CMS?

Emulator stands in for the Payload REST API offline, so frontend tests run without a real CMS. Tests that use the Local API still need Payload and a database. The SQLite adapter keeps that setup light.

Are there lint rules for Payload projects?

Yes. The Payload team publishes ESLint rules for Payload-specific patterns and a shared flat config. Community packages add Biome and Oxlint rules against unsafe Local API calls.