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

v0.7.1

Published

Enhancement-first internationalization contracts and runtime for eXact

Readme

@exactjs/intl

Enhancement-first internationalization for eXact. Authored TSX remains the unavailable-capability fallback while analyzed builds use validated, data-only plans and ordinary component ownership.

@exactjs/intl combines a cross-build plugin with a standard eXact component library. Shared adapter integration coordinates extraction and catalogs, while ordinary component branding covers IntlProvider and explicit intl components. The enhancement entry exports message, plural, select, currency, unit, cldr, and supported translated properties.

Usage

Register the enhancement for every compiled component in the package:

// exact.config.ts
export * as intl from '@exactjs/intl/enhancements' with { type: 'exact-enhancement', scope: 'package' };
import { defineConfig } from '@exactjs/config';

export default defineConfig({});

Then author messages without repetitive component imports:

import { createIntlEnvironment, IntlProvider } from '@exactjs/intl';

const environment = createIntlEnvironment({ sourceLocale: 'en-US', locale: 'en-US' });

function Page(props: { name: string }) {
	return () => (
		<IntlProvider environment={environment}>
			<main intl:locale>
				<p intl:message>Hello, {props.name}.</p>
			</main>
		</IntlProvider>
	);
}

intl:locale reuses the nearest provider (or creates a zero-configuration locale scope) and keeps the target intrinsic's lang and dir attributes synchronized across SSR and client updates. Its locale value uses the CLDR-backed IntlLocaleString type; call defineIntlLocale(value) to validate and narrow a dynamic string. Semantic unit preferences otherwise come directly from CLDR locale data and only need configuration for intentional application or user overrides. Prefer a semantic intrinsic host for a formatter that owns its complete content; reserve _ for a narrower inline range, multiple independently formatted regions, or a value with no suitable host. Selectors and formatters nested in intl:message join its single reorderable translation unit. A standalone plural, select, currency, unit, or cldr activation creates an implicit message; co-target it with intl:message when the scope needs a readable name.

Message-only fragments stay transparent; contributed attributes such as intl:locale create a default span. intl:intrinsicFragment selects another constant tag; consecutive same-tag owners share a host. In title/textarea, generated markup is literal text, with no parent-prop promotion.

IntlProvider supplies active/source locales to this.intl. Omitted locales and requests matching sourceLocale use the active locale; other explicit locales remain explicit. Equivalent formatters share core's bounded realm-wide cache. The compiler lowers native constructors and locale-string calls automatically; helpers can import intl from @exactjs/core to share the cache.

Message keys hash a generic translator-facing text and placeholder contract. An optional authored message name becomes a readable prefix; exact bindings and formatter options use a separate execution-contract hash and do not enter XLIFF.

The Node-only @exactjs/intl/language entry helps editors diagnose message, locale, and catalog problems. Package configuration covers every component. File-local imports narrow the scope, and translate="no" excludes content.

Automatic destination units use pinned Unicode CLDR 48 preferences; explicit application policy takes priority while intl:convert-to stays fixed. See the reference. For measurement changes, add difference to intl:unit or intl:cldr. A subtraction such as {daytime - nighttime} exposes both endpoints. An already-calculated temperature change converts without offsets. Nonlinear changes, such as MPG to L/100 km, require the subtraction endpoints or difference={{ from: previous, to: current }}. Values remain signed.

Component libraries can opt into IntlScalarPresentationContext to receive current scalar text, source fallback, locale, and direction; structurally movable messages remain render-only. Runtime values use resolveIntlMeasurementPresentation() plus the public conversion and formatting operations, reusing the same CLDR, preferences, precision, formatter cache, and bidi policy as intl:unit.

Documentation | Source on GitHub