Simplify your stack and build anything. Or everything.
Build tomorrow’s web with a modern solution you truly own.
AGENCY TESTIMONIAL
"Payload has transformed the way our clients manage content. It's an indispensable tool for any modern agency."
Code-based nature means you can build on top of it to power anything.
Resources for Developers
Get the resources you need to start building today
It’s time to take back your content infrastructure.
Featured Customer Story
Microsoft chose Payload to tell the world about AI.
"Proper way" to share a custom field?
3
I can't seem to find any info about this in the docs or in Discord/Github, so my apologies if this is obvious. 😅
What would be the "proper" way to share custom Field Components, whether with other people or between your own projects?
I guess maybe bundle the whole thing into a npm package and import it like you'd do normally (
https://payloadcms.com/blog/building-a-custom-field#:~:text=Import%20the%20field%20in%20a%20collection) ?
I think packaging it up would make the most sense, this way it can receive updates easily
Checks out! I don't have any experience making npm packages so I wasn't sure how involved that would be or if that would even be the best option in that scenario. 👍
@233209174069084161this guy's content is very good
https://www.youtube.com/watch?v=eh89VE3Mk5glink from a live:
https://www.youtube.com/watch?v=aKTSC4D1GL8ik its video content so it sucks to skim but hes a good one, the long video should give you full indepth coverage should you need it
Star
Discord
online
Can't find what you're looking for?
Get dedicated engineering support directly from the Payload team.