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

typesafe-object

v0.1.0

Published

Simple composable typesafe object validation and data conversion, with no dependencies.

Downloads

1

Readme

typesafe-object

Simple composable typesafe object validation and data conversion, with no dependencies.

Validating and converting data that is out of your control can be an annoying repetitive chore.

This happens all the time when accepting POST bodies in http endpoints, events in serverless functions, when integrating with external APIs or queueing systems, or any other piece of code that accepts data from the outside world.

  • No dependencies
  • No codegen
  • No hassle

How to use

There are two steps:

  1. define your field types
  2. create an object parser for a schema

Initialize with your field types

These are the functions that validate and parse incoming fields.

The key names in this object are important -- they will be used in the next step to specify how each field in an object is parsed.

import typesafeObject from 'typesafe-object'

const typesafe = typesafeObject({
  capitalizedString: value => ('' + value).toUpperCase(),
  roundedInteger: value => Math.round(Number(value)),
})

Create an object parser from a schema

A "Schema" is an object that has a key for each field, and the value is one of the field types you defined.

The keys here match the fields on the objects you will parse. The values are the keys that we used above for the field definitions.

This is typescript-enabled, so you will see type errors if any of the field types don't match the ones you set up in the first step.

const parser = typesafe.objectParser({
  firstName: 'capitalizedString',
  lastName: 'capitalizedString',
  age: 'roundedInteger'
})

Now parse some data:

const arthur = parser.parse({
  firstName: 'Arthur',
  lastName: 'Dent',
  age: '53.7'
})

console.log(arthur.firstName) // => 'ARTHUR'
console.log(arthur.lastName) // => 'DENT'
console.log(arthur.age) // => 54


// the field types are determined by the return types of the
// functions we used above. Since the 'roundedInteger' field
// returns a number, arthur.age is a number
const age: number = arthur.age

// This will be a type error.
// There is no field named 'answer'
console.log(arthur.answer)