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

@memoized-dom/language-service

v0.0.5

Published

TypeScript language-service diagnostics and code fixes for memoized-dom

Readme

@memoized-dom/language-service

TypeScript editor diagnostics and code fixes for memoized-dom. Compiler errors come from @memoized-dom/compiler's structured graph diagnostic API, so the editor, Vite overlay, and direct compiler report the same restrictions. Compiler diagnostics preserve the authored ESTree start/end range, so route attributes, invalid writes, and other failures are underlined at their actual source node instead of a generic one-character position.

Add the plugin to the application tsconfig.json:

{
  "compilerOptions": {
    "plugins": [
      {
        "name": "@memoized-dom/language-service"
      }
    ]
  }
}

TypeScript language-service plugins run in editors powered by tsserver. They do not add diagnostics to standalone tsc; the analysis core is kept separate so a future CLI can report the same diagnostics in CI.

The first diagnostic suggests const for initialized let bindings that are never reassigned. Its message explains that memoized-dom reactivity follows reads and writes rather than declaration keywords; const arrays and objects can still mutate their contents. The editor fix changes only the declaration keyword.

Set "preferConst": false on the plugin entry to disable this diagnostic. Set "compilerDiagnostics": false only when compiler errors should be hidden from tsserver.