Skip to content
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

Deno compatibility #85

Open
gr2m opened this issue Oct 10, 2022 · 0 comments
Open

Deno compatibility #85

gr2m opened this issue Oct 10, 2022 · 0 comments
Labels
deno Type: Bug Something isn't working as documented typescript
Projects

Comments

@gr2m
Copy link
Contributor

gr2m commented Oct 10, 2022

I spent some time on testing with Deno.

Things look good, I even added a smoke test:
#83

However loading the type-only modules (@octokit-next/types*) is not working as expected.

First, there is a problem with https://esm.sh that I described at esm-dev/esm.sh#433. I found a workaround.
But then I ran into a problem with Deno itself: it doesn't seem to parse the types of Type-only packages, unless I'm missing something: denoland/deno#16239

It does work in the TypeScript playground and with node code edited in VS code. But Deno doesn't seem to be able to handle it at this point 🤷🏼

@gr2m gr2m added Type: Bug Something isn't working as documented deno typescript labels Oct 10, 2022
@ghost ghost added this to Bugs in JS Oct 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deno Type: Bug Something isn't working as documented typescript
Projects
No open projects
JS
  
Bugs
Development

No branches or pull requests

1 participant