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

@linkforty/ui

v3.0.3

Published

React UI components for deeplink management

Readme

@linkforty/ui

React components for deeplink management interfaces

The link table, link detail view, create/edit modals, app configuration form and toast system that the LinkForty dashboard is built from, published so you can build your own interface on top of @linkforty/core without starting from a blank page.

npm version License: MIT

What's in the box

| Export | What it is | |---|---| | LinkTable | Table of links with sortable columns, per-row inspect and analytics actions, optional row selection | | LinkDetail | Read-only view of one link: short URL with copy and QR code, campaign parameters, template, project, deep link info, fallback paths, targeting rules, Launchpad funnel | | CreateLinkModal | Form for creating a link from a template, with project, domain, deep-linking, UTM, targeting and expiry fields | | EditLinkModal | The same form for an existing link | | OrganizationAppConfig | Form for a workspace's app configuration: URI scheme, iOS team and bundle id, Android package and SHA-256 fingerprints, Universal Link and App Link domains, default store and fallback URLs | | ToastProvider, useToast, ToastItem | Toast notifications, rendered through a portal on document.body | | Types | Link, CreateLinkRequest, UpdateLinkRequest, LinkTemplate, Project, CustomDomainOption, AppConfig, Organization, UTMParameters, TargetingRules, and more — see src/types | | Constants | PROJECT_COLORS, DEFAULT_PROJECT_COLOR, projectPillClasses(), DEFAULT_SHORTLINK_DOMAIN |

The components are presentational: they take data and callbacks, and never call an API themselves. Fetching, mutations and routing stay in your app.

Installation

npm install @linkforty/ui react react-dom

React 18 is a peer dependency.

Quick start

1. Import the styles and wrap your app in ToastProvider

import { ToastProvider } from '@linkforty/ui';
import '@linkforty/ui/styles';

function App() {
  return (
    <ToastProvider>
      {/* your app */}
    </ToastProvider>
  );
}

2. Use the components

import { LinkTable, CreateLinkModal, useToast } from '@linkforty/ui';
import type { CreateLinkRequest } from '@linkforty/ui';
import { useState } from 'react';

function LinksPage({ links, templates, projects, domains, defaultDomain }) {
  const [showCreate, setShowCreate] = useState(false);
  const { success, error } = useToast();

  const handleCreate = async (data: CreateLinkRequest) => {
    try {
      await api.createLink(data);
      success('Link created');
      setShowCreate(false);
    } catch (e) {
      error('Failed to create link');
    }
  };

  return (
    <>
      <button onClick={() => setShowCreate(true)}>New link</button>
      <LinkTable
        links={links}
        defaultDomain={defaultDomain}
        onInspect={(link) => navigate(`/links/${link.id}`)}
        onViewAnalytics={(link) => navigate(`/analytics?link=${link.id}`)}
      />
      <CreateLinkModal
        isOpen={showCreate}
        onClose={() => setShowCreate(false)}
        onSubmit={handleCreate}
        templates={templates}
        projects={projects}
        domains={domains}
        defaultDomain={defaultDomain}
      />
    </>
  );
}

Components

LinkTable

| Prop | Type | Required | Description | |---|---|---|---| | links | Link[] | Yes | Links to display | | defaultDomain | string | No | Host that links without an assigned domain are served on, e.g. go.example.com | | customDomain | string | No | Workspace-level custom domain, used when a link has no domain of its own | | onInspect | (link: Link) => void | No | Row action: open the link's detail view | | onViewAnalytics | (link: Link) => void | No | Row action: open the link's analytics | | selectedIds | Set<string> | No | Controlled row selection | | onSelectionChange | (ids: Set<string>) => void | No | Called when the selection changes; selection UI is shown only when both selection props are given |

The short URL shown per row is https://<host>/<short_code> (with the template slug in between when the link has one), where the host is the link's own domain, then customDomain, then defaultDomain, then DEFAULT_SHORTLINK_DOMAIN.

LinkDetail

