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

pod-upload

v1.1.0

Published

## Quick start

Downloads

8

Readme

pod-upload

Quick start

npm i -g pod-upload

or

yarn global add pod-upload
pod-upload --key=XXX path/to/collection/

The key value is obtained by creating a new account at https://nft.storage/ -> API keys

This command when run will do the following:

  1. It will scan the images to collect all .png and .gif files and upload them to the IPFS, what we get back is a CID (Content Identifier - a hash) of that image/gif
  2. When it got the CID back it will modify the matching json metadata file and insert a new property image
  3. After all metadata files is updated, it will pack the metadata directory into a CAR file and upload that to IPFS as well - which will return another CID back to us.

In the end we will have one single CID that is the root of all metada files and in each file there is an updated ipfs url to the image.

Notes

  1. This command will permanately upload your data to the public internet which will be impossible to remove once it is cached on other peers's node so think carefully before you decide to run it

  2. If by any chance that you encounter an error during run (e.g 429 too many requests on the nft.storage api) you can decrease the limit option (default is 5 which should be acceptable by nft.storage)

    pod-upload --limit=2 path/to/collection/

    Any uploaded file before the error happened will be skipped so it won't wastefully do the whole list twice

  3. collection should follow this structure

    collection/
    ├─ images/
    │  ├─ 0.png
    │  ├─ 1.png
    │  ├─ 2.png
    │  ├─ ...
    ├─ metadata/
    │  ├─ 0
    │  ├─ 1
    │  ├─ 2
    │  ├─ ...