Shared lint, test and quality configs that keep Payload projects consistent
Airness
Governance checks and ESLint rules for Payload project structure, access code and hooks
Installation
pnpm add @airness/payload About
Airness Payload checks Payload CMS projects for problems that tend to slip past review, such as access rules that drift from the project's conventions, hooks that bypass the request's transaction, generated files that fall out of sync, migrations that no longer match the schema, and environment variables read outside one validated module. Each check runs from the command line inside a Payload project and reports what it finds, so a team can catch these issues before they reach a merge.
The package also ships an ESLint configuration for Payload projects. It applies the same conventions in the editor: no inline functions in collection, global, field or block configs, hooks that pass the request through to Payload operations, and immutable data handling in hooks. Editors load it next to the general Node rules from the wider Airness stack.
Package info
- Package name
@airness/payload- Latest version
1.0.12- Unpacked size
- 276 kB
- License
- MIT-0
- Weekly downloads
- 512
- Last publish
- Nov 14, 2026
More from ciechanowiec
View profileSimilar tools
More in Dev workflowStateful test emulator of the Payload collection REST API with seeded data
Editor support for Payload component paths, with import checks and autocomplete
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