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

@fishka/angular

v0.1.5

Published

Shared Angular UI components

Readme

@fishka/angular

Shared Angular UI components for downstream apps. Not yet published — consumed locally via a file: dependency until the API settles across consumers.

Components

SplitterComponent (fi-splitter)

Two-pane resizable splitter with a draggable divider. Both panes are always shown (down to minimumSize) — pane1 absorbs the larger share (3:1) of any extra container space; pane2 keeps its dragged/default size as a baseline but can still grow some too. [collapseMode]="'pane1' | 'pane2' | 'none'" pins one pane at its minimum and gives the other the rest (e.g. "maximize pane2" / "minimize pane2" toggle buttons) without losing the dragged pane2 size — switching back to 'none' restores the normal split. Persistence is handled through the storage-agnostic SPLITTER_PERSISTENCE injection token so each app can back it with its own storage (localStorage, a settings service, ...).

<fi-splitter mode="split-vertically" [minimumSize]="[300, 200]" persistenceKey="my-app:split">
  <div pane1>...</div>
  <div pane2>...</div>
</fi-splitter>

minimumSize is [pane1MinPx, pane2MinPx]; defaultPane2Size (px) seeds pane2 the first time, before anything's persisted. To persist the dragged pane2 size, provide SPLITTER_PERSISTENCE (optional — without it, pane2 resets to defaultPane2Size on reload):

import { SPLITTER_PERSISTENCE, type SplitterPersistence } from '@fishka/angular';

const persistence: SplitterPersistence = {
  getNumber: key => {
    /* read a number, or undefined */
  },
  setNumber: (key, value) => {
    /* write a number */
  },
};

providers: [{ provide: SPLITTER_PERSISTENCE, useValue: persistence }];

Each pane defaults to overflow: auto (--splitter-pane1-overflow / --splitter-pane2-overflow). Override to hidden from the consumer if that pane's own content already manages its own internal scrolling (e.g. a fixed header + scrolling body) — otherwise the default stacks a second, usually- empty scrollbar on top of the content's own:

fi-splitter {
  --splitter-pane2-overflow: hidden;
}

Observer utilities

resizeObserver(element) / intersectionObserver(element, options?) — RxJS wrappers over ResizeObserver / IntersectionObserver.

Directives

  • [fiAutofocus] — focuses the host element after view init (native autofocus doesn't reliably work in Angular views).
  • [fiAutoFocusOnVisible] — focuses the host element the moment it transitions from invisible to visible (e.g. a panel that gets toggled open). visibilityThreshold input, default 0.5.
  • [fiNoDragClick] — emits (fiNoDragClick) only when mousedown/mouseup didn't move past a 2px threshold, so a drag gesture doesn't also fire a click.
  • [fiFillAvailableScreenHeight] — sizes the host element's max-height (and optionally height) to fill the viewport space remaining below it. Inputs: minHeight, bottomSpace, heightMode ('max-height' | 'max-height-and-height') — named heightMode rather than mode so it doesn't collide with other directives' own mode input (e.g. SplitterComponent's) on the same element.

All four use the fi selector prefix.

Development

  • npm run buildng-packagr build into dist/ (Angular Package Format).
  • npm test — Jest + jest-preset-angular (TestBed) component tests.
  • npm run lint, npm run format — eslint + prettier.
  • npm run typechecktsc --noEmit.

Published by the author separately (npm run release); consumers pin a version once it's out.