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

@gigamusic/links

v4.2.0

Published

Editable Linktree-style link pages for gigamusic artist sites. Ships admin API handler factories and platform-detection helpers (the Drizzle schema + queries live in @gigamusic/db).

Readme

@gigamusic/links

Linktree-style per-release link pages for the gigamusic platform. Ships admin API handler factories, platform-detection helpers, and a small SVG LinkPlatformIcon component.

The link_pages / link_page_items Drizzle schema and the link-page queries live in @gigamusic/db — they're folded into the single createQueries(db) so a consumer builds one query object for every table. This package re-exports the link-page row types for convenience.

import {
  detectLinkPlatform,
  PLATFORM_LABELS,
  LinkPlatformIcon,
  type KnownLinkPlatform,
  type LinkPageWithItems,
} from "@gigamusic/links";

// Admin handler factories live on the /server subpath
import {
  createAdminLinkPagesHandlers,
  createAdminLinkPageByIdHandlers,
  createAdminLinkPageItemsHandlers,
} from "@gigamusic/links/server";

Reads and writes

All link-page DB access comes from @gigamusic/db's queries:

import { createQueries } from "@gigamusic/db";

const queries = createQueries(db); // one object, every table

// Public link-page UI — fetch and render whatever you want:
const page = await queries.getPublicLinkPageBySlug(slug);

The admin handler factories from @gigamusic/links/server take that same queries object:

const handlers = createAdminLinkPagesHandlers({ queries });

Release back-reference

linkPages.releaseId is a nullable FK to releases.id. Both tables and their relations live in @gigamusic/db/schema; linkPagesRelations already declares the linkPage.release direction. If you want a release.linkPages back-reference (for db.query.releases.findFirst({ with: { linkPages: true } })), compose it onto the base releasesRelations in your own schema file:

import { relations } from "drizzle-orm";
import { releases, linkPages } from "@gigamusic/db/schema";

export const releasesRelations = relations(releases, ({ many }) => ({
  // ...keep the existing many() relations from @gigamusic/db/schema if you need them...
  linkPages: many(linkPages),
}));

Because relations are TS modules, you compose them once and never re-apply patches on package upgrades.