-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEAT]: WebStandard Middleware #1063
Comments
👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labeled with |
I created this middleware, https://github.com/octokit/webhooks.js/compare/web-middleware |
app.js and It was already supported in oauth-app.js https://github.com/octokit/oauth-app.js/blob/main/src/middleware/web-worker/index.ts |
Describe the need
Currently, octokit only supports creating middleware for Node.js ,
but there are times when I want to use octokit in an environment other than Node.js .
This is not a big problem with runtimes that are compatible with Node.js, such as Deno and Bun,
Edge runtimes such as Cloudflare Workers may not offer Node.js compatibility.
Therefore, it is necessary to provide Middleware that uses WebStandard API (
Request
/Response
).SDK Version
No response
API Version
No response
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: