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

add-urls-to-planning-file

v8.54.1

Published

NB: THIS PROGRAM HAS NOT BEED TESTED IN CASE THE PRODUCT IS NOT AVAILABLE ON A WEBSITE. THE BEHAVIOR IN THIS CASE IS UNPREDICTABLE.

Downloads

2

Readme

add-urls-to-planning file

NB: THIS PROGRAM HAS NOT BEED TESTED IN CASE THE PRODUCT IS NOT AVAILABLE ON A WEBSITE. THE BEHAVIOR IN THIS CASE IS UNPREDICTABLE.

Usage

ENV=production node bin/run.js -u "http://spreadsheetUrl.com" -n "sheetName"

Manual test

  • consider the following spreadsheet to run test https://docs.google.com/spreadsheets/d/1EvD9mGr9zPAjTgifBc-dtT6PNlB4mcUywtUo_XJGo48/edit#gid=1097386816

How it works

Given an SKU and channel, it uses bing for searching for the query

site:amazon.de  "HF3507/20" // QUERY_TYPE=v1
domain:amazon.de intitle:"QE75Q7F" "QE75Q7F" "Produktinformation" // QUERY_TYPE=v2
domain:amazon.de && intitle:"QE65Q7F" && "QE65Q7F" && -intitle:"Suchergebnis auf" // QUERY_TYPE=v3

Example

It returns the triple <URL, name, URL_QUALITY>, representing:

  • URL: the page of the product (e.g. where the product is sold)
  • name: the name of the page as it appears on the search engine when you run a search
  • URL_QUALITY: if the name contains the SKU: because the name is usually the title of the page, and if the page contains the SKU, there is 99% chance that it is the correct page

Ideas for improvements (next versions)

  • a query like site:amazon.de "Modellnummer:HF3507/20" is much more strict, and it returns few result - usually just one - it could be used to increase the precision of the algorithm (less recall is acceptable)

Resources

  • sometimes site works, someother times don't, same for domain, check following examples

    TODO

    • [ ] Print report - out of tot entries, tot URLs has been found (percentage, and absolute numbers)
    • [ ] To add validation of the column of the spreadsheet: each row should have at least the fields <sku, channel, urlName, urlQuality, url>