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

v0.7.2

Published

Webpack 5 integration for eXact TypeScript, TSX, and generated artifacts.

Readme

@exactjs/webpack-plugin

Webpack 5 integration for eXact TypeScript, TSX, and generated artifacts.

Configuration

For applications in a nested workspace directory, configuration discovery and library authorization use Webpack’s compiler context. Set applicationRoot to override that location explicitly.

import { ExactWebpackPlugin } from '@exactjs/webpack-plugin';

export default {
	resolve: { extensions: ['.tsx', '.ts', '.js'] },
	plugins: [new ExactWebpackPlugin()]
};

Use target: 'server' and serverComponents: true for server builds. The ./loader export is available when an existing rule needs explicit loader composition. Both the installed pre-loader and the explicit loader leave ?raw and ?url requests to your Webpack asset rules. For source text, use an asset/source rule with resourceQuery: /(?:^|[?&])raw(?:[=&]|$)/. The same TSX file can also be imported as an executable component. For browser builds, set renderMode: 'hydrate' when the entry adopts SSR HTML or renderMode: 'client' when it only performs fresh mounts. The default universal contract remains available when one output must support either mode. For an SSR-only server entry, set renderMode: 'server-render' to omit continuation-dispatch executors. Keep the default for a server bundle that also handles continuation requests.

What the plugin handles

The plugin installs the compiler loader, emits executable JavaScript from TypeScript and TSX, applies client or server export conditions, reports diagnostics, supports source maps and watch invalidation, verifies browser isolation, and can configure React compatibility.

For target: 'server', the loader records compiler component facts and the module factory authorizes resolved package instances before Webpack builds them. Configure componentLibraries once in exact.config.*; successful compilations emit private authorization and audit assets under .exact/. Client-only component code does not use this additional gate.

Attributed enhancement imports populate the application-bundle enhancement catalog. The plugin aliases DOM, hydration, and SSR entry points to the shared facades that supply that catalog; application aliases remain authoritative, and the compiler does not maintain a plugin registry. An attributed namespace export with scope: 'package' in exact.config.* supplies a virtual namespace to every package component; Webpack emits its catalog registration only from modules that activate it.

Optional debug settings control private server catalogs and compact browser instrumentation. Disable both for hardened output. See eXact DevTools.

Microfrontends

When exact.config.* enables @exactjs/microfrontends, the client plugin emits each configured exposure as an independent ESM entry and preserves its CSS, assets, lazy chunks, hydration registration, and provided-package identity. No additional Webpack plugin is required.

Use onRemoteEntries to publish successful production entries and onRemoteDevelopmentEntries to expose stable development module IDs. Failed watch compilations do not publish a partial map; the previous successful deployment map remains valid.

Shared application helpers can live in ordinary .ts or .js modules. See the task reference for pending state and receiver limits.

Policy conflicts warn at build and reject execution. Correct the policy and rebuild before deployment.

Documentation | Source on GitHub