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

dse_public_content_html

v1.0.0

Published

dse static html

Readme

This file system is statically delivered by a server. To modify and debug please read the sections on dev-server and index.js.

-- dev-server To run dev-server 1.) unzip dev-server.zipx to here. 2.) install gulp globally (npm install --global gulp-cli) 3.) run cmd (npm run gulp)

The server should start with no errors and should serve the files like the application server.

-- index.js This project is set up to be a modular angularJS application. The index file can but should not be modified directly.

There are two "POWERSHELL" scripts that can be used to break down index.js and watch for changes in the broken down files. Thes files are found in the "Expand" folder.

Breakdown.ps1
  Reads index.js and creates the file system described by the comments of
  the form //-- {file name relitive to the Breakdown folder} --//.
  run with: & .\Breakdown.ps1

Watch.ps1
  Watches all js files in the Breakdown folder and bundles them into
  index.js when any of the files are updated.
  run with: & .\Watch.ps1

Run both commands $.\Breakdown.ps1; &.\Watch.ps1
  This is recommened when ever pulling file for the first time since
  index.js could have been updated directly.

-- content.html This html file is used to import html resources in the en and es folder.

URL Parameters: resource - this is the file name, exculding '.html' of the resource you wish to retrieve. It will pull files from both/all the en and es folder if they exist. If both exist - it will display english by default(see lang param) and a link in the upper right will allow you to switch languages.

              If only one exists - The one that exists will be displayed
                regardless of language requested.

              if non exist - an error message will be displayed.

lang - This param will set the "perferred" language of the resource.
  If resource exists in more than one language including the perferred - the
    perferred will be displayed and the other valid laguages can be switched
    two by buttons in the upper right corner.

  If resource dne in perferred language, it will be displayed in the first
    valid language found(see ContentController.js: function show content).

Creating new language Simply add language to the "LANG" array in ConstantService.js and add a import-html tag in the same format as the en and spanish tags, Changing the lang param of course. All functions should be generalized and you are done!

-- css format Css to control 90+ percent of the content is found in style.css, between the /**** Rebranding ****/ comment at the top of the page.

To rebrand simply open the resource css-format in your browser and then modify all the css to conform the the new style.