@ltikit/next
v1.0.0-rc.5
Published
Next.js App Router route-handler bindings for ltikit (Web-standard Request/Response — no next dependency).
Readme
@ltikit/next
Next.js App Router route-handler bindings for LTIkit — built on
Web-standard Request/Response, no next dependency. Works in any App Router route.
Pick one framework binding (this, @ltikit/hono,
or hand-rolled). Requires @ltikit/core.
npm i @ltikit/core @ltikit/nextUsage
// app/api/lti/login/route.ts
import { oidcLogin } from '@ltikit/next'
export const POST = oidcLogin(lti, { redirectUri: `${APP_URL}/api/lti/launch` })
// app/api/lti/launch/route.ts
import { launch, sessionRedirect } from '@ltikit/next'
export const POST = launch(lti, async (result) => {
// create your session (see Auth integration), then:
return sessionRedirect({ to: '/home', cookies: [/* your session cookie */] })
})
// app/.well-known/jwks.json/route.ts
import { jwks } from '@ltikit/next'
export const GET = jwks(lti)Also exports iframe helpers — cspFrameAncestors, sameSiteNoneCookie (with CHIPS
Partitioned support), sessionRedirect, frameResizeScript — and a ./client entry for LTI
Platform Storage (cookieless launches, survives third-party-cookie blocking):
import { platformStorage } from '@ltikit/next/client'Docs
Links
Repository · Issues · Need help? — paid setup/integration help available.
MIT
