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

postalien

v0.16.0

Published

NodeJS 14 app with Typescript

Downloads

5

Readme

post-alien | Lightweight framework to create programmable query CLI

Build Status

NPM

Usage

import { postwowan, setVar, getVar } from "postalien";
postalien(request: Requests);

Requests object

Each sub-field act as a sub-level until you define the Request object.

Parent: {
    Child: {
        "Request 1": {
            request: () => fetch(..),
        },
        "Request 2": {
            body: {
                name: `name`,
                url: `{{variable}}`,
            },
            prequest: function () {
                return Promise.resolve(doSomething(this.body));
            },
            request: function (prequest_result?) {
                return fetch(this.body);
            },
            postquest: (request_result?) => {
                setVar(request_result.x);
                return Promise.resolve();
            }
        },
    },
}

Will give you this structure:

Parent
=== Child
   Request 1
   Request 2

Request object

has 4 fields:

  • quiet?: boolean print output of request to console.
  • body?: object literal the optional body for the request, so you can define the body of the request here instead of putting it directly in the request function, this helps if someone want to verify the body structure instead without needing to look into the request function source code. You can also use variable here using the syntax {{variable}}
  • prequest?: executed before request, return Promise, result of Promise will be passed to request
  • request: the request function, return Promise, result of Promise will be passed to postquest
  • postquest?: executed after request, return Promise, result of Promise will be ignored.

The result of these 3 functions are chained one after another: prequest -> request -> postquest. Also, if you want to use the body in one of these 3 functions, make sure you use the function() syntax and not the arrow function, as it doesn't bind this. Nothing stop you from defining another data field than body then use it, but only body field support {{variable}}. To set or get variables in functions, use setVar and getVar, or set it manually in db.json