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

@ikenga/pkg-tasks

v0.8.3

Published

Tasks — List, Agenda, Triage over the production tasks schema. Multi-file iframe pkg; deterministic CSS vendoring build.

Readme

Tasks

Ikenga pkg — the Tasks workspace: List, Agenda (today's time-rail), and Triage (backlog health) over the production tasks schema. Multi-file iframe pkg, no build step. React 19 + htm + TanStack Query via esm.sh.

| | | |---|---| | Pkg id | com.ikenga.tasks | | Kind | embedded (UI iframe) | | Surface | /pkg/com.ikenga.tasks/ | | Data | Supabase tasks (+ task_comments, reserved) | | Build | none — dist/ is the whole app | | License | Apache-2.0 (per ADR-009) |

Layout

tasks/
├── manifest.json             # CSP allows esm.sh + *.supabase.co; tables: tasks, task_comments
├── package.json
├── README.md
├── tsconfig.dev.json         # dev-only checkJs — NEVER in the publish path
└── dist/                     # kernel convention — iframe sources live here
    ├── index.html            # mount point; imports app.js as ES module
    ├── app.js                # bridge + supabase + QueryClient → mounts <TasksView/>
    ├── tasks.css             # locked D-01 visuals (.tk-*/.ag-*/.tr-*/.ip-tab) + de-Tailwind utils
    ├── lib/
    │   ├── ui.js             # React, ReactDOM, htm, TanStack Query (esm.sh) + Icon/Button/cn
    │   ├── bridge.js         # @modelcontextprotocol/ext-apps wrapper
    │   ├── supabase.js       # lazy createClient
    │   ├── queries.js        # Task typedef, list columns, triage/detail/subtask/blocking queries
    │   ├── query-keys.js     # TanStack cache keys
    │   ├── shared.js         # groupTasks / buildAgenda / buildTriage + label helpers
    │   └── esm-sh.d.ts       # dev-only ambient decls for the esm.sh URL imports
    └── features/tasks/
        ├── tasks-view.js     # list + filter bar + groups + master/detail split + view switcher
        ├── task-row.js · task-detail-pane.js
        ├── view-tabs.js · agenda-view.js · triage-view.js

Why dist/? The shell's pkg-content server only serves files under <install_path>/dist/ for iframe routes (kernel convention). For a no-build pkg, your "build output" is your source — keep editing in dist/ directly. Forks work the same way.

Views

  • Tasks — grouped list (Overdue / Today / This week / Later / Auto-closed) with a filter bar (search, status, owner, category, show-auto-closed), collapsible group heads, and a master/detail split. The detail pane shows status, progress, tags, source chips, subtasks, the blocking task, and an activity timeline. Status changes write direct via Supabase (anon RLS grants UPDATE of status/completed_at).
  • Agenda — projects the loaded list onto today's hourly rail with a live now-line and an overdue-pulled-forward bucket.
  • Triage — four server-side health counts (overdue / stale>7d / unassigned / blocked) + sample rows + a backlog health grade.

View selection persists to localStorage (ikenga-tasks-view).

Create = dispatch, not insert

Anon RLS only grants UPDATE of status/completed_at on tasks — never INSERT. So New task does not write to Supabase directly. It dispatches a user turn into the shell's active Claude session (host.sendToActiveSession); the agent creates the task on its privileged path. The button is disabled in standalone preview (no host to dispatch to).

Fork in one step

cp -r ikenga-pkgs/packages/apps/tasks ~/my-tasks
# edit ~/my-tasks/manifest.json (change id), and any dist/features/*
ikenga add ~/my-tasks

No pnpm install, no tsc, no Vite. Forks are file edits + reload. (The tsconfig.dev.json + tsc -p tsconfig.dev.json flow is optional dev-time type-checking only — it is never part of publish.)

Standalone preview

file:///path/to/dist/index.html?url=https://xxx.supabase.co&anon_key=eyJ...

The pkg detects window.parent === window and falls back to query-string Supabase config. Useful for quick UI iteration without the shell.

CSP

manifest.json declares ui.csp overrides allowing:

  • script-src / style-src / font-src: https://esm.sh (React, htm, TanStack Query, Supabase, ext-apps SDK)
  • connect-src: https://*.supabase.co (PostgREST) + wss://*.supabase.co (Realtime)

See docs/pkg-patterns/01-ui-iframe.md.