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

yahf

v0.1.5

Published

Yet Another HTTP Framework, that you don't really need

Downloads

1

Readme

YAHF

Yet Another HTTP Framework, that you don't really need

Trying to build a HTTP server framework, without using any external modules, because who needs npm?!

Everything is as I want it to be, not as one might used to.

Continuous Integration

API

  • Create new YAHF instance, with default options

    import YAHF from 'yahf';
    
    const server = new YAHF();
  • Options that can be passed to the YAHF constructor, as an object:

    • logger: (str: string) => void. Defaults to console.log.
    • port: number. Defaults to 1337.
  • useMiddleware(middleware: (data) => void).

    • Any result returned from this functions will be ignored.
    • Will be called in FIFO.
    • Return this so it can be chained.

example:

import YAHF from 'yahf';

const server = new YAHF()
server.useMiddleware((data) => {
    server.logger(data);
})
  • addHandler(path:string | string[], handler: async data => RequestResult | undefined.

    • Return this so it can be chained.
    • RequestResult is optional.
  • RequestResult

    {
        statusCode: number; // Defaults to 200
        contentType: string; // Defaults to 'application/json'
        payload: any;
    }
  • start() : Promise<this>

    • Will start the server, listening on the port was passed in.
    • Resolves to this so it can be chained.
  • kill() : Promise<this>

    • Will close the server.
    • Resolves to this so it can be chained.
  • logger : (str: string) => void

    • Returns the passed in logger. will default to console.log

Request lifecycle

  • Every middleware/handler will get the following object:
    {
      path: string;
      query: URLSearchParams;
      method: 'GET' | 'POST' | 'PUT' | 'DELETE' | 'PATCH'...;
      headers: object;
      payload: string; // Defaults to an empty string
    }
  • Middlewares are called FIFO, and called before any handler.
  • Handlers are called for exact match for the path, without starting /.