[BUG]: Next 15 not supported

[sammaxwellxyz]

Describe the bug

When I try to install alongside next 15 an error is raised including

npm error Conflicting peer dependency: next@14.2.17
npm error node_modules/next
npm error   peer next@"^9.5.0 || ^10.2.1 || ^11.1.0 || ^12.1.0 || ^13.0.0 || ^14.0.0" from next-safe@3.5.0
npm error   node_modules/next-safe
npm error     next-safe@"^3.5.0" from the root project

Steps To Reproduce

1. Create new Next.js app
2. Setup next-safe:

   npm add next-safe
   

3. Start app
4. See error

Version

v3.x.x

Relevant log output

❯ npm add next-safe
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: safe-demo@0.1.0
npm error Found: next@15.0.3
npm error node_modules/next
npm error   next@"15.0.3" from the root project
npm error
npm error Could not resolve dependency:
npm error peer next@"^9.5.0 || ^10.2.1 || ^11.1.0 || ^12.1.0 || ^13.0.0 || ^14.0.0" from next-safe@3.5.0
npm error node_modules/next-safe
npm error   next-safe@"*" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error

Code of Conduct

• I agree to follow this project's Code of Conduct

[brandanking-decently]

This would be great, especially if this project is still maintained

[trezy]

The issue is that React 15 relies on React 19, which uses a new (and very different) reconciler.

This comment provides more context on my plans for the library.

[davidmytton]

We ended up building a new library because this one seems unmaintained: https://blog.arcjet.com/nosecone-a-library-for-setting-security-headers-in-next-js-sveltekit-node-js-bun-and-deno/

[multivoltage]

I tried with:

• next 15
• react 19
• next-safe 3.5.0

And for me work even if inside next.config.ts instead to have

import { nextSafe } from "next-safe";
// and use like ......nextSafe({})

I have to write

import nextSafe from "next-safe";
// and use like ......nextSafe({})

Adding a ts-ignore flag. I can confirm that work