SolidStart i18n · TypeScript
Palamedes pairs a Vite build integration with dedicated Solid authoring and runtime packages. Solid-native components and hook-free lookups share one catalog model across request-local SSR and hydration.
Solid macros, formatters, and locale primitives.
Vite Environment API, Nitro v3, and Vite 8.
Isomorphic routes with one locale per document.
Cookie, route, subdomain, and top-level domain.
@palamedes/solidv1.17.32.4K downloads / month01 — The framework problem
A Solid application should not need provider patterns designed for another renderer. Locale state must still agree across the server response, hydration, and a later document navigation.
02 — The Palamedes model
The native core and Vite adapter stay common across hosts. @palamedes/solid owns rich-message rendering while the active locale remains framework-neutral document bootstrap state.
Use t, plural, and the Solid Trans macro beside JSX. Rich messages compile for Solid instead of passing through a React adapter.
Translations read one active instance through a plain getter. Locale controls navigate the document so Solid state and external caches restart together.
The same extraction, ICU diagnostics, PO or FCL storage, audits, and semantic merging apply before the renderer sees a message.
03 — In TypeScript
vite.config.ts + routes/[locale].tsx
// vite.config.ts
import { nitro } from "nitro/vite"
import { defineConfig } from "vite"
import { solidStart } from "@solidjs/start/config"
import { palamedes } from "@palamedes/vite-plugin"
export default defineConfig({
plugins: [
palamedes({ framework: "solid" }),
solidStart(),
nitro(),
],
})
// routes/[locale].tsx
import { Trans } from "@palamedes/solid/macro"
export default function LocalePage() {
return <h1><Trans>Welcome to Palamedes</Trans></h1>
}The route example activates a request-local server instance for SSR, initializes the browser locale once, and uses normal links for locale navigation.
04 — Locale strategy
SolidStart's file routes and request APIs decide where the locale lives. Each checked Palamedes example keeps the Solid authoring and runtime surface unchanged while swapping the detection and switching policy.
One URL for all locales. Best for apps behind login where SEO is irrelevant and switching should be instant.
/de/checkout-style paths. The SEO-friendly default for public content with indexable localized pages.
de.example.com. Clean separation per market, works well with regional CDNs and analytics splits.
example.de vs example.com. Maximum market trust; Palamedes maps each domain to its locale.
◌ local / CIsource →
05 — Proof and boundaries
The SolidStart matrix uses @palamedes/solid directly. Browser checks exercise the rendered page, the locale switch, and localized server work for every URL strategy.
No React provider or React translation component.
The selected catalog renders before hydration.
A new document renders consistently in the selected locale.
Translated server output is exercised in CI.
06 — Questions
The short version of the decisions that usually block an implementation.
07 — Keep exploring