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

@dojo-ng/framework

v0.3.4

Published

Dojo NG framework — clean-room v()-only VDOM renderer (ESM, property-first for custom elements, O(n) keyed reconciliation)

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

saysomethingsaysomethingbitranchbitranchjepejepe

Keywords

dojovdomrendererweb-componentsesm

Readme

@dojo-ng/framework

Clean-room v()-only VDOM renderer — ESM, property-first for custom elements, O(n) keyed reconciliation. See CHANGELOG.md for the design writeup and size/perf numbers.

Development

The canonical repository is Mercurial, hosted on foss.heptapod.net:

hg clone https://foss.heptapod.net/dojo-ng/framework
cd framework
npm install
npm run build

Hosting for this repository is provided at no cost by foss.heptapod.net. Heptapod is published by Orbeet, and the instance runs on infrastructure donated by Clever Cloud. Our thanks to both for supporting free and open source projects.

Testing

Three layers, in increasing cost:

| Command | What it runs | |---|---| | npm run smoke | Zero-dependency has()/tsx() sanity checks (smoke/has.mjs, smoke/tsx.mjs) | | npm run test:golden | Goldens — the renderer's behavior spec, driven over a mock DOM (test/vdom.test.mjs, test/factories.test.mjs) | | npm run test:browser | Real-browser smoke — the mock-vs-real-DOM gaps a mock can't fake (real events, real focus, real rAF, real CSSStyleDeclaration, a real custom element), on Chromium, Firefox, and WebKit (test/browser/*.test.mjs) |

npm test runs build + smoke + goldens (not the browser layer, which needs Playwright's browsers: npm install && npx playwright install, once).

npm run bench is the performance gate — after any renderer change, confirm keyed-reverse stays ~O(n) (10k rows in tens of ms, not seconds).

The goldens are the authoritative spec: if a browser-layer test exposes a real renderer bug, the fix lands with a new golden, not just a browser assertion.

License

BSD-3-Clause. See LICENSE.