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

chunk-fetch

v25.0.4

Published

Use the same `fetch()` API browsers provide for HTTP, but for IPFS

Downloads

135

Readme

chunk-fetch

example of how a url looks like using chunk-fetch ipfs://someCidAsHostname/some/path

_ - hostname is ignored, url will start with the path and the path becomes the query, so ipfs://_/somepath becomes ipfs://somepath CID - a CID that is used for the query

method: HEAD - does not return a body, only returns headers hostname:

  • _ - ignores the hostname, path becomes the query path:
    • /path/to/dir/or/file - it can be any path including /, this path is the query that will be used with ipfs headers:
      • X-Copy - true | false - if true, a directory will be created with the CID, the data will be stored inside that directory. if false, the data will be stored using the path but without the new directory.
      • X-Timer - String - a number for a timeout
  • CID - a CID identifier for some data path:
    • / - used for a directory,if the CID is a directory headers:
      • X-Copy - true | false - if true, a directory will be created with the CID, the data will be stored inside that directory. if false, the data will be stored using the path but without the new directory.
      • X-Timer - String - a number for a timeout
    • /path/to/file - used for a file, if the CID is a file headers:
      • X-Copy - true | false - if true, a directory will be created with the CID, the data will be stored inside that directory. if false, the data will be stored using the path but without the new directory.
      • X-Timer - String - a number for a timeout

method: GET - return a body hostname:

  • _ - ignores the hostname, path becomes the query path:
    • /path/to/dir/or/file - it can be any path including /, this path is the query that will be used with ipfs headers:
      • X-Timer - String - a number for a timeout
  • CID - a CID identifier for some data path:
    • / - used for a directory if the CID is a directory headers:
      • X-Timer - String - a number for a timeout
    • /path/to/file - used for a file, if the CID is a file headers:
      • X-Timer - String - a number for a timeout

method: POST - return a body hostname:

  • _ - ignores the hostname, path becomes the query path:
    • /path/to/dir/or/file - it can be any path including /, this path is the query that will be used with ipfs headers:
      • X-Opt - String - options to use for the content, stringified object

method: DELETE - returns a body hostname:

  • _ - ignores the hostname, path becomes the query path:
    • /path/to/dir/or/file - it can be any path including /, this path is the query that will be used with ipfs headers:
      • X-Opt - String - options to use for the content, stringified object