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

@linto-ai/transcript-ui-core

v0.9.18

Published

State layer and UI shell for @linto-ai/transcript-ui — core, stores, format adapters, and the TranscriptUI component

Readme

@linto-ai/transcript-ui-core

Part of @linto-ai/transcript-ui — see there for the full package list and quick start.

The main piece of @linto-ai/transcript-ui — a Vue component for displaying and interacting with a transcript. It bundles the document state (createCore), the editor layout (Layout), and adapters that convert LinTO Studio API or WhisperX transcripts into a format it understands.

Usage

<script setup lang="ts">
import { TranscriptUI, mapApiDocument } from "@linto-ai/transcript-ui-core"
</script>

<template>
  <TranscriptUI ref="editor" locale="en" />
</template>

TranscriptUI handles everything on its own: it creates the document state, shows a loading spinner, then the transcript once a document is loaded.

Building your own layout instead

If you don't want TranscriptUI's default screen, createCore/provideCore and Layout are the two pieces it uses internally — use them directly to build your own.

Turning a transcript into something this package understands

  • mapApiDocument — for a transcript from the LinTO Studio API.
  • mapWhisperXDocument — for raw WhisperX output.

Data model

A document (EditorDocument) has a flat list of speakers and one or more channels.

  • Channel — one audio/recording track (e.g. one microphone, one room). Has one or more Translations.
  • Translation — one language track within a channel: the source language, or an auto-translated version. Exactly one per channel is the source (isSource: true). Holds an ordered list of Turns and, for the source, the AudioSource to play.
  • Turn — one speech segment: a speakerId (pointing into the document's shared speakers map, or null if unassigned), a language, and either text (a plain string, e.g. from a live text-only source) or words (per-word timing, e.g. from ASR) — never both.
  • Word — one word inside a turn: its text, character offsets into the turn's plain text, and optional start/end time and confidence.
  • Speaker — id, display name, color. Stored once per document, referenced by id from every Turn — renaming a speaker updates every turn that points at them for free.
EditorDocument
├── speakers: Map<id, Speaker>
└── channels: Channel[]
    └── translations: Translation[]   (one is the source; others are translations)
        └── turns: Turn[]
            ├── speakerId → looked up in EditorDocument.speakers
            └── text (string) OR words (Word[]) — never both