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

v0.7.2

Published

Vite integration for compiling and serving eXact applications.

Readme

@exactjs/vite-plugin

Vite integration for compiling and serving eXact applications.

Configuration

Configuration discovery and authorization follow Vite's root. Override with applicationRoot.

import { exact } from '@exactjs/vite-plugin';
import { defineConfig } from 'vite';

export default defineConfig({ plugins: [exact()] });

Applications with separate client and server configs can build both in one process and reuse one native compiler project generation:

import { buildExactViteApplication } from '@exactjs/vite-plugin/build';

await buildExactViteApplication(['vite.config.ts', 'vite.server.config.ts']);

Use target: 'server' for server artifacts, serverComponents: true for split server-component builds, and reactCompatibility only when the application consumes React-owned packages. The plugin rejects mismatched Vite and eXact build targets. Set renderMode: 'hydrate' for a browser bundle that adopts SSR HTML, or renderMode: 'client' for fresh browser mounts. These modes prune unused contract fields. The default universal behavior preserves the complete contract. For an SSR-only server entry, combine target: 'server' with renderMode: 'server-render' to omit later continuation-dispatch executors. Keep the default for a server bundle that also calls composeExactExecutorContract() or handles continuation requests.

What the plugin handles

The plugin compiles eXact TSX, configures the automatic JSX runtime, resolves generated .exact facades, preserves Vite's platform conditions, supports HMR, and keeps server-only code out of the final browser graph. Middleware development SSR uses the same plugin for ssrLoadModule(). Installed @exactjs/* packages and declared participating component libraries stay in its SSR graph so target exports and enhancement catalogs remain coordinated without manual registration or an eXact-specific ssr.noExternal rule. Published component libraries and their framework runtimes also stay outside Vite dependency optimization so renderer enhancement imports remain active and hydration shares one runtime instance.

For target: 'server', compiler-recorded component package requests are resolved and authorized before Vite loads their implementations. Configure trust through componentLibraries in exact.config.*. Builds emit server-private authorization and audit manifests under .exact/. Client-only package components do not pass through this server authorization gate. Server dependency discovery waits for authorization. Allowed packages use ordinary Rollup chunking.

Attributed enhancement imports populate the shared bundle-local catalog, supplied through renderer facades. A scope: 'package' namespace supplies a virtual namespace to every package component. Only modules that activate it emit registration. The compiler maintains no plugin registry.

The optional internationalization integration analyzes source messages, watches XLIFF or protocol-JSON catalogs, and emits component-owned translation companions. It supports descriptor callbacks and compiler-proven client capability providers. See internationalization for catalog ownership, locale selection, invalidation, and polyfill configuration.

include and exclude select transformed modules. Tests stay runner-owned unless compileTestModules is true. typescriptConfig can select their test project. Vite ?raw and ?url imports preserve host assets alongside executable TSX imports, without entering compilation or replacing component authorization facts.

Optional debug settings control private inspection catalogs and browser instrumentation. Share a stable build identity across production targets.

See eXact DevTools and component registries. Component authorization permits in-process server execution and is not a JavaScript sandbox.

Documentation | Source on GitHub

One browser HTML file

import { defineConfig } from 'vite';
import { exactSingleFile } from '@exactjs/vite-plugin';
export default defineConfig({ plugins: [exactSingleFile()] });

This builds one HTML entry with embedded scripts, styles, imported images, and fonts. Dynamic imports are folded into the script. Use hash navigation for offline file: URLs. Import assets through Vite. External CSS/modules, unresolved URLs, srcset, separate worker files, and server operations are rejected. Optional application fetches still require connectivity.

buildExactViteApplication() accepts an optional afterBuild(configFile) callback to publish client asset metadata before the server build while retaining the shared compiler generation.