-
Notifications
You must be signed in to change notification settings - Fork 310
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]: OctokitOptions declared locally but not exported #645
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 labled with |
You are getting that error because that export does not exist. It's imported in the If you absolutely need to import it, you can use: import type from "@octokit/core/dist-types/types.d": |
Its mostly for cleanliness of some helper functions we are establishing for Octokit initialization. Any plans to add this as an export? Would it be an accepted PR? |
You can also do this: type OctokitOptions = ConstructorParameters<Octokit>; I'm open to a PR |
Created PR #646 |
🎉 This issue has been resolved in version 5.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 5.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
What happened?
I am trying to use OctokitOptions in a typescript project for DenoJS, but am getting the following error when using this import
import { OctokitOptions } from "@octokit/core";
Not sure how to handle, thanks for the help.
Versions
octokit/core: https://esm.sh/@octokit/[email protected]
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: