You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
is that we create an expressJS handler that is specific to NextJS / Vercel's edge function model. However, under the hood, it's just plain expressJS (I believe).
If we extract the configuration options and the actuall proxying
I am marking this issue as stale as it has not received any engagement from the community or maintainers for a year. That does not imply that the issue has no merit! If you feel strongly about this issue
open a PR referencing and resolving the issue;
leave a comment on it and discuss ideas on how you could contribute towards resolving it;
leave a comment and describe in detail why this issue is critical for your use case;
open a new issue with updated details and a plan for resolving the issue.
Throughout its lifetime, Ory has received over 10.000 issues and PRs. To sustain that growth, we need to prioritize and focus on issues that are important to the community. A good indication of importance, and thus priority, is activity on a topic.
Unfortunately, burnout has become a topic of concern amongst open-source projects.
It can lead to severe personal and health issues as well as opening catastrophic attack vectors.
The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone.
If this issue was marked as stale erroneously you can exempt it by adding the backlog label, assigning someone, or setting a milestone for it.
Thank you for your understanding and to anyone who participated in the conversation! And as written above, please do participate in the conversation if this topic is important to you!
See discussions https://ory-community.slack.com/archives/C02MR4DEEGH/p1646150967822979
Basically, what we do here
integrations/src/next-edge/index.ts
Line 26 in 808c421
is that we create an expressJS handler that is specific to NextJS / Vercel's edge function model. However, under the hood, it's just plain expressJS (I believe).
If we extract the configuration options and the actuall proxying
integrations/src/next-edge/index.ts
Line 108 in 808c421
we could for sure make it work with netlify and other providers (e.g. cloudflare functions).
It's probably just a bit of fiddling to get it right!
The text was updated successfully, but these errors were encountered: