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

@pleta/dashboard

v0.2.0

Published

Angular dashboard grid with draggable and resizable widgets.

Readme

Pleta Dashboard

Independent @pleta/dashboard library. Depends on @pleta/ui and @pleta/icons. Workspace scripts build icons → ui → dashboard. No drag-and-drop dependency, network requests or storage are added.

import { signal } from '@angular/core';
import { PleDashboardGrid, PleDashboardItem, PleDashboardLayoutItem } from '@pleta/dashboard';

readonly layout = signal<readonly PleDashboardLayoutItem[]>([
  { id: 'sales', label: 'Sales', x: 0, y: 0, width: 3, height: 3,
    minWidth: 2, minHeight: 2, maxWidth: 4, maxHeight: 5 },
  { id: 'notes', label: 'Notes', x: 3, y: 0, width: 3, height: 3 },
]);

Add PleDashboardGrid and PleDashboardItem to component imports:

<ple-dashboard-grid
  [(layout)]="layout"
  [columns]="6"
  [rowHeight]="80"
  (layoutChangeEnd)="save($event.layout)"
>
  <ng-template pleDashboardItem="sales" let-item let-index="index">
    <p>{{ item.label }}: {{ item.width }} × {{ item.height }}</p>
  </ng-template>
  <ng-template pleDashboardItem="notes"
    ><label>Note <input /></label
  ></ng-template>
</ple-dashboard-grid>

PleDashboardItem is a template directive keyed by layout ID, not a DOM wrapper. Missing templates fall back to label/id. Optional itemTemplate applies to all cells and takes precedence over projection. Both receive PleDashboardItemContext ($implicit: item, index). Use one projected template per item ID.

Public API

PleDashboardLayoutItem has a unique nonempty string id, optional label, integer x/y (zero-based), positive integer width/height in grid units. Optional minWidth/maxWidth/minHeight/maxHeight constrain resizing. Minimum defaults to 1, maximum to columns/maxRows. Optional movable/resizable default to true; false disables the action and corresponding numeric editor fields.

| Binding | Default / purpose | | --------------- | ------------------------------------------------------------ | | [(layout)] | Empty array; immutable controlled layout | | columns | 12; fixed positive column count | | rowHeight | 80px, minimum 44px | | gap | 12px; finite nonnegative gap | | minColumnWidth | 64px, minimum 44px; horizontal scrolling on narrow screens | | maxRows | 100; positive maximum row count | | readonly | false; hides editing controls | | label | Дашборд; accessible name of scroll region | | itemTemplate | Optional common TemplateRef | | layoutChangeEnd | { layout, previousLayout, itemId, action }; move/resize/edit |

Interaction

Move handle and lower-right resize handle use Pointer Events/capture for mouse, touch and pen. Preview is local: layoutChange and layoutChangeEnd emit once on completion, only when geometry actually changed. Application code owns persistence.

Keyboard on a handle: arrows preview one-unit steps; Enter/Space confirms (or starts a transaction); Escape cancels. Tab/blur cancels keyboard previews. Pointer cancel/lost capture cancels dragging. External layout, geometry or readonly changes cancel pending interactions instead of overwriting newer state.

Configure opens numeric X/Y/width/height fields: a pointer-only alternative to dragging, also accessible by keyboard. Apply commits; Cancel/Escape discard edits. Focus returns to the Configure button.

Items snap to cells, cannot overlap or leave bounds. Blocked preview shows the original position; dropping it cancels. Invalid incoming layouts show an error rather than silently rearranging data. Keep IDs stable to preserve embedded form and component state. Changing the template itself can recreate its view.

Fixed columns with horizontal scrolling; no responsive auto-reflow, packing, collision pushing, arbitrary-edge resizing, cross-grid transfer, virtualization, automatic scrolling during dragging, undo history or saved-layout service yet.

Storybook /dashboard: both template APIs, readonly mode, fixed widgets, preview/commit and content-state preservation.

Theme documentation

Storybook /theme has an @pleta/dashboard tab with the grid's color tokens, defaults and a scoped CSS example. Dashboard inherits the shared UI palette: --ple-surface, --ple-surface-subtle, --ple-text, --ple-text-muted, --ple-border, --ple-border-subtle, --ple-focus and --ple-error. There are no separate --ple-dashboard-* tokens. Buttons and editor fields use UI tokens; application-owned widget content uses the consumer's styles.

Optionally import @pleta/ui/theme.css in global CSS. Override the shared palette on html[data-theme='dark'] (and set color-scheme: dark) to apply your own dark theme. UIKit supplies light defaults and does not switch themes. Grid geometry is configured through component inputs, not color tokens.

License

Pleta uses the proprietary Pleta Free Application Use License. Personal and commercial application use is free, including paid products, client projects, and SaaS. Application builds and distribution with bundled Pleta code are permitted. Modifying or forking the library itself, extracting its implementation, and republishing it as a standalone package or reusable library are not permitted except as stated in the license. Include the license in your application's legal notices. Third-party materials retain their own licenses. See the LICENSE file shipped with each package for the full terms.