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

unprunk

v0.1.1

Published

What the funk is a prunk?

Downloads

6

Readme

What the funk is a prunk?

A Prunk is defined as the intersection of the following:

  • a Result
  • a function which accepts Props and returns a Result
  • a function which accepts Props and returns a Promise which resolves with a Result
  • a Promise which resolves with a Result
  • a Map of keys and Prunks

In typescript that looks like the following:

export type PrunkFunc<Props, Result> = (
  props: Props
) => Result | Promise<Result>;

export interface PrunkMap<Props, MapType, Key extends keyof MapType>
  extends Map<Key, Prunk<Props, MapType[Key]>> {}

// the main Prunk type
export type Prunk<Props, Result> =
  | PrunkFunc<Props, Result>
  | Promise<Result>
  | PrunkMap<Props, Result, keyof Result>
  | Result;

Why would I want to use a prunk?

Prunks are mostly useful when accepting configuration for a component or library that may externalize a large portion of business logic based on values not known at the time of configuration. They're a sort of opt-in callback, where you can either provide a known static value, or provide a callback to defer configuration or add more complex logic.

TODO: add some examples here demonstrating use cases

Installation

npm i -s unprunk

Both typescript and javascript support come out of the box.

Usage

import unprunkWithProps from 'unprunk';

const test = async () => {
  try {
    // props our functional prunks should expect
    const props = { value2: 'value2', value3: 'value3' };
    // unprunk is a function which will do the actual unprunking
    // unprunk will always return a Promise which will resolve with result
    const unprunk = unprunkWithProps(props);
    /**
     * config will equal:
     * {
     *   prop1: 'value1',
     *   prop2: [false, true, 'value2'],
     *   prop3: {
     *     nested: 'value3'
     *   }
     * }
     */
    const config = await unprunk({
      prop1: Promise.resolve('value1'),
      prop2: Promise.resolve([
        false,
        Promise.resolve(true),
        ({ value2 }) => Promise.resolve(value2)
      ]),
      prop3: Promise.resolve({
        nested: ({ value3 }) => value3
      })
    });
  } catch (error) {
    console.log(error);
    throw error;
  }
};

Why Prunk?

props/promise + func/thunk = prunk

License

Licensed under MIT