Contribution / Local Development Setup

[wide pilot]

Hi everyone,

When developing Next.js projects locally, I often have the case that I want to debug or log payload in order to better understand the behavior of payload or error messages that occur in my projects or in payload and possibly also contribute bug fixes or features. My Next.js projects are either standalone or organized in a monorepo with turbo repo. Is there a guide or recommendation on how I can best do a local development setup with payload for both use cases (standalone Next.js project or monorepo Next.js project)?

Thanks for your help!

[gloomy pawn]

New Community-Help Thread Created!

Help is on the way! To mark it as solved, use the /solve command. In the meantime, here are some existing threads that may help you:

Documentation:

• Local API - Accessing Payload - Importing it
• Migrations - When to run migrations - Postgres
• Using Payload outside Next.js - Importing the Payload Config outside of Next.js

Community-Help:

• Deploying payload 3.0 with docker to Coolify
• Req.user null presumably due to cross-site request?
• Host/Headers in 3.0.beta.32
• Loading Payload in a Docker Container

[wide pilot]

Any Non-Payload-Bot recommendations? 😃

[quaint ravine]

There's a contribution guide on youtube as well as in a readme file in the monorepo

Essentially, you want to:

• Fork the repo
• Pull locally
• Install deps
• pnpm dev <test folder> (Commonly you'll use pnpm dev _community)

Video here: https://www.youtube.com/watch?v=08Qa3ggR9rw&ab_channel=Payload