v0.5.1 — @dualmark/nextjs

@dualmark/nextjs@0.5.1

Patch Changes

• fix(nextjs): withDualmark() rejecting typed NextConfig from next.config.ts (#26).

  The internal NextConfigShape constraint had an [key: string]: unknown index
  signature, which TypeScript treats as a structural demand on the input. Next.js's
  NextConfig is a closed interface with no top-level index signature, so any
  caller passing a typed next.config.ts hit:

  Type 'NextConfig' is not assignable to type 'NextConfigShape'.
    Index signature for type 'string' is missing in type 'NextConfig'.
  

  The constraint was unnecessary — the function only reads transpilePackages
  and spreads the remaining config, neither of which need an index signature.
  Removing it unblocks typed configs on Next 14, 15, and 16. Runtime behavior
  is unchanged.

• docs(nextjs): Next.js 16 compatibility — package metadata, docs, and example (#27).

  • Drop the "Next.js 15" reference from the package description; the adapter
    works with the Next.js App Router on 14, 15, and 16.
  • Bump the next devDependency from ^15.0.0 to ^16.2.6 (test/build
    toolchain only — the peerDependencies range is unchanged).
  • Update README to document the Next.js 16 proxy.ts file convention,
    with a note that Next ≤15 should keep using middleware.ts (body is
    identical). No runtime behavior change.

  The reference example at examples/nextjs-app-router was migrated to
  Next.js 16 in the same change and still scores 120/125 under next dev.

Other packages

@dualmark/core, @dualmark/converters, @dualmark/astro, @dualmark/cloudflare, @dualmark/cli are unchanged at 0.5.0 (no changesets touched them this cycle).

Full Changelog: v0.5.0...v0.5.1