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

@kbco/pcpartpicker

v0.0.2

Published

An unofficial client for the 2019 PC part picker api

Downloads

9

Readme

What is @kbco/pcpartpicker?

This is mean to be a super dynamic library for querying against the undocumented API that PC Part Picker has.

Right now only the following part types are supported: cpu, cpu cooler, motherboard, memory, storage, video card, power supply, and case.

To add support for more part types, all that will need to be done is updating the constants.js file to have the proper mappings, and the actual api url.

So how do I use it?

yarn add pc-part-picker

or

npm add --save pc-part-picker

then somewhere in you script

Using async/await

const partPicker = require('@kbco/pcpartpicker');

let queryPartPicker = async (type) => await partPicker.query(partPicker.constants.urls[type], partPicker.constants[type])
  
let searchPartPicker = async (type, query) => await partPicker.search(type, query)

console.log(searchPartPicker('cpu', 'Ryzen'))

Using promises

const partPicker = require('@kbco/pcpartpicker');

function queryPartPicker (type) { 
    return partPicker.query(partPicker.constants.urls[type], partPicker.constants[type])
}

function searchPartPicker(type, query) {
    return partPicker.search(type, query)
}

searchPartPicker('cpu', 'Ryzen')
    .then(function (parts) {
        console.log(parts)
    })

Support on Beerpay

Hey dude! Help me out for a couple of :beers:!

Beerpay Beerpay

Proper Mappings

So this is a little bit tricky. I'll do my best to explain.

Finding the API endpoint.

  • Open the developer tools for your browser.

  • Go to the page you want to add support for.

  • Go to the network tab.

  • Look for the request that looks like ?mode=list&xslug=&search=

  • Copy that full URL and paste it into your local constants file.

  • Go back to the page and we're going to want to count the number of columns that it has, starting at 0 (zero)

    • Note that for each column, we may want to normalize the fields (like for the video card's page the column of index 1 is called "Video Card", we call it "name" since it's the name of the part).
  • Once you have the indices and the column names, you're going to want to put them in the constants.js file, associated with the proper key (You'll have to creat a new one...).