0.0.2 • Published 3 years ago
hugtight v0.0.2
hugtight
CLI for devs to turn twitter app/dev tokens into user tokens
Mr Twit was good at catching birds. On the day before Bird Pie day, he would put the ladder up against The Big Dead Tree and climb into the branches with a bucket of glue and a paint-brush. The glue he used was something called HUGTIGHT and it was stickier than any other glue in the world. He would paint it along the tops of all the branches and then go away.
usage
TWITTER_API_KEY=xxxxxx \
TWITTER_API_SECRET=yyyyyyyyyy \
TWITTER_ACCESS_TOKEN=zzzzzzz \
TWITTER_ACCESS_TOKEN_SECRET=qqqqqqqqqq
npx hugtight
use the tokens from your twitter app and your developer account and it'll walk you through getting credentials for a different user. when it's done, it'll print them out as env vars for you to use in other commands, like:
TWITTER_ACCESS_TOKEN=hualgahualghuahg
TWITTER_ACCESS_TOKEN_SECRET=a8os7ydna8sd7ya9s8nyda8yn77o
Notes
- Output to a file by redirecting stdout, e.g.
npx hugtight >> .env
. All the prompts and logging are on the stderr stream, so they won't output to the file; only the env vars themselves will. - Uses
dotenv
to get env vars, so if you don't pass 'em at the command line, it will use the api keys and other env vars in an.env
file in the working directory if one exists.