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

@document-explorer/angular

v0.1.1

Published

Clean, configuration-driven document explorer for Angular. Bring your own data.

Readme

@document-explorer/angular

Turn any document data into a clean, navigable explorer — in Angular.

npm install @document-explorer/angular
import { DocumentExplorerComponent } from '@document-explorer/angular';

@Component({
  standalone: true,
  imports: [DocumentExplorerComponent],
  template: `<doc-explorer [data]="documents" />`,
})
export class MyComponent {}

Add the stylesheet once, in angular.json or a global stylesheet:

"styles": ["@document-explorer/angular/styles.css", "src/styles.css"]

Bring your own data

<doc-explorer
  [data]="apiResponse"
  [mapper]="mapper"
  title="Documents"
  [search]="{ scope: 'global', searchableFields: ['metadata.owner'] }"
  [selection]="{ mode: 'multiple', folders: false }"
  [actions]="{ view: true, download: true }"
  (documentOpen)="open($event)"
  (selectionChange)="selected = $event"
/>

The component is standalone, OnPush, and signal-driven throughout — it works zoneless.

Inputs

Identical in name and meaning to the React package: data, mapper, title, rootLabel, view, views, defaultView, search, sort, columns, columnAlign, resizableColumns, columnWidths, selection, actions, interaction, loading, error, locale.

Outputs

folderOpen, documentOpen, selectionChange, searchChange, sortChange, viewChange, documentView, documentDownload, columnResize ({ key, width, widths }), and action ({ actionId, item }) for custom actions.

Custom rendering

Angular's equivalent of React's renderers is ng-template slots:

<doc-explorer [data]="documents">
  <ng-template #deFile let-item>
    <my-file-card [file]="item" />
  </ng-template>
  <ng-template #deEmpty>Nothing here yet.</ng-template>
</doc-explorer>

Available slots: #deFile, #deFolder, #deEmpty, #deToolbar.

Per-column cells

For one column rather than a whole row — an avatar beside an owner, a status pill — use the deColumn directive, the Angular equivalent of React's ColumnDef.render:

import { DeColumnTemplateDirective } from '@document-explorer/angular';
<doc-explorer [data]="documents" [columns]="columns">
  <ng-template deColumn="metadata.owner" let-item let-value="value">
    <span class="de-avatar">{{ initials(value) }}</span>
    <span class="de-avatar-label">{{ value }}</span>
  </ng-template>
</doc-explorer>

The context carries the whole item and value, the column's formatted text.

Avatars

Showing a person is built in. Angular cannot return markup from a plain object the way React's render can, so avatarColumn returns the column and the options for <de-avatar-cell>:

readonly owner = avatarColumn({ key: 'metadata.owner', display: 'avatar' });
readonly columns = ['name', this.owner.column, 'size'];
<doc-explorer [data]="documents" [columns]="columns">
  <ng-template deColumn="metadata.owner" let-item>
    <de-avatar-cell [item]="item" columnKey="metadata.owner" [options]="owner.options" />
  </ng-template>
</doc-explorer>

display is 'both' (default), 'avatar' (name on hover and to screen readers) or 'name', and image is independent of it — pair display: 'avatar' with image for a photo on its own. image takes a dot path or function and falls back to initials on load failure. Colours come from six theme tokens, assigned stably per name — identical to the React package, because both call resolveAvatar() in core.

Badges

readonly status = badgeColumn({ key: 'metadata.status' });
<ng-template deColumn="metadata.status" let-item>
  <de-badge-cell [item]="item" columnKey="metadata.status" [options]="status.options" />
</ng-template>

Conventional statuses get a tone with no configuration — approved green, pending amber, rejected red. tones, format and variant override it, and the colours are --de-tone-* tokens.

Resizable columns

<doc-explorer
  [resizableColumns]="true"
  [columnWidths]="saved"
  (columnResize)="persist($event.widths)"
/>

width is the starting track, maxWidth caps how far it can be dragged, minWidth floors it, and resizable: false pins a column entirely.

Drag a handle to resize, double-click to reset. The handle is a focusable role="separator", so / resize and Enter resets — resizing is not drag-only. A flexible column keeps a floor so widening a neighbour can never hide the file names, and once the columns stop fitting the list scrolls horizontally with the rows widening to match.

columnResize fires once on release, not per pointer move.

Parity with React

Both packages drive the same engine — @document-explorer/core — including the keyboard contract. The test suite here is a deliberate mirror of the React one: the same assertions, in the same order, against the same fixture. A divergence between them is a bug in core, not in a renderer.

Theming and accessibility work exactly as documented in the React package README.

License

MIT