-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
README refers to non-existant exported Action
member
#2094
Comments
This isn't a bug with deno, but with our documentation. There isn't any You can use |
Action
member
OK, thanks for looking into this so quickly. I am still seeing issues though, the script looks like this now: import { Octokit, App} from "https://cdn.skypack.dev/octokit?dts";
const o = new Octokit();
console.warn(`${JSON.stringify(o)}`); This prints
However, if I try to access It seems like the type definitions are not picked up by tsc? |
it's |
Also note that there is a known problem with Deno right now, likely related to our dependency on Bottleneck, see the thread at #2075 |
Thanks for the pointer.
|
It does work in the browser: import("https://cdn.skypack.dev/octokit").then(pkg => {
const octokit = new pkg.Octokit()
console.log(octokit.rest.projects)
}) so I assume it's probably related to the problem described at #2075 |
closing in favor of #2075 |
I am trying out the deno example in the README, and it does not work:
The text was updated successfully, but these errors were encountered: