For when you want to yeet things. Files mainly.
Yeetr provides a cli wrapper for various methods of sharing files. Sharing is, by design, ephemeral, so, the link that yeetr provides will expire, after a given time or when the file is downloaded. This is great for two reasons:
- No confusion about which file the recipient has (e.g. searching through an email chain)
- No old versions cluttering up Google Drive, dropbox, etc.
For persistent storage, sharing and deployments, you should use something else, like Netlify, Vercel, or roll your own S3 hosting.
Note that there's a limit of 100mb on files.
npm install yeetr -g
// from any directory
yeet
Yeetr by default will offer a list of files in your current working directory.
You can scroll through this list, or use the autocomplete function to narrow down the selection.
Hit enter to confirm, and that's it.
When you just want to send a file to someone, use
yeet [dir] [expiry]
So just running yeet in your current directory will let you select a file and then use our default 1 day expiry for hosting. We print the file to console output and you can copy/paste it as you wish.
Sending files uses file.io, a wonderful service that provides ephemeral file storage.
You can specify the expiry time, but remember that the link expires as soon as it's downloaded as well.
// lists files in current dir
yeet
// current dir, expires in 3 days
yeet . 3d
// expires in 4 weeks
yeet . 4w
// another dir, in 2 months
yeet /Users/rasputin/gifs 2m
// passing a direct path using -f or --file
// (no search)
yeet -f /Users/rasputin/gifs/rara.gif -e 3d
A forthcoming feature we'll add is to be able to email a link to the file to whomever you wish. I'm using Courier at the moment to do this. To make this work you're going to need to put a copy of the .yeetconfig.example file in your home directory (~/), rename it to .yeetconfig and provide the details given to you when configuring Courier.
Adding an at or a parameter to the one-line yeet will then attempt to email a link to the uploaded file to the receipient.
yeet -f avatar.jpg -e 3w -a [email protected]
I plan to add direct support for e.g. Mailgun but I wanted to try out Courier, so here we are. The neat thing about courier is you can customise the email like this:
Quick, emphemeral static web hosting does have a use case but there are already some great existing solutions.
Honestly, you should use netlify for this, or better yet, surge.
Stay tuned for what we come up with in this space, though.
- commander.js
- inquirer
- axios
- chalk
All of which are awesome and made by far more talented people than I.
Building this was a learning experience for me in trying to develop a CLI in node.js. My goal was to focus on a simple and streamlined user experience. I really enjoy well-designed CLI programs and wanted to try making one myself.
Frequently in software development we need to
- swap snippets of code, documentation, configuration
- deliver an asset without polluting email threads or slack channels
- stage a project for someone to view
Uploading a file for sharing invariably leaves an artifact behind: a file attached to an email, or an old version of the documentation left rotting on a chat client somewhere.
For situations where you need one-time file sharing that auto-expires, just yeet it.
Only as secure as uploading something to internet. Which is probably not secure enough if you're asking this question.
If you want to securely share credentials I'd head on over to magic wormhole.
Where's the file you sent?
Oh, I yote it over a couple hours aho
Why's George so late?
He was yeeting files late last night to family and friends
