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

list-fetch

v31.0.9

Published

coming soon

Downloads

34

Readme

list-fetch

example of how a url looks like using list-fetch bt://someAddressOrInfohashAsHostname/some/path

_ - does different things depending on the http method address - a public key that is 64 characters that is used as an address infohash - a identifier for torrents that is 40 characters

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

  • _ - user's own data path:
    • / - if path is / then it returns data about the current torrents, if no headers are used, then it returns the byte size and count of all of the authored torrents headers:
      • X-Data - true | false - if true, it returns the byte size and count of all the torrents, if false, it returns only the count of all the torrents
    • /path/to/dir/or/file - if path is not / then it returns data in the headers about the user directory that is local and not publically shared
  • address | infohash - a torrent you want to load path:
    • /any/path/to/dir/or/file - it can be any path including /, if no headers, it returns the byte size, link, and other data of the torrent in the headers headers:
      • X-Copy - true | false - if true, copies a file and saves it to the user directory(with the address or infohash as the directory name, it is publically shared) on the local disk, if false, copies a file and saves it to the user directory(it is publically shared) on the local disk
      • X-Timer - String - a number for a timeout

method: GET - return a body hostname:

  • _ - user's own data path:
    • / - if path is / then it is same as HEAD, in addition, it also sends a body. if there are no headers, then only author data is returned headers:
      • X-Data - true | false - if true, it returns the byte size and count of all the torrents, if false, it returns only the count of all the torrents
    • /path/to/dir/or/file - if path is not / then it is the same as HEAD, in addition, it also sends a body
  • address | infohash - a torrent you want to load path:
    • /any/path/to/dir/or/file - it can be any path including /, if no headers, it returns the byte size, link, and other data in the headers headers:
      • Range - if path is a file, it returns the data from a file that fits this range
      • X-Timer - String - a number for a timeout

method: POST - return a body hostname:

  • _ - make a new torrent path:
    • /path/to/dir/or/file - any path, this is where the files will go for the torrent body:
    • FormData | String - either FormData which will hold the files or some string for a single file headers:
    • X-Update - true | false - if true, a mutable BEP46 torrent, if false, an immutable regular torrent
    • X-Version - String - what sequence to use for the torrent
    • X-Opt - String - options to use for the content, stringified object
  • address | infohash - an already existing torrent that you want to modify path:
    • /path/to/dir/or/file - any path, this is where the files will go for the torrent body:
    • FormData | String - either FormData which will hold the files or some string for a single file headers:
    • X-Version - String - what sequence to use for the torrent
    • X-Opt - String - options to use for the content, stringified object

method: DELETE - returns a body hostname:

  • _ - delete user directory data path:
    • /path/to/dir/or/file - any path, this is where the files will go for the torrent
  • address | infohash - an already existing torrent to delete entirely or modify path:
    • /path/to/dir/or/file - any path, if / then entire torrent is delete, if not /, then only the path is deleted and a new torrent is made headers:
    • X-Opt - String - options to use for the content, stringified object