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

pear-link

v4.2.1

Published

Parse Pear Links

Readme

pear-link

Parse Pear Links. This includes URLs with pear: & file: protocols.

npm install pear-link

Pear Link Format

The pear: protocol supports the following syntax:

pear://[<fork>.][<length>.]<keyOrAlias>[.<dhash>]<path>[?<search>][#<lochash>]
  • fork is the fork id for the underlying hypercore.
  • length is the length of the underlying hypercore.
  • keyOrAlias is the z32 or hex encoded key or an alias for the key.
  • path is zero or more path segments separated by a /.
  • search is a query string of non-hierarchical data proceeded by a question mark (?).
  • lochash is the fragment proceeded by a hash (#).

API

const plink = require('pear-link')

Exports a singleton with methods parse, serialize and normalize.

Supports aliases per pear-aliases.

const { protocol, pathname, search, hash, origin, drive } = plink.parse(url)

Parses the provided url string returning an object describing the URL's properties.

The returned object contains the following:

{
  protocol, // The url's protocol. Supported protocols include `pear:` & `file:`
  pathname, // The `some/path` in `pear://key/some/path`. Same as the standard URL pathname
  search,   // The query string in the URL, aka anything after a `?` including the `?`
  hash,     // The fragment part of the URL, eg `#fragment` in `pear://key/path#fragment`. Includes the `#`.
  origin: this.normalize(`${protocol}//${hostname}${pathname}`),
  drive: {
    key,    // The key for the hyperdrive. Usually the `key` part of a pear link.
    length, // The hyperdrive length defined in the URL.
    fork,   // The hyperdrive fork defined in the URL.
    hash,   // The dhash in the URL.
  }
}

const normalizedLink = plink.normalize(link)

Normalizes the link by removing trailing path separators (/).

const link = plink.serialize({ protocol, pathname, search, hash, drive }) | const link = plink.serialize(key)

Expects either

  • a parsed object as returned by plink.parse
  • a hypercore-id-encoding key, eg drive.key - the key in pear://<key> - key may be buffer or string.

Returns a pear:// link as a string.

License

Apache-2.0