Skip to content

Conversation

@dargmuesli
Copy link
Member

@dargmuesli dargmuesli commented Jan 7, 2026

πŸ”— Linked issue

#3676

❓ Type of change

  • πŸ“– Documentation (updates to the documentation or readme)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • πŸ‘Œ Enhancement (improving an existing functionality like performance)
  • ✨ New feature (a non-breaking change that adds functionality)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

πŸ“š Description

See Nuxt server's forwarding context & headers description.

Using the method described there, this PR aims to make the context forwarding more flexible. This helps me adding support for the nuxt-csurf module for example.

Please check the first commit first to see the actual change this PR proposes more clearly. Due to a typescript excessive stack depth error I had to refactor the code a bit in the second commit.

πŸ“ Checklist

  • I have linked an issue or discussion.
  • I have updated the documentation accordingly.

@vercel
Copy link

vercel bot commented Jan 7, 2026

@dargmuesli is attempting to deploy a commit to the Nuxt Team on Vercel.

A member of the Team first needs to authorize it.

@pkg-pr-new
Copy link

pkg-pr-new bot commented Jan 7, 2026

npm i https://pkg.pr.new/@nuxt/content@3677

commit: a03fea8

@dargmuesli dargmuesli marked this pull request as ready for review January 7, 2026 21:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant