-
Notifications
You must be signed in to change notification settings - Fork 82
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
[BUG]: inferred web middleware type depends on import("undici-types")
#1118
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 |
Thanks for the report, I swear that sometimes Typescript infers types out of nowhere. Feel free to send a PR. It would be the quickest way to get it fixed |
🎉 This issue has been resolved in version 13.7.4 🎉 The release is available on: Your semantic-release bot 📦🚀 |
What happened?
@octokit/webhooks v13.7.x (ie. versions featuring #1078) features the following emitted type pattern in
dist-types/middleware/web/index.d.ts
:The middleware return type is not specified in the source, and is inferred as
Promise<import("undici-types").Response>
rather thanPromise<Response>
for the declaration emit, via @types/node's fetch types.Since undici-types is not a dependency of the octokit packages, this leads to the following TypeScript compilation error, depending on build environment:
It looks like this has bricked a number of GitHub Actions workflows.
Versions
@octokit/webhooks v13.7.x
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: