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 🙏

© 2026 – Pkg Stats / Ryan Hefner

type-forcer

v1.0.2

Published

A simple utility lib designed to enforce typescript's types on parses :)

Readme

typescript-type-forcer

A simple utility lib designed to enforce typescript's types on parses :)


Requiremets:

For this to work, you must use the following packages in your project.

ttypescript: https://www.npmjs.com/package/ttypescript typescript-rtti: https://www.npmjs.com/package/typescript-rtti reflect-metadata: https://www.npmjs.com/package/reflect-metadata


Installing:

npm install type-forcer


Using:

There are 3 main functions:

  • forceObjectType:

    • Ensures the object has all of the desired class' required properties recursively, throws MissingFieldException if any required property is null or undefined;
    • Recreates the object with all previous values and all the desired class' functions working as they should be.
    • Ex.: const myObject = forceObjectType(request.body, MyRequestClass, modelIndex, showDebugLogs)
  • forceArrayType:

    • Uses forceObjectType to fix all objects within the array.
    • Ex.: const myObjectList = forceArrayType(request.body, MyRequestClass, modelIndex, showDebugLogs)
  • is:

    • Utility function to compare an object with the desired class name.
    • Ex.: const isMyException = is("MyCustomExceptionClass", error)

What is modelIndex?

When we are converting an object into a class recursively, we must check every level of the object to see if there is another object also needed to be transformed. That problem is easily solved by getting the new class' name and making a new instance of it. modelIndex is literally the file where you must index all of the classes you wish to use in the transformations. Following is an example:

Inside your modelIndex.ts

export * from "./models/myRequest.ts"
export * from "./models/myResponse.ts"

Using it

import * as modelIndex from "./models/modelIndex.ts"

Why should I use your library?

Imagine we have the following classes:

class CustomClass {
    constructor(
        public firstParam: string,
        public secondParam: number,
        public thirdParam: AnotherClass
    ) {}

    doSomething() {
        // Do something
    }
}

class AnotherClass {
    constructor(
        public firstParam: string,
        public secondParam: string
    ) {}

    doSomethingElse() {
        // Do something
    }
}

If we receive an object like so:

{
    "firstParam": "1",
    "thirdParam": {
        "firstParam": "1",
        "secondParam": "2"
    }
}

And we straight up cast it to our type like so: const myObject = jsonObj as CustomClass Typescript will just let it slide but it won't make sure that any of the required properties are actually there and none of our functions will work so we won't really have the class we desired, it's only a fake.

By using type-forcer, we make sure our parse is not a fake, but it also transforms the object into the actual class.