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

@cirrusct/ts-reflector

v1.0.98

Published

Typescript Reflector

Downloads

134

Readme

ts-reflector

The bulk of the heavy lifting code from: https://github.com/s-panferov/tygen

tygen model is to walk all types and references in every source file in the entry package and all of its references in a ts project (whether used by entry package or not), create reflected objects with ts meta data, and immediately generate json files on disk to be consumed by documentation generation code.

This adaptation is focused on using tygen's code to parse out a project and using the reflected data store in-memory, and not on generating reflections to files.

This code is great for getting all of the ts data into a more usable form, but is expensive and slow as it parses lots of modules that are not necessarily used by the package we want to document.

Would eventually like to adapt to only walk modules referenced by entry package as required by the documentation code, but works for now..