npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

http-to-fetch

v1.1.0

Published

Transform node:http requests into requests that match the browser Fetch API.

Downloads

13

Readme

http-to-fetch

Very simple handler for converting node:http's IncomingMessage object into a Fetch API Request

Usage

npm install http-to-fetch

After starting a server using node:http, listen for requests and convert the objects. Example:

// (typescript)
import http from "node:http";

http.createServer((request, response) => {
    // create request and return 200 response
    const req = new Request();
    req.translate(request, response);

    // the HTTPResponse object will automatically close the request!
    new HTTPResponse(
        `Hi mom!`, // body
        {
            // options
            status: 200,
            headers: new Headers({
                "Content-Type": "text/plain",
            }),
        },
        req // request
    );
}).listen(8080);

Usage (with PluginAPI)

This library also includes a "Plugin API" that makes the whole process much more like the the native web Fetch API.

Using a basic loader (or the one from /example), just listen and handle the request.

// (typescript)
import loader from "./loader.js";

// start server
loader.start(8080);

// bind endpoint
loader.bind({
    endpoint: "/", // serve everything on the root endpoint (/)
    fetch: (Request, Response) => {
        return new Response(
            "Hello, world!", // body
            {
                // options
                status: 200,
                headers: new loader.Headers({
                    "Content-Type": "text/plain",
                    "Hi-Mom": "It works!",
                }),
            }
        );
    },
});

This loader uses the Plugin.registerEndpoint to register an endpoint for the endpoint you defined.

// (typescript)
// from: loader.ts
// ...
export function bindEndpoint(params: { endpoint: string; fetch: fetch }) {
    // create plugin client
    const pluginClient = new Plugin();

    // update plugin client bindings
    pluginClient.bindOnRegEndpoint((endpoint: string, fetch: fetch) => {
        endpointList[endpoint] = fetch;
        endpointList[`${endpoint}/`] = fetch; // account for trailing slash
    });

    // bind endpoint
    pluginClient.registerEndpoint(params.endpoint, params.fetch);
}
// ...

loader.bind just calls loader.bindEndpoint

// (typescript)
// from: loader.ts
// ...
export default {
    bind: bindEndpoint,
    // ...

It is recommended that you just use the example loader and extend it.