npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details


  • User packages



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.


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 🙏

© 2023 – Pkg Stats / Ryan Hefner




Searches for paths within pathseeker blocks and adds them to Grunt variables.





Searches for paths within pathseeker blocks and adds them to Grunt variables.

Getting Started

This plugin requires Grunt ~0.4.2

If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:

npm install grunt-pathseeker --save-dev

Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:


The "pathseeker" task

Pathseeker allows comment blocks to be defined within html files that can be searched for paths to scripts and stylesheets. Those paths are added to config variables that can be used by other task (such as minifiers) within the Gruntfile. This means any new script or stylesheet sources in the html will automatically be picked up by tasks that rely on them.


In your project's Gruntfile, add a section named pathseeker to the data object passed into grunt.initConfig().

  pathseeker: {
    your_target: {
      files: {
        src: ['app/index.html']

In the target html files, surround <script> or <link> tags with pathseeker comment blocks. Each block is opened with <!-- pathseeker:name --> and closed with <!-- pathseekerend -->. Each block must have a unique name specified after the semi-colon. This name will be the name of the variable made available in your Gruntfile.

        <!-- pathseeker:scripts -->
            <script src="test/first.js"></script>
            <script src="test/scripts/second.js"></script>
        <!-- endpathseeker -->

        <!-- pathseeker:styles -->
            <link rel="stylesheet" type="text/css" href="test/first.css">
            <link rel="stylesheet" type="text/css" href="test/styles/second.css">
        <!-- endpathseeker -->

Pathseeker will find all src and href paths within each block. These paths will be stored in arrays named after their respective blocks inside a pathseeker config variable. This config variable can be accessed anywhere in the Gruntfile.

var pf = grunt.config.get('pathseeker');
console.log( pf.styles );
// returns ['test/first.css', 'test/styles/second.css'] from the styles block

These arrays of paths can now be used by other tasks.

NOTE: Remember to run the pathseeker task before any tasks that need to access the pathseeker config variable.



Type: Boolean or String Default value: true

Prefixes all paths with a base path relative to the target source file. A string will explicitly override the prefix. Setting this to false will exclude the prefix entirely.


In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.

Release History

1.0.0 - Initial release