Redfire

Importing is currently along the lines of ```js import fs from "fs"; import {get} from "./http.js"; ``` Both of those methods (directly sending a request) and creating a request handler/agent...

For this, we should probably use [swc](https://github.com/swc-project/swc) to transpile the TypeScript to JavaScript. In order to prevent unnecessary transpilation, the SHA of the TS file and the transpiled JS need...

All modules already have TypeScript (and Flow) definitions created, I think it's mostly a matter of integrating those into IDEs and stuff.

That's the plan for the future, it's just that I don't want to deal with caching, which is going to be almost certainly required.

I completely forgot about mentioning this here, but until full support is added, I've moved all TypeScript (and Flow) bindings to a seperate folder (). This will be published as...

As of https://github.com/Redfire75369/spiderfire/commit/9e05f8c12da3c1b0d1805cfaa83119ecf2b12b2e, typescript support has been added! You'll still need the global declaration files for your IDE but this is a good step forward. There's also no support for...

[`cargo-nextest`](https://nexte.st/index.html) could also be a possible solution. It seems to spawn each test in a separate process. I'll try it later, after completing the `http` module.

**Old API** ```ts declare module "http" { export type Header = string | string[]; export interface Headers { [key: string]: Header, } type TypedArray = Int8Array | Int16Array | Int32Array...

I have just pushed the first implementation to the [feature/http](https://github.com/Redfire75369/spiderfire/tree/feature/http) branch. In some sense, it may be smarter to implement this as `fetch` first, but a lot of the options...

Since the main features are complete now, I'll be merging this into `master` in a few days. The final-ish bindings are as above. The classes are `Headers`, `Request` and `Response`,...