TL;DR

Update the proxy.ts documentation to consistently state that it uses the Edge Runtime, as implied by multiple sources including the migration guide and auth docs.

Guidance

• Review the documentation for proxy.ts and ensure it accurately reflects the runtime environment, which appears to be the Edge Runtime based on the migration guide and auth docs.
• Verify the consistency of runtime information across relevant documentation pages, including the proxy.ts docs, migration guide, and auth docs.
• Consider adding a note to the proxy.ts docs to clarify its limitations, such as not being a good fit for session management, despite being mentioned as a documented approach in the auth docs.

Notes

The inconsistency in documentation may be due to the recent migration from middleware to proxy in v16, and updating the docs to reflect the correct runtime environment should help resolve the issue.

Recommendation

Apply workaround: Update the proxy.ts documentation to reflect the correct runtime environment, as this appears to be the most straightforward solution to resolve the inconsistency in the documentation.