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

@reportwright/angular

v1.0.0

Published

ReportWright viewer and designer custom elements for Angular (CUSTOM_ELEMENTS_SCHEMA).

Readme

@reportwright/angular

<reportwright-viewer> and <reportwright-designer> custom elements: the ReportWright report viewer and drag-and-drop designer in Angular.

npm license Socket

Live demo: mrarun005.github.io/reportwright-demo (Embed it shows the wrapper code; the designer playground is the designer these elements mount).

Custom elements need no Angular compiler step, so they work with any Angular version.

Install

npm i @reportwright/angular @reportwright/viewer @reportwright/fonts

Serve the fonts as static assets, e.g. in angular.json under assets: { "glob": "**/*", "input": "node_modules/@reportwright/fonts/public", "output": "pw" }, then pass fontsUrl: '/pw/fonts/'.

Quick start (30 seconds)

// main.ts
import { defineReportWrightElements } from '@reportwright/angular';
defineReportWrightElements();

// orders.component.ts
import { Component, CUSTOM_ELEMENTS_SCHEMA } from '@angular/core';
import definition from './orders.pw.json';   // the report from @reportwright/engine's README examples (resolveJsonModule)

@Component({
  selector: 'app-orders',
  standalone: true,
  schemas: [CUSTOM_ELEMENTS_SCHEMA],
  template: `<reportwright-viewer [options]="options" style="display:block;height:720px"></reportwright-viewer>`,
})
export class OrdersComponent {
  options = {
    definition,
    data: { orders: { rows: [{ customer: 'Asha Rao', amount: 1200.5 }, { customer: 'Ben Ode', amount: 80 }] } },
    fontsUrl: '/pw/fonts/',
  };
}

The elements were verified against this version with Vite 7 in Chromium (created from plain JavaScript, as Angular does).

Examples

Get the handle, re-run with parameters, export:

@Component({
  selector: 'app-orders',
  standalone: true,
  schemas: [CUSTOM_ELEMENTS_SCHEMA],
  template: `
    <button (click)="viewer?.setParameters({ minAmount: 100 })">Over 100</button>
    <button (click)="excel()">Excel</button>
    <reportwright-viewer [options]="options" (pw-ready)="viewer = $event.detail"></reportwright-viewer>`,
})
export class OrdersComponent {
  viewer?: ViewerHandle;   // import type { ViewerHandle } from '@reportwright/angular'
  options = { definition, data: { orders }, fontsUrl: '/pw/fonts/' };
  async excel() { open(URL.createObjectURL(await this.viewer!.export('xlsx'))); }
}

Edit a report and save it (without onSave in the options, the designer fires pw-save):

<reportwright-designer [options]="{ definition: def, fontsUrl: '/pw/fonts/' }" (pw-save)="save($event.detail)"></reportwright-designer>

With a self-hosted ReportWright server:

<reportwright-viewer [options]="{ server: 'https://reports.example.com', report: 'invoice', params: { id: id } }"></reportwright-viewer>
<reportwright-designer [options]="{ server: server, definition: def }" (pw-save)="save($event.detail)"></reportwright-designer>

A runnable app is in the repository's examples/angular.

Properties, attributes and events

| | Element | Meaning | |---|---|---| | options property | both | the options of mountViewer / mountDesigner (full table in @reportwright/viewer) | | server, report, height, lang attributes | both | the same options as attributes | | pw-ready | both | detail: the ViewerHandle / DesignerHandle | | pw-error | both | detail: the error when the viewer's code did not load | | pw-save | designer | detail: the definition (only when options has no onSave) |

Exports: defineReportWrightElements(), and the types ReportWrightViewerElement, ReportWrightDesignerElement, ReportWrightReadyEvent, ViewerHandle, DesignerHandle.

Support

Angular 14 or later (peer @angular/core >= 14). Browsers and limits are the viewer's: see @reportwright/viewer.

No server needed: pass definition, data (JSON by data source name) and fontsUrl (a copy of @reportwright/fonts/public/fonts). server (the self-hosted ReportWright server) is optional: see what works standalone.

Related packages

@reportwright/viewer (what this wraps), @reportwright/engine, @reportwright/fonts, and the react, vue and svelte wrappers.

MIT.