npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

payloadcms-compiler-check

v1.1.0

Published

Check for common PayloadCMS build and usage issues

Readme

payloadcms-compiler-check

A CLI tool to ensure your Payload CMS client-side code only imports valid Payload collections and that all collections used in client code are consistent with those defined in your Payload config.

Features

  • Detects invalid or missing Payload collection imports in client-side files (e.g., React/Next.js components).
  • Flags use of collections that are not present or out-of-sync with your payload.config.ts collections array.
  • Ensures updates to collections are reflected across your codebase, reducing runtime errors from stale imports.
  • Provides actionable suggestions to fix collection mismatches or import issues.

Installation

Install the package globally or locally via npm:

npm install -g payloadcms-compiler-check

Or install it in your project:

npm install payloadcms-compiler-check

Usage

Run the CLI on your project’s source directory:

npx payloadcms-compiler-check ./src
  • The tool scans all .js, .jsx, .ts, and .tsx files in the specified directory for Payload imports.
  • If no path is provided, it defaults to ./src.

Example Output

Given a file with issues:

// src/components/ArticleList.tsx
import { usePayload } from 'payload-react';
import { BlogPosts } from '../collections/BlogPosts'; // This collection does not exist in config

export default function ArticleList() {
  // ...
}

Running the tool:

npx payloadcms-compiler-check ./src

Output:

Checking Payload collections in ./src...

Diagnostics:
- src/components/ArticleList.tsx:2:10 - Imported collection "BlogPosts" not found in payload.config.ts.
  Suggestion: Add "BlogPosts" to your payload.config.ts collections or remove the import.

1 issue(s) found.

Contributing

Fork the repository: https://github.com/dan-li-dev/payloadcms-compiler-check

Create a feature branch: git checkout -b feature/add-collection-check

Commit your changes: git commit -m "Add check for invalid collection imports"

Push to the branch: git push origin feature/add-collection-check

Open a pull request.

License

MIT License. See LICENSE for details.