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

topology-viewer2

v0.0.20

Published

Topology Viewer component library

Downloads

31

Readme

Topology Report

It is a React component for the Topology Report. It is transpiled with Babel and bundled with Rollup. It can be published to a NPM registry (public or private) which can then be imported by React or Angular applications. It requires BootStrap 4 to work properly.

To install dependencies: npm install

To run tests: npm test

To build: npm run build

This builds the component in the build directory.

To publish to a npm registry: npm publish

To install it from npm after publishing: npm install topology-viewer2

Integration with Angular

  1. Create an Angular component wrapper.
import {TopologyViewer} from 'topology-viewer2/build';
...

export class TopologyViewerComponent implements AfterViewInit {

    @Input()
    public content = '';

    constructor(private router: Router, private hostRef: ElementRef) {
      this.onComputerTableClick=this.onComputerTableClick.bind(this)
      this.onInstrumentTableClick=this.onInstrumentTableClick.bind(this)
    }

    ngAfterViewInit(): void {
      this.render();
    }

    onComputerTableClick(name:string) : void {
      this.router.navigate(['computer-details', name]);
    }

    onInstrumentTableClick(name:string) : void {
      this.router.navigate(['instrument-details', name]);
    }

    private render(): void {
      const hostElement = this.hostRef.nativeElement;
      const tvElement = React.createElement(TopologyViewer, {
          handleComputerTableClick : this.onComputerTableClick,
          handleInstrumentTableClick : this.onInstrumentTableClick
        }, this.content)    
      ReactDOM.render(tvElement, hostElement)  
  }

}
  1. Create ComputerDetailsComponent:
import {ComputerDetails} from 'topology-viewer2/build';
...
export class ComputerDetailsComponent implements AfterViewInit, OnInit {

    name : string

    @Input()
    public content = '';

    constructor(private router: Router, private route: ActivatedRoute, private hostRef: ElementRef) {
      this.onNodeClick=this.onNodeClick.bind(this)
    }

    ngOnInit() {
      this.name = this.route.snapshot.paramMap.get('name')
    }

    ngAfterViewInit(): void {      
      this.render();
    }

    onNodeClick(name:string) : void {
      this.router.navigate(['instrument-details', name]);
    }

    private render(): void {
      const hostElement = this.hostRef.nativeElement;
      const computerDetails = React.createElement(ComputerDetails,  
        {match:{params:{name:this.name}}, 
        handleNodeClick:this.onNodeClick}, 
        this.content)     
      ReactDOM.render(computerDetails, hostElement)  
  }
  1. Create InstrumentDetailsComponent in a similar manner.
  2. Add routes to the RoutingModule that route 'computer-details' to ComputerDetailsComponent and 'instrument-details' to InstrumentDetailsCoomponent. (Adjust the paths accordingly.)