Next.js — PLANNED / NOT_IMPLEMENTED

Quick summary

There is currently no dedicated Next.js license adapter. The Next.js sample app is an integration fixture, not evidence that such a package exists.

For server-side licensing, review the generic Node SDK and implement explicit server-route authorization until a Next.js adapter is shipped.

No Next.js adapter exists

There is no @yetdapay/license-next or @yetdapay/sdk-next package in this repository. This page exists to state that honestly rather than let readers infer one.

What does exist today

• examples/nextjs-site/ — a minimal Next.js 14 (app router) fixture site used as an install target for the yetdapay-install skill. It is intentionally not pre-integrated; an agent adds donation/feedback surfaces to it end-to-end.
• The copy-in @yetdapay/sdk React component works in Next.js: sdk/react/YetdaPayButtons.tsx is already marked 'use client' — copy it plus sdk/core.ts into your app and render it from a client component.
• The framework-agnostic license cores (@yetdapay/license-nuxt/core, @yetdapay/license-nuxt/client) accept a plain {headers, method, requestTarget, rawBody} descriptor, so a route-handler adapter is straightforward to write — but none ships.

If you need licensing in Next.js now

Two DIY paths, both outside the shipped surface:

1. Route handlers (app/api/**/route.ts) — adapt the 4-field descriptor contract of createLicenseGuard from @yetdapay/license-nuxt/core to Next's Request.
2. Direct @yetdapay/license-server use — call authorize(headers, requestTarget, rawBody) inside a route handler and map the LicenseError to a Response.

Status wording

• Next.js license adapter: NOT_IMPLEMENTED.
• Next.js donation/feedback install: works today via the copy-in React component or a hosted <a> link (this is what examples/nextjs-site/ demonstrates).