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

@elah/timeline

v0.4.1

Published

React timeline UI for the Elah video engine — tracks, clips, ruler, playhead, drag and trim gestures

Downloads

905

Readme

@elah/timeline

React timeline UI for the Elah video engine. Renders tracks, clips, ruler, and playhead — and wires up drag, trim, scrub, zoom, and drop gestures into @elah/core engine calls.

A consumer of @elah/core. Owns no project state — all state lives in the core stores.

npm gzip size license


Install

npm install @elah/timeline @elah/core @elah/react lucide-react

Peer dependencies: react, react-dom >= 18, lucide-react >= 0.400.0 (used directly by TrackRow/ClipBlock for clip icons — install it even if nothing else in your app needs it). Engine/playback context (EditorContext, useTimelineEngine) comes from @elah/react, a runtime dependency pulled in automatically.

Bundle size: ~12 KiB gzipped (61 KiB raw, tsc ESM output). UI layer only — project state lives in @elah/core.


Components

| Component | Description | |---|---| | Timeline | Root surface — tracks, ruler, playhead, gesture wiring | | Ruler | Time ruler — click or drag to scrub | | TrackRow | Single track lane with clip blocks and drop target | | ClipBlock | Individual clip — drag to move, edge-drag to trim | | Playhead | Playhead needle driven by usePlaybackStore |


Quick start

Timeline reads the engine and playback clock from React context — it has no engine prop. Wrap it in an EditorContext.Provider from @elah/react (or use EditorProvider from @elah/editor, which does this for you):

import { Timeline } from '@elah/timeline'
import { TimelineEngine, PlaybackEngine } from '@elah/core'
import { EditorContext } from '@elah/react'

const engine = new TimelineEngine({ fps: 30, stage: { width: 1920, height: 1080 } })
const playback = new PlaybackEngine({ fps: 30, getTotalFrames: () => engine.getTotalFrames() })

function App() {
  return (
    <EditorContext.Provider value={{ engine, playback }}>
      <Timeline fps={30} style={{ height: 300 }} />
    </EditorContext.Provider>
  )
}

EditorContext supplies the engine pair only — it does not wire engine events into the Zustand mirrors the way <EditorProvider> does, so a bare EditorContext.Provider like this needs its own engine.on('change', ...)tracksStore.sync(...) wiring (see @elah/editor's EditorProvider source) or the UI won't update. Prefer EditorProvider unless you specifically need a custom store-sync strategy.

The stores Timeline reads (tracksStore, playbackStore, selectionStore, ...) are module-level singletons in @elah/core — only one engine's state can be mirrored into them at a time. Rendering two <Timeline> trees backed by two different engines on the same page will have them fight over the same store; see @elah/core's README for details.


Styling

Import the compiled stylesheet once (plain CSS — Tailwind is not required in your app, and no utility classes leak into your global scope):

import '@elah/timeline/styles.css'
import '@elah/editor/styles/tokens.css' // --elah-* defaults (standalone use)

Colors are driven by --elah-* CSS variables. Re-theme by overriding them in your own .elah-root scope — see design-tokens.md.

Per-instance overrides — classNames

For one-off styling on a specific timeline, pass classNames — a per-slot map of Tailwind classes. Whatever you pass wins over the built-in classes (tailwind-merge).

<Timeline
  classNames={{
    root:       'rounded-xl',
    ruler:      'bg-zinc-900',
    rulerTick:  'bg-zinc-700',
    rulerLabel: 'text-zinc-500',
    trackLabel: 'bg-zinc-900',
    lane:       'bg-zinc-950',
    clip:       'rounded-lg shadow-lg',   // shape/shadow (all clip types)
    // per-type clip color — body + accent are separate slots:
    clipVideo:       'from-sky-400 to-sky-600',  // body (gradient or solid bg-*)
    clipVideoAccent: 'text-sky-300',              // stripe + selection + track bar
    playhead:   'text-rose-500',
  }}
/>

Conventions:

  • Backgrounds (ruler, lane, label, clip bodies) take bg-* or gradient stops (from-… to-…; the gradient direction is added for you).
  • Accents (playhead, clip stripe/selection, track-label bar) paint from currentColor, so recolor them with a text-* class.

Slots: root, ruler, rulerTick, rulerLabel, track, trackLabel, lane, clip, clip{Video,Audio,Text,Image}, clip{Video,Audio,Text,Image}Accent, playhead. See the TimelineClassNames type for the full list.


Hooks

import { useTracks, usePlayback, useSelection } from '@elah/timeline'

const tracks = useTracks(s => s.tracks)
const { currentFrame, isPlaying } = usePlayback(s => s)
const { selectedClipIds } = useSelection(s => s)

Drag & drop

Attach media drop handlers to any track lane element. useTimelineDrop(trackId, lane) takes the track id and the lane DOM node positionally, and reads the engine from the EditorContext (so it must run inside the provider). It wires the handlers as a side-effect and returns nothing:

import { useRef } from 'react'
import { useTimelineDrop } from '@elah/timeline'

function Lane({ trackId }: { trackId: string }) {
  const laneRef = useRef<HTMLDivElement>(null)
  useTimelineDrop(trackId, laneRef.current)
  return <div ref={laneRef} />
}

Dragging a media asset from the library onto the lane resolves drop position to startFrame (respects zoom and snap).


Links