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

zletils

v0.0.1-f

Published

My handy utils

Downloads

3

Readme

zletils

My handy utils

If, at least sometimes, you really care about guaranteed run-time type safety, these are for you.

Usage

import { typedProps } from 'zletils';

const manyValues = {
  a: 1,
    b: '2',
    c: false,
    d: true,
    e: null,
    f: document.createElement('div'),
    g: () => ({}),
    h: undefined,
    i: {},
    j: [],
    k: new RegExp('abc'),
};
const test = typedProps({
  values: manyValues,
  strict: true // Optional: causes the set function to throw, not log, en error on incorrect assignment attempts
});

test.a = 3
test.a // 3
test.a = []
index.js:60 ### Cannot change property type Number with Array

test.a = '511'
index.js:60 ### Cannot change property type Number with String

test.k = 'no wai'
index.js:60 ### Cannot change property type RegExp with String

test.k = /^no wai$/
/^no wai$/

test.e // null
test.e = null
test.e = 'OK'
test.e = null
index.js:60 ### Cannot change property type String with null

test.g // () => ({})
test.g = {}
index.js:60 ### Cannot change property type Function with Object

test.g = function ohYeah() {}
test.g // ƒ ohYeah() {}

Use an existing object

import { typedProps } from 'zletils';

const foo = new Object({ cool: 'story' });

const fewValues = {
  a: 1,
  b: '2',
  c: false,
};
const test = typedProps({
  values: fewValues,
  strict: true // Optional: causes the set function to throw, not log, en error on incorrect assignment attempts
}, foo);

console.log(foo); // {a: 1, b: "2", c: false, cool: "story"}

Single prop

Having a getter and setter functions for each and every property is expensive and completely non-sensical in at least 99.99999% of any real case scenario. It serves no real purpose.

However, if you really, really need a run-time guaruantee for a single property, that's fine.

Here's how

import { typedProp } from 'zletils';

const arr = typedProp([123]);
console.log(arr); // TypedProp {enumerable: true, get: ƒ, set: ƒ}

const someObject = Object.defineProperties({}, {
  arr,
  something: { value: 'else', enumerable: true, wriatable: true },
});

console.log(someObject); // { something: "else", arr: Array(1) }