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

@galaxy-io/filament-ui

v0.6.0

Published

Filament's web UI as a Galaxy module a host app mounts

Readme

Filament UI

Web UI for Filament, built with Vite + React + @galaxy-io/dls (the Galaxy Design Language System), talking to the ConnectRPC IngestionService.

Develop

just infra   # postgres + nats (Compose; CONTAINER_ENGINE=podman selects Podman)
just dev     # control-plane + server (:8080) + this UI (:5173)

Or run the pieces individually: just server, just control-plane, and just ui.

The dev server proxies /ingestion.v1.IngestionService, /metrics.v1.MetricsService and /auth.v1.AuthService to http://localhost:8080 (the port the justfile server recipe binds), so the app is same-origin in dev and prod alike. Set API_PROXY_TARGET to proxy to another local server, or VITE_API_URL to point the app at a remote Filament instance.

Build & embed

The server binary embeds this app. just binaries builds build/ and compiles cmd/server with -tags embedui. To build those pieces from the repository root:

just ui-build                                     # tsc + vite build → ui/build/
GOWORK=off go build -C cmd/server -tags embedui . # binary serving API + UI

Without -tags embedui, ui.Handler() serves a placeholder page and go build ./... needs no Node toolchain.

Module and host

The same src/ tree also builds @galaxy-io/filament-ui, a module a Galaxy host mounts under any path.

pnpm build:lib       # vite.lib.config.ts → dist/
pnpm check:package   # publint and the dist import scan
pnpm check:host      # type-check and build the fixture host against the package

src/host/ is standalone-only and never ships. src/module/ is the module's surface. The public API is the exports map in package.json.

| Subpath | What | |---|---| | ./paths | FilamentPath and createFilamentHref | | ./routes | one *RouteOptions per page, plus filamentLayoutRouteOptions and filamentNotFoundRouteOptions | | ./FilamentLayout | the shell, its sidebar and the URL-driven drawer and modals | | ./commands | useFilamentCommandItems({ base, transport }) for a host command palette | | ./pages/<Page> | ObservabilityPage, PipelinesPage, PipelinePage, PipelineCanvasPage, PipelineHistoryPage, PipelineSettingsPage, SourcesPage, SinksPage, NotFoundPage | | ./styles.css | every class the module renders, all prefixed filament- |

fixtures/host/ is the reference host and the executable copy of this contract. A host does the following.

  1. Install @galaxy-io/filament-ui from npm (pnpm add @galaxy-io/filament-ui) and every peer dependency in package.json. The host tsconfig uses "moduleResolution": "bundler", which every Vite host does. The host bundler replaces process.env.NODE_ENV, which Vite and webpack do.
  2. Import the CSS once at the app entry, in this order. @galaxy-io/dls/styles.css, tokens.css, fonts.css, then @galaxy-io/filament-ui/styles.css. Filament overrides the DLS at equal specificity, so its file comes last.
  3. Mount the providers above the router. GalaxyProvider owns the theme (Filament has no theme API), then QueryClientProvider and RouterProvider.
  4. Give Filament a transport. Filament reads the connect-query transport from context. A host whose global transport already reaches Filament's services needs nothing more. Otherwise nest a TransportProvider in the layout route's component. Create the transport once, at module scope, and pass the same instance to useFilamentCommandItems when the palette lives outside the mount, so the palette and the pages share cache entries. The module takes no baseUrl. Only the host adds auth interceptors or picks the wire format.
  5. Add the routes.
    • A layout route { ...filamentLayoutRouteOptions, component: Layout }.
    • One child per page, { ...pipelinesRouteOptions, component: PipelinesPage }, with the page imported in that file.
    • A $ splat { ...filamentNotFoundRouteOptions, component: NotFoundPage }.
    • Index redirects (/ → observability, pipelines/$id/ → canvas) as host files with absolute paths.
    • No defaultPendingComponent, defaultErrorComponent or defaultNotFoundComponent is needed. The route options carry Filament's own.
  6. Own the query client. Filament works with TanStack's defaults. Skip retries for NotFound, PermissionDenied, Unauthenticated, InvalidArgument and Unimplemented, or a missing pipeline retries for about 7s before its not-found page. A staleTime of 30s is recommended.
  7. Proxy /ingestion.v1.IngestionService, /metrics.v1.MetricsService and /auth.v1.AuthService to the Filament API at the transport's baseUrl. When another product also serves metrics.v1.MetricsService, put one product behind a prefix.
  8. Give the layout a box. FilamentLayout fills its parent, so the parent needs a definite height (a flex child with min-height: 0).

Releasing

@galaxy-io/filament-ui is published to npm by .github/workflows/ui-release.yaml. The filament-ui release-please component bumps package.json from conventional commits under ui/. Merging its release PR tags filament-ui-x.y.z, and the workflow then runs pnpm check and publishes through npm trusted publishing, with no token.

Codegen

TypeScript clients are generated from the protobuf definitions under ../api/ into src/gen/ (checked in):

cd ui && pnpm codegen   # buf generate

Re-run after changing the protos. src/host/routeTree.gen.ts is generated by the TanStack Router plugin during pnpm dev / pnpm build and is also checked in.

Conventions

Everything in src/ follows the filament-ui skill at .agents/skills/filament-ui (DLS components by subpath, Linaria with DLS tokens, no margins, no barrels, feature-prefixed files, URL-backed view state, the query layer in src/api/queries). Read its SKILL.md before adding a screen, and update its references when a convention changes.