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

@recubed/object-satisfies

v0.1.2

Published

key-based object validation

Downloads

6

Readme

MIT
license Build
Status Coverage Status CodeFactor dependencies
Status devDependencies Status

object-satisfies

Tiny helper library written to simplify the task of fine-grained object validation. Pretty much what you can do with ramda/where or lodash/conforms except that it's smaller, prioritizes typings and makes field-level predicates aware of field existence (not just emptiness).

Given an arbitrary object, e.g.:

const scenario = {
  a: 42,
  b: 'ohai',
}

object-satisfies allows key-based predicate composition, i.e.:

import satisfies from '@recubed/object-satisfies';

const spec = satisfies({
  a: x => x === 42,
  b: x => typeof x === 'string',
  // c is optional and not in the 'scenario' object, object-satisfies 
  // lets you run a predicate regardless, additionally - field existence flag is 
  // added to the list of predicate arguments; 
  c: (x, found) => !found     
})
const outcome = spec(scenario);

console.log(outcome); // true

Please note that type-wise, example above will only compile because the type of scenario object is unavailable at the time spec argument is defined. To overcome this limitation one would need to specify generic argument explicitly, like this:

import satisfies from '@recubed/object-satisfies';

const spec = satisfies<typeof scenario>({
  a: x => x === 42,
  b: x => typeof x === 'string',
  c: (x, found) => !found     
});

...however, if validation of explicitly typed "scenario object" against a spec argument is performed one needs to make sure the former is a superset (key-wise) of the latter, optional properties do count. To fix the compilation error caused by the piece of code above following type definition would need to be provided:

type Scenario = { 
  a: number;
  b: string;
  c?: () => {};
};
const scenario: Scenario = {
  a: 42,
  b: 'ohai',
};

See tests for additional use cases / behaviours.