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

@palamedes/solid

v0.3.0

Published

Solid runtime components and macro entry points for Palamedes

Downloads

108

Readme

@palamedes/solid

Use this package when your app wants Solid-native translation components such as Trans, Plural, Select, and SelectOrdinal, plus a small headless frontend helper layer for locale-aware UI.

Palamedes keeps the runtime model provider-free. Transformed code resolves the active i18n instance through getI18n() from @palamedes/runtime, so your Solid app only needs to register the active client or server instance before translated code runs.

This package is part of the verified SolidStart story in the example matrix. It shares the same catalog model, runtime semantics, and Vite plugin path as the React integrations while swapping only the thin JSX adapter layer.

Install

pnpm add @palamedes/core @palamedes/solid @palamedes/runtime
pnpm add -D @palamedes/vite-plugin @palamedes/cli @palamedes/config vite-plugin-solid

Example

import { Trans } from "@palamedes/solid/macro"

export function Footer() {
  return (
    <footer>
      <Trans>Powered by Palamedes</Trans>
    </footer>
  )
}

When the Palamedes transform runs, macro imports are rewritten to runtime imports from @palamedes/solid.

Headless Frontend Helpers

This package also exposes small Solid-native helpers that stay deliberately headless:

  • createClientLocaleEffect(localeAccessor, sync) from @palamedes/solid/client
  • buildLocaleSwitchItems({ locales, currentLocale, labels, testIdPrefix? })
  • LocaleSwitchItem<TLocale>

They do not own routing, styling, cookie policy, or server decisions. They only cover the stable frontend primitives that repeat across apps:

  • synchronizing the active client locale
  • building render-ready locale switch models for links, buttons, or forms
import { buildLocaleSwitchItems } from "@palamedes/solid"
import { createClientLocaleEffect } from "@palamedes/solid/client"

function LocaleToolbar(props: { locale: "en" | "de"; sync: (locale: "en" | "de") => void | Promise<void> }) {
  createClientLocaleEffect(() => props.locale, props.sync)

  const items = () =>
    buildLocaleSwitchItems({
      locales: ["en", "de"] as const,
      currentLocale: props.locale,
      labels: { en: "English", de: "Deutsch" },
    })

  return (
    <nav>
      {items().map((item) => (
        <button data-testid={item.testId}>{item.label}</button>
      ))}
    </nav>
  )
}

Related Docs