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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@nutgaard/typeanalyzer

v1.1.0

Published

Captures and analyzes datastructures

Readme

Type analyzer

A port of a similar library written in kotlin.

Useful in cases where you're not quite sure how a datastructure looks like, e.g whats nullable and whats not.

This library helps the investigation into what you can expect by capturing the structure, and generating examples classes for you.

Usage:

import {Typeanalyzer} from "./Typeanalyzer";

const serviceAnalyzer = new Typeanalyzer();

function somemethod(): Map<string, unknown> {
    const data = service.getSomeData();
    serviceAnalyzer.capture(data);
    return data;
}

NB: You should not reuse an instance of Typeanalyzer for objects you expect to be different.

Typeanalyzer captures and maintains an inner representation of the datastructures it has captures, which fields that are nullable, and what their types should be (See the representation in the snapshot).

To get the representation programmatically you can call serviceAnalyzer.report(), which returns the most up-to-date representation. This representation can be used to generate pseudo-code for kotlin and typescript:

const typescriptCode = serviceAnalyzer.print(new TypescriptFormat());
const kotlinCode = serviceAnalyzer.print(new KotlinFormat());

In-depth:

The typeanalyzer works by capturing the structure of a given value, and gradually relaxing the constraints.

F.ex;

const analyzer = new Typeanalyzer();
analyzer.capture(["value"]); // ListCapture[PrimitiveCapture[type = TEXT, nullable = false]]
analyzer.capture([null]);    // ListCapture[PrimitiveCapture[type = TEXT, nullable = true]]

If the typeanalyzer has not previously seen a valid type for a field, it tries to specify it if given the chance.

F.ex;

const analyzer = new Typeanalyzer();
analyzer.capture([null]);     // ListCapture[NullCapture[]]
analyzer.capture(["value"]);  // ListCapture[PrimitiveCapture[type = TEXT, nullable = true]]

In the previous example the analyzer was initally passed null in the first capture, and the specified field was thus marked as nullable. This is in contrast to if the analyzer has not yet seen any values in the list.

F.ex;

const analyzer = new Typeanalyzer();
analyzer.capture([]);         // ListCapture[UnknownCapture[]]
analyzer.capture(["value"]);  // ListCapture[PrimitiveCapture[type = TEXT, nullable = false]]
analyzer.capture([null]);     // ListCapture[PrimitiveCapture[type = TEXT, nullable = true]]