@palamedes/solid

Breaking minor release at 1.18.0: @palamedes/solid moved from Solid 1 to Solid 2 while Palamedes packages continued their lockstep 1.x releases. A dependency range such as ^1.17.3 can therefore upgrade a Solid 1 app to a Solid 2 adapter and lose Solid 1 compatibility. If your app must stay on Solid 1, pin @palamedes/solid to 1.17.3, the last Solid 1-compatible release. To use a newer adapter, migrate the app and its compiler/tooling to Solid 2 first; @palamedes/solid 1.18.0 and newer target Solid 2.

Exports

• Trans
• buildLocaleSwitchItems(options)
• TransProps
• BuildLocaleSwitchItemsOptions
• LocaleSwitchItem

The locale-switch helper and related types are re-exported from @palamedes/core/locale.

The macro subpath @palamedes/solid/macro exports compile-time macro components:

• Trans
• Plural
• Select
• SelectOrdinal

The transform rewrites Trans to @palamedes/solid/compiled. In v2, the package root and the /compiled alias resolve to the same parser-free compiled runtime. The alias remains useful for explicit macro targets; it is not a parser- enabled compatibility mode. Hand-written components that still depend on raw ICU parsing must migrate to compiled messages.

Runtime component

The package root exports the parser-free runtime Trans component. It reads the active i18n instance through the plain @palamedes/runtime getter and does not install signal dependencies for locale changes; changing locale requires a document navigation.

import { Trans } from "@palamedes/solid";
<Trans id="title" message="Welcome to Palamedes" />;

For source authoring, prefer macro imports from @palamedes/solid/macro.

Choice macros

Plural, Select, and SelectOrdinal are compile-time components. Import them from @palamedes/solid/macro; they are transformed into the parser-free runtime before the application runs. The package root does not export choice components or a runtime parser for hand-written choice trees.

Choice macros take branch text as props: plural categories (zero, one, two, few, many, other) and exact matches spelled _0, _1, … because a JSX attribute cannot start with =. Exact matches are normalized to ICU =N, mirroring the macro transform. other is required.

Plural and SelectOrdinal also accept offset, the ICU offset:N of the synthesized pattern, for "and N others" sentences where the number shown is smaller than the number counted:

import { Plural } from "@palamedes/solid/macro";

<Plural value={attendees()} offset={1} _0="nobody else" one="# other" other="# others" />;

• exact _N / =N keys match the raw value, before the offset is subtracted
• plural categories select on value - offset
• # inside a branch renders value - offset

offset must be a non-negative safe integer; anything else throws a RangeError rather than rendering a wrong count. Select has no numeric operand and takes no offset.

Framework Selection

Set the framework only so generated MDX uses Solid's component contract:

// vite.config.ts
palamedes({ framework: "solid" });

Macro t / plural calls still use the same framework-neutral, hook-free runtime getter. See docs/locale-strategies.md for document navigation and the unsupported root-key escape hatch.