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

easier-type-checker

v1.0.2

Published

Just advanced version of type checker, made simple to use

Downloads

5

Readme

easier-type-checker

usecase

import types from 'easier-type-checker'

//code goes here

find

use find to find what types are the variable. (one variable can have many types) example:

types.find("5") //return [ 'int', 'number' ]
types.find(5) //return [ 'number', 'char', 'string' ]

return type: string[]

is

use is to check if variable is right type or not example:

types.is.number(5); //return true
types.is.number('5'); //return true

types.is.int(5) //return true
types.is.int('5') //return false

//and etc.

return type: string[]

is is an object, so you can do:

Object.keys(types.is).join('\n');

to see the list of all types that are implemented

Types

Types is raw version of is. Its a Map. So you can implement/add your own types to it easily, and then convert to an object:

Types.Types.set("<your type>",<func>);
//will become the same thing as an original is
const is = Object.fromEntries(Types.Types);

why not use Types rather than is?

it will be ugly:

Types.Types.get("number")(5)

and also typescript might say warning, because Map can return undefined, so u would need to write something like this:

let answer = Types.Types.get("number")
if(answer!==undefined) answer = answer(5);

or something similar

full list of implemented types

int
object
map
number
string
symbol
null
array
ENG
char
symbols