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

structured-pyright

v1.0.11

Published

Type checker for structured editors using the Python AST

Readme

Structured Pyright

Warning: This fork is full of horrible hacks and commented out code. Support is best-effort, but contributions are welcome!

This repo is a fork of pyright hacked for use in a web-based structured editor. Please see the pyright repo for more information about how it works.

Like most type checking, type inference, and autocomplete tools, pyright is built on the assumption that code is expressed as a series of text files. When you're trying to build a structured editor which operates on the code at an AST level, you can't make use of these tools because the public API works only in terms of text files and line/character offsets.

This fork effectively punches holes through the pyright API to allow the parse tree to be provided to pyright's internal binding and type evaluation logic without it being read from a text file. Elements of that parse tree can then be used for type checking and autocomplete without the need for there to be some kind of intermediate text format.

All credit to the folks at Microsoft as well as other contributors to pyright. Sorry for desecrating your work.

Differences to Pyright:

  • Adds methods to override the parse tree to skip parsing from a text file
  • Exposes internal parse tree types and enums (to enable building it yourself)
  • Supports running in a browser by faking out the filesystem access and adding polyfills for nodejs libraries
  • Expects typeshed type definition files to be hosted at a URL that can be fetched when needed
  • Modifies a lot of operations to be async to enable async fetching of type definition files

As much as possible it aims to keep upstream code separate to make it easier to pull updates. That being said, some of the above involved some invasive changes.

Developer Guide

To keep it separate, the structure-pyright module is in packages/structured-pyright.

To build:

cd packages/structured-pyright
npm install
npm run build