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

hipr-ipfs

v0.5.1

Published

## Usage

Downloads

3

Readme

IPFS Middleware

Usage

hipr-ipfs is hipr middleware.

if you don't have hipr installed, run

npm i -g hipr

then you can install the hipr-ipfs middleware

hipr install hipr-ipfs

and spin up a server

hipr hipr-ipfs :5333 198.41.0.4

this starts a recursive server on port 5333 capable of resolving zone files from ipfs using one of ICANN's root server as a stub resolver. If you want to resolve handshake names, and you are running hsd or hnsd with a root server on port 5349, then start hipr with

hipr hipr-ipfs :5333 :5349

Example

You can test that hipr is resolving properly by running

> dig @127.0.0.1 -p 5333 ipfs.chan0
66.42.108.201

which resolves ipfs.chan0 A via the ipfs zone file bafybeibr4k6zof34lj3goushjbzbruqa6eknfvqrrlmizvbjfkn5x4nw6m obtained from the HIP-5 NS record

ipfs.chan0. 3600 IN NS bafybeibr4k6zof34lj3goushjbzbruqa6eknfvqrrlmizvbjfkn5x4nw6m._ipfs.

in the parent zone chan0. Note, bafybeibr4k6zof34lj3goushjbzbruqa6eknfvqrrlmizvbjfkn5x4nw6m is the CIDv1 (base32) encoded IPFS content identifier.

If you want to convert to CIDv1, you can use the CID Inspector.

IMPORTANT: the CIDv0 (base58) encoding QmRhPDZ6DAnWKpzpt8tUwqNujS9uyZp69nDKF5Re9wrfdk cannot be used in your NS record. For example,

; INVALID !!
ipfs.chan0. 3600 IN NS QmRhPDZ6DAnWKpzpt8tUwqNujS9uyZp69nDKF5Re9wrfdk._ipfs.

will not resolve properly, because hostnames are case-insensitive and the CID will be parsed as qmrhpdz6danwkpzpt8tuwqnujs9uyzp69ndkf5re9wrfdk. You've been warned!