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

@lukekaalim/to

v1.2.0

Published

A small library to help build typesafe object converters and checkers

Downloads

3

Readme

@lukekaalim/to

CircleCI

There and ~~back again~~.

Installation

npm i @lukekaalim/to

Usage

const { toString, toNumber, toObject } = require('@lukekaalim/to');

const toUser = toObject({
  name: toString,
  age: toNumber,
  meta: toObject({
    createdAt: toNumber,
    modifiedAt: toNumber,
  }),
});

const userJson = `
{
  "name": "luke",
  "age": 24,
  "meta": { "createdAt": 0, "modifiedAt": 0 }
}
`;

const user = toUser(JSON.parse(userJson));

Recursive object structure checking for typing those pesky models.

API

toAString

const { toAString } = require('@lukekaalim/to');

const name = toAString('luke'); // name === 'luke'

Identity if the value is a string, throw a NotStringError if not. Naming is seperate than other (Normall would be toString) but is different to avoid naming clashes with the standard object.toString(); method

toNumber

const { toNumber } = require('@lukekaalim/to');

const age = toNumber(25); // age === 25

Identity if the value is a number, throw a NotNumberError if not.

toBoolean

const { toBoolean } = require('@lukekaalim/to');

const isDev = toBoolean(true); // isDev === true

Identity if the value is a boolean, throw a NotBooleanError if not.

toObject

const { toObject } = require('@lukekaalim/to');

const toLukeName = value => {
  if (value === 'luke') {
    return value;
  }
  throw new Error('I\'m not luke!');
};

const toLuke = toObject({
  name: toLukeName,
});

const luke = toLuke({ name: 'luke' });

Given a map of converters, creates a function that accepts an object (Throws a NotObjectError or ValueWasNullError error if not), and creates a new object with properties based on running the arguments through the converter who's key is the property's key. A converted just needs to accept any value, and return anything.

If a converter throws an error, that error is wrapped in a PropertyError.

toArray

const { toArray } = require('@lukekaalim/to');

const toFunc = value => {
  if (typeof value === 'function') {
    return value;
  }
  throw new Error('Not a function!');
};

const toFuncArray = toArray(toFunc);

const funcArray = toFuncArray([console.log, console.error]);

Given a converter, creates a function that accepts an array (Throws a NotArrayError error if not), and creates a new array with elements based on running the converter through each element. A converter just needs to accept any value, and return anything.

If a element throws an error, that error is wrapped in a ElementError.