Feat/next16 compat

[PaulBoye-py]

Description

Adds Next.js 16 support to next-cloudinary. No library source code changes were required, and the existing components are compatible with Next.js 16 as-is.

Issue Ticket Number

Supersedes #645 (same intent, reimplemented cleanly on top of current main)

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Fix or improve the documentation
• This change requires a documentation update

Changes

• next-cloudinary/package.json — adds || ^16 to next peerDependencies
• tests/nextjs-app/package.json — upgrades integration test app to Next.js 16, React 19, ESLint 9
• tests/nextjs-app/tsconfig.json — sets moduleResolution: bundler and jsx: react-jsx (both required by Next.js 16)
• pnpm-lock.yaml — updated to reflect peerDependency change

Validation

• pnpm test — 16/16 unit tests pass
• pnpm test:app — full Next.js 16.3.4 (Turbopack) production build passes cleanly
• CI: Passed Test (Node 20) and (Node 22) ✓

Notes

• Next.js 16 requires Node.js 20.9+ minimum — the CI already satisfies this
• Turbopack is the default bundler in Next.js 16 — no issues were found
• forwardRef and JSX.Element are soft-deprecated in React 19 but still work — this will been tracked for future v7 items

Checklist

• I have followed the contributing guidelines of this project as mentioned in CONTRIBUTING.md
• I have checked to ensure there aren't other open Pull Requests for the same update/change
• I have performed a self-review of my own code
• I have run tests locally to ensure they all pass
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes needed to the documentation

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
next-cloudinary	Ready	Preview	Sep 10, 2026 12:37pm UTC