Extending req/res objects in custom server/standalone mode for App router

[coltonehrman]

Link to the code that reproduces this issue

#54440

To Reproduce

See #54440

Current vs. Expected behavior

See #54440

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 22.6.0: Wed Jul  5 22:21:53 PDT 2023; root:xnu-8796.141.3~6/RELEASE_ARM64_T6020
Binaries:
  Node: 16.20.1
  npm: 8.19.4
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 13.4.20-canary.37
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.0.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

App Router, Standalone mode (output: "standalone")

Additional context

Is this behavior suppose to exist for App router?

Based on the docs here, it seems that extending/modifying the Request object and accessing it in the App router is not possible. How will these use cases which were supported in Pages router be supported in App router?

[nicholasgriffintn]

Yeah this is the last thing holding us off from app router if the speed improvements are actually effective (not tried in a while), can't move off of custom server without having to host a proxy in front of next either, so don't really want to do that...

[kenreis]

Is this something that will be addressed. We are currently looking into transitioning to the App router, but we rely on extending the req object through our custom server set up. Not having access to the extended request object is a blocker for us.

[github-actions]

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.