Skip to content

Conversation

@AntonRatnick
Copy link

What?

UnsafeUnwrappedCookies and UnsafeUnwrappedHeaders added to next/headers next v14

Why?

We have a codemod which updates a codebase and uses the Unsafe types in case it is not able to modify code properly.
Such cases requires manual resolution from a developer. It would be nice to be able to run codemod staying on next.js v14 and being able to migrate gradually.

How?

Just adding types required =)

@ijjk
Copy link
Member

ijjk commented Nov 12, 2025

Allow CI Workflow Run

  • approve CI run for commit: c0d61c7

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

1 similar comment
@ijjk
Copy link
Member

ijjk commented Nov 12, 2025

Allow CI Workflow Run

  • approve CI run for commit: c0d61c7

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

@AntonRatnick AntonRatnick changed the title feat: add UnsafeUnwrappedCookie and UnsafeUnwrappedHeaders to next 14 feat: add UnsafeUnwrappedCookies and UnsafeUnwrappedHeaders to next 14 Nov 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants