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

@exactjs/dom

v0.7.1

Published

Browser DOM renderer for compiled eXact components.

Readme

@exactjs/dom

Browser DOM renderer for compiled eXact components.

Usage

import { render, unmount } from '@exactjs/dom';

const container = document.getElementById('app')!;
render(<App />, container);

// Later:
unmount(container);

What it provides

The renderer mounts and disposes durable component trees, updates compiler-owned reactive regions, and handles DOM properties, events, bindings, refs, namespaces, portals, keyed lists, Suspense, and hydration markers.

ARIA boolean values remain textual "true" or "false". HTML boolean attributes use presence or omission. For data-*, true writes "true" and false omits the attribute. Supply a string when a textual "false" value is required. Null and undefined omit attributes.

Application components should be compiled before they reach the renderer. Use @exactjs/testing for component tests and @exactjs/hydrate when adopting server-rendered HTML.

Generated application bootstraps may import render from @exactjs/dom/root. That entry makes the compiler-selected capability boundary explicit while retaining the same compiled-component behavior as the main entry.

Compiler-resolved enhancements automatically load their DOM integration beside the component that uses them, including from lazy chunks and microfrontends. An integration that manually constructs enhancement markers and catalogs must import render from @exactjs/dom/enhanced; the ordinary entry intentionally leaves the optional enhancement host out of enhancement-free bundles.

The compiler applies the same bundle-local selection to native modal bindings, target contributions, unsafeHtml(), and the coordinated Activity/Suspense renderer. Compiled modules carry the capability imports required by their output; raw runtime construction of those internal VNode forms is not an alternative component mode.

Documentation | Source on GitHub