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

fling-cli

v0.0.8

Published

Your daily log using Farcaster

Downloads

5

Readme

fling ⌆

fling (and retrieve) your daily logs with Farcaster. Read more about the fling pattern.

Setup

npm install -g fling-cli

This is a demo CLI tool, do not expect perfection!

For example, "signing in" to your Farcaster account is fairly hacky right now with this tool. Current implementation assumes two environment variables in your local shell: MNEMONIC and FNAME.

You could add these to your bash_profile directly (probably not advised, in case you keep your dotfiles in a public repo!), but what I've done is create a new file in my home directory called .fling that looks like this:

export MNEMONIC="twelve words go here"
export FNAME="my_farcaster_username"

And then I've updated my .bash_profile to source that file:

source ~/.fling

Just don't check in your .fling file to your dotfiles repo. Also, please submit a PR to improve this setup, please!

Usage

$ fling -m "* shipped basic web view for fling data"

Some time later that day:

$ fling -m $'* cli pushed to npm\n* sent proposal to first beta testers'

That's it! Your flings should show up in any Farcaster client, or you can try specific clients tuned just for the fling pattern, such as this demo web client.

Updating NPM package

npm run release