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 🙏

© 2024 – Pkg Stats / Ryan Hefner

diagnostics-pagelet

v1.0.5

Published

Default diagnostics Pagelet used by the 404 and 500 Pagelet

Downloads

26

Readme

Diagnostics Pagelet

Version npmBuild StatusDependenciesCoverage Status

Default diagnostics Pagelet used by the diagnostics and 500 Pagelet. This Pagelet is responsible for displaying additional diagnostics. By default the diagnostics Pagelet is provided with BigPipe. However, if you need a custom diagnostics you can extend this Pagelet. For example to change the default view.

Installation

The diagnostics Pagelet is distributed through the node package manager (npm).

npm install --save diagnostics-pagelet

Support

Got stuck? Or can't wrap your head around a concept or just want some feedback, we got a dedicated IRC channel for that on Freenode:

  • IRC Server: irc.freenode.net
  • IRC Room: #bigpipe

Still stuck? Create an issue. Every question you have is a bug in our documentation and that should be corrected. So please, don't hesitate to create issues, many of them.

Example

In this example the diagnostics Pagelet is extended with a custom view, which in turn is provided to a custom 500 Pagelet. BigPipe will automatically discover this extended version of the 500 Pagelet if it is provided to BigPipe alongside the other pagelets.

'use strict';

//
// Extend 500 Pagelet with custom Diagnostics Pagelet.
//
var Fivehundred = require('500-pagelet').extend({
  pagelets: {
    diagnostics: require('diagnostics-pagelet').extend({
      view: '/path/to/my/custom-view.html'
    })
  }
});

Debugging

The library makes use the diagnostics module from Pagelet. To display the diagnostics Pagelet specific debug messages, supply the following before running the program or

DEBUG=pagelet:diagnostics node ...

Testing

Tests are automatically run on Travis CI to ensure that everything is functioning as intended. For local development we automatically install a pre-commit hook that runs the npm test command every time you commit changes. This ensures that we don't push any broken code in to this project.

To run tests locally, make sure the development dependencies are installed.

npm test
npm run coverage

License

diagnostics-pagelet is released under MIT.