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 🙏

© 2025 – Pkg Stats / Ryan Hefner

favicon-url

v0.0.5

Published

Get the actual favicon url of a given host domain

Readme

styled with prettier & JavaScript Style Guide

Project Goal

This utility was extracted out of REDPILL. The goal was to embed into the application the icon of a given host domain: ex..: google.com.

Possible solutions :

  • Every host domain url will most likely have a favicon.ico somewhere in the root so we might get away with guessing it: ex... for google.com -> http://google.com/favicon.ico

  • Use the content-length property of the headers' response in a network request to the icon directly. To validate the above point.

  • We could parse the host domain html structure and look for the link tag with the icon rel... etc.

The following scenarios are handled:

  • 200 status code
  • Other then 200
  • Icon type or invalid icon type
  • No data buffer present but status 200
  • No content-length in the request
  • Error
  • Timeout of the request to abort
  • Minimun Data buffer length

For all these you will either get the url or null. There will be no error handling(null if). The function only does 1 thing. Url or nothing.

Install

yarn add favicon-url

Run tests with mocha

$ yarn run test

API

const faviconUrl = require('favicon-url')

faviconUrl('google.com', {}, (favicon, dataBufferLength) => {
    // console.log(favicon)
    // console.log(dataBufferLength)
})

The options object


faviconUrl('google.com', {timeout: 2000, minBufferLength: 400, securedOnly: true}, (favicon, dataBufferLength) => {
    // Only favicons served over https.
    // console.log(favicon)
    // console.log(dataBufferLength)
})

The following properties are supported:

  • timeout (default: 8000) – The timeout of the HTTP/HTTPS request in milliseconds.

  • minBufferLength (default: 200) – sets the minimum length of the data buffer. Any favicon who's data buffer length is below will return null.

  • securedOnly (default: false) – sets the agent option per protocol, since HTTP and HTTPS use different agents. Example value: { securedOnly: true } will only return favicons served over HTTPS.

Dependencies

follow-redirects

MIT. Copyright (c) Wilkin Novo.