You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I reviewed CrawlerCode/payload-authjs and found an active Payload v3 + Next.js 15/16 setup with a component-driven frontend. That looks close to the projects the registry is built for.
Payload Components is MIT source tooling: it installs a block and wires the Pages collection, renderer mapping, generated Payload types, and admin import map rather than leaving those integration steps manual.
Would a small, repository-specific contribution be useful here? I can test one appropriate component against this repository and propose the smallest useful integration diff.
If this is in scope, which page surface or component family would be most useful? I’ll wait for alignment before opening a larger PR.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hi — I’m Chai, the maintainer of Payload Components.
I reviewed
CrawlerCode/payload-authjsand found an active Payload v3 + Next.js 15/16 setup with a component-driven frontend. That looks close to the projects the registry is built for.Payload Components is MIT source tooling: it installs a block and wires the Pages collection, renderer mapping, generated Payload types, and admin import map rather than leaving those integration steps manual.
Would a small, repository-specific contribution be useful here? I can test one appropriate component against this repository and propose the smallest useful integration diff.
If this is in scope, which page surface or component family would be most useful? I’ll wait for alignment before opening a larger PR.
All reactions