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

lxl.harvest

v1.1.2

Published

Harvests data from given endpoints and saves them to a local folder

Readme

LxLabs Harvest Function

WordPress REST API calls take time, hammer users' bandwidth, occasionally fail, and don't really work offline.

The solution? We do all of the heavy lifting instead!

We can move the API request to build time instead of render time - using this handy harvest function!

This README is for version 1.1.2 and it would be appreciated if it was kept up-to-date if there are any changes made to the processes detailed here.

Getting started

Step 1

Install the package in your project using

npm install lxl.harvest

Step 2

Create a local task file

// harvest.js

const Harvest = require('lxl.harvest');

const options = {
  API: 'http://localhost/wp-json/wp/v2',
  ENDPOINTS: ['posts', 'pages'],
  FOLDER: 'src/_data',
  PERPAGE: 100,
}

const myApp = new Harvest(options);

myApp.init();

options

| Key | Value | | --------- | -------------------------------------------- | | API | The endpoint of the CMS | | ENDPOINTS | An array of endpoints | | FOLDER | The destination folder for the returned data | | PERPAGE | The maximum number of posts per page |

Step 3

Either run the task directly with node harvest.js or add the task to your build process in package.json

For example;

{ 
  "scripts": {
    "harvest": "node harvest.js",
  }
}
npm run harvest

Support 💪

Gotchas! 🤔

Housekeeping 🛋