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

@higherkinded/bottom

v1.1.0

Published

Simple stub factories reminiscent of undefined in Haskell

Downloads

3

Readme

Bottom

Check out on NPM Check out on
NPM License Typedefs JS Support

A set of easily pluggable and extremely touchy empty definitions.

Naming

The name is ripped off the Haskell community's term for undefined. The idea partially comes from there as well — a polymorphic value that can be put anyplace to signify unimplemented functionality.

Motivation

I've had a lot of situations where I had to implement some large module and had to write the bottom function myself just to plug something in place of implementation for some time. What was also quite important to it is to fend off any accidental uses by causing the bottom to throw exceptions. Being tired of rewriting this multiple time and, surprisingly, seeing no alternative implementations (at all), I've written this library. It covers use cases of both TypeScript bottom-related needs and JavaScript bottom-related needs.

How do I?

So how to use it? In case of TypeScript functions, it will be...

import { bottom, bottomFn } from 'bottom';


// ...like this:
const product: (...args: number[]) => number = bottom;


// Or like this:
const someComplexProcedure = <A, B, C, R>(a: A, b: B, c: C): R => {
  /* 
    ...
    
    Some partial implementation here
    
    ...
  */
  
  return bottom();
};


// Or perhaps you want to carry the name?
const namedFunction: <A, R>(a: A): R = bottomFn('namedFunction');


// Also OK in return statement:
const someNamedProcedure = <A, B, C, R>(a: A, b: B, c: C): R => {
  /* 
    ...
    
    Some partial implementation here
    
    ...
  */
  
  return bottomFn('someNamedProcedure')();
};

For classes, you have these options:

import { Bottom, bottomMethod } from 'bottom';

// Declared but unimplemented and uninstantiable class
class Foo extends Bottom {

  /* Bottom-ed method of a class, carrying the info about who they are and who
     owns them. */
  static someMethod = bottomMethod('someMethod', 'Foo');

}