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/vite

v0.0.5

Published

Vite 8 adapter for connected memoized-dom module graphs

Downloads

614

Readme

@memoized-dom/vite

Vite 8 adapter for compiler-linked memoized-dom applications.

import { defineConfig } from 'vite';
import memoizedDom from '@memoized-dom/vite';

export default defineConfig({
  plugins: [
    memoizedDom({
      entries: 'src/App.tsx',
      rootId: 'App',
    }),
  ],
});

Entries are authored graph roots, not necessarily the browser bootstrap module. The adapter follows local static value imports with Vite's resolver, compiles the graph through compileModules(), and caches output per Vite environment.

Vite HMR cannot replace existing factory closures or their module state bindings. A change to any managed graph file therefore invalidates all managed modules through the environment module graph and requests a full browser reload. This is conservative state-resetting development behavior, not state-preserving component HMR.

Run the package-owned integration tests and adapter benchmark with:

bun run --cwd packages/vite test
bun run --cwd packages/vite bench