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

@ga-ut/ce

v0.1.1

Published

Custom Elements runtime with signals, routing, and dependency-free app bundling

Downloads

191

Readme

@ga-ut/ce

Custom Elements runtime with function components, signals, scoped rendering, optional routing, and a dependency-free app bundler.

Install

npm install @ga-ut/ce
pnpm add @ga-ut/ce
yarn add @ga-ut/ce
bun add @ga-ut/ce

You can also run the CLI without installing it globally:

npx --package @ga-ut/ce ce-cli build --entry ./src/main.js --out ./dist
pnpm dlx @ga-ut/ce ce-cli build --entry ./src/main.js --out ./dist
yarn dlx @ga-ut/ce ce-cli build --entry ./src/main.js --out ./dist
bunx -p @ga-ut/ce ce-cli build --entry ./src/main.js --out ./dist

Runtime Usage

import { config, define, derived, html, signal } from "@ga-ut/ce/web";
import styles from "./ce.css?inline";

config({
  globalStyles: [styles],
});

define(function ProductBadge({ props }) {
  const selected = signal(false);
  const label = derived(() => selected() ? "Selected" : props.label);

  return html`
    <button onclick=${() => selected.update((value) => !value)}>
      ${label}
    </button>
  `;
}, {
  props: {
    label: String,
  },
});

App Build

Create a browser entry:

import { config, define, html } from "@ga-ut/ce/web";
import styles from "ce:styles";

const homePageTag = define(function HomePage() {
  return html`<main class="p-4"><h1>CE App</h1></main>`;
});

config({
  globalStyles: [styles],
  entryPoint: "ce-app",
  routes: [{ path: "/", tag: homePageTag }],
});

Generate index.html and app.js:

ce-cli build --entry ./src/main.js --out ./dist --css ./src/ce.css

The build command bundles static relative imports, @ga-ut/ce/web, and optional ce:styles CSS into a browser ESM file. Use --root to choose the generated root custom element tag and --title to set the document title.

Browser Bundle

Use bundle when you only want the browser ESM file:

ce-cli bundle --entry ./src/main.js --out ./dist/app.js --css ./src/ce.css

Use the virtual ce:styles import to inject the CSS file as globalStyles:

import { config } from "@ga-ut/ce/web";
import styles from "ce:styles";
import { routes } from "./routes.js";

config({
  globalStyles: [styles],
  entryPoint: "ce-app",
  routes,
});

The CLI intentionally does not transpile TypeScript, process JSX, resolve arbitrary node_modules, minify, or support dynamic import(). Existing app bundlers can still consume CE normally through @ga-ut/ce/web; the CLI is a small CE-focused path for projects that do not want another bundler.

Entry Points

  • @ga-ut/ce
  • @ga-ut/ce/core
  • @ga-ut/ce/web
  • ce-cli package binary

Documentation

  • Public API: docs/api.md
  • Release checklist: docs/release.md