| Prop | Type | Required | Description | |---|---|---|---| | link | DiscoveredLink | Yes | The link (Link plus optional creator_email and template_name) | | baseShortUrl | string | Yes | Short URL origin for links without an assigned domain, e.g. https://go.example.com | | apiBaseUrl | string | Yes | Origin of the API that serves GET /api/links/:id/qr, used by the QR code section | | onNavigate | (path: string) => void | No | Called for in-app navigation (template, project) so the host's router can handle it | | renderUtmValue | (param, value) => ReactNode | No | Overlay friendly names on UTM values; raw values are shown when omitted | | fetchLaunchpadStats | (linkId, days) => Promise<LaunchpadLinkStats> | No | Loads the Launchpad funnel for a period; the funnel card is hidden when omitted |

<LinkDetail
  link={link}
  baseShortUrl="https://go.example.com"
  apiBaseUrl="https://api.example.com"
  onNavigate={(path) => navigate(path)}
  fetchLaunchpadStats={(id, days) => api.getLaunchpadStats(id, days)}
/>

CreateLinkModal

| Prop | Type | Required | Description | |---|---|---|---| | isOpen | boolean | Yes | Controlled open state | | onClose | () => void | Yes | | | onSubmit | (data: CreateLinkRequest) => Promise<void> | Yes | Receives the validated payload | | templates | LinkTemplate[] | Yes | Templates to choose from; the default template's settings prefill the form | | projects | Project[] | No | Shows a project select when non-empty; projectId is null when none is chosen | | domains | CustomDomainOption[] | No | Verified custom domains; shows a domain select when there is a real choice; domainId is null for the workspace default | | defaultDomain | string | No | Host shown for the workspace default option | | orgAppConfig | AppConfig | No | Prefills deep-linking fields from the workspace's app configuration | | isLoading | boolean | No | Disables the submit button |

EditLinkModal

Same props as CreateLinkModal minus orgAppConfig, plus:

| Prop | Type | Required | Description | |---|---|---|---| | link | Link \| null | Yes | The link being edited; null renders nothing | | onSubmit | (data: UpdateLinkRequest) => Promise<void> | Yes | expiresAt: null clears an expiration date | | templates | LinkTemplate[] | No | Used to show the template's name |

OrganizationAppConfig

| Prop | Type | Required | Description | |---|---|---|---| | appConfig | AppConfig | No | Current values | | onSave | (appConfig: AppConfig) => Promise<void> | Yes | Receives the validated configuration | | isLoading | boolean | No | Disables the save button | | bare | boolean | No | Render without the card wrapper, for embedding in your own panel |

<OrganizationAppConfig
  appConfig={organization.settings?.appConfig}
  onSave={(appConfig) => api.updateOrganization({ settings: { appConfig } })}
/>

Toasts

const { success, error, warning, info, showToast } = useToast();

success('Saved');
error('Something went wrong', 8000);
showToast('Custom', 'info', 3000);

Styling

The components are styled with Tailwind utility classes compiled into the package stylesheet:

import '@linkforty/ui/styles';

The stylesheet includes Tailwind's base reset, so load it once, early.

Surfaces (panels, cards, table chrome, inputs) read these custom properties when your page defines them, and fall back to a light palette — dark under prefers-color-scheme: dark — when it does not:

:root {
  --color-popover-bg: #ffffff;      /* panels and cards */
  --color-popover-border: #e5e7eb;
  --color-input-bg: #ffffff;        /* inputs and recessed areas */
  --color-input-border: #d1d5db;
  --color-table-bg: #ffffff;
  --color-table-header-bg: #f9fafb;
}

Beyond that, override the utility classes in your own stylesheet or fork the components; there is no wider theme API.

Types

Everything under src/types is exported:

import type {
  Link,
  CreateLinkRequest,
  UpdateLinkRequest,
  LinkTemplate,
  Project,
  CustomDomainOption,
  AppConfig,
  Organization,
  UTMParameters,
  TargetingRules,
  Toast,
  ToastType,
} from '@linkforty/ui';

Field names follow the API they were built against: snake_case on records read from the API (Link, LinkTemplate), camelCase on request payloads (CreateLinkRequest, AppConfig).

Form validation

The modals validate with zod and show errors inline: URLs must be well-formed, custom codes allow letters, numbers, hyphens and underscores, and text fields carry maximum lengths.

Development

npm install
npm run storybook   # component explorer on port 6006
npm run build       # ESM + CJS + type declarations into dist/

Browser support

Current versions of Chrome, Firefox, Safari and Edge.

Changelog

See CHANGELOG.md. 3.0.0 is a breaking release; read its Removed and Changed sections before upgrading from 2.x.

License

MIT — see LICENSE.

Related projects