Deno compatibility

Open
#34 14 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
28/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
deno, typescript
Domain
api, developer-experience

Research direction

Start by reviewing how axios is used and where TypeScript import paths omit .ts extensions. Check the proposed fetch replacement with a Node.js polyfill and verify the package can run under Deno without breaking Node.js support. Done means both checklist items are addressed and Deno compatibility is demonstrated.

Written by the indexing model from the issue text.

Description

enhancement

It would be nice if we could use this within Deno. Here are the things that would have to occur if we were to proceed with this:

  • Switch axios to fetch (with the polyfill node-fetch for node.js)
  • Explicitly define '.ts' file extensions

There are many reasons to use Deno over Node, including the built-in TypeScript support, Permission system and much more

Is there a Revolt channel I could use to discuss revolt.js? It would be best for fast communication

Dominant language
TypeScript
Stars
285
Forks
108
Avg merge
16h 49m
Merged PRs (30d)
3

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stoatchat/javascript-client-sdk

All issues in stoatchat/javascript-client-sdk

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.