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

bad-typing-converter-cli

v1.0.1

Published

Bad Typing Converter, but in your terminal! Built using node.js

Downloads

2

Readme

Bad-Typing-Converter-CLI

Setup

Prerequisites

  • Node.js
  • Git (optional)
  • a brain
  • An OpenAI API Key

Method 1

$ npm i bad-typing-converter-cli

Go to wherever you downloaded this, for example ./node_modules/bad-typing-converter-cli/

$ cp .env.example .env

Open up .env, and paste in your OpenAI API key. Save, and close. You can now use btcc anywhere in your terminal!

Method 2

$ git clone https://github.com/FireStreaker2/Bad-Typing-Converter-CLI.git
$ cd Bad-Typing-Converter-CLI
$ npm i
$ npm i -g
$ btcc ping

If it replies with Pong!, proceed to the next step. If it doesn't, you did something wrong lmao

$ cp .env.example .env

Open and paste your OpenAI API key into the .env file, then save and close. Now, return to your terminal.

$ btcc ping

PLEASE NOTE THAT IF YOU DO NOT RUN npm i -g AFTER THE OTHER STEPS IN METHOD 2 YOU WILL NOT BE ABLE TO USE IT WITH btcc

Commands

You can run btcc or btcc help to display all the current commands, but they'll also be listed below.

btcc - displays help
btcc help - also displays the help message
btcc ping - pings something (idk what it pings) to make sure the cli is working
btcc website - open the website version of this
btcc convert <phrase> - the actual converting part. just do btcc convert + your phrase, and it'll convert after a while. please note that a) you need to have your api key configured, and b) if your phrase is more than one word, you have to surround it in double quotes. (ex. ``btcc convert "hello today i wnt to ues discord")

FAQ

Q: Why did you make this?
A: idk i wanted to make a cli for some reason

Q: whats the purpose of this?
A: so you can quickly translate your friends badly typed sentence i guess

Q: Will this be maintained?
A: probably not lmao

Q: This doesn't work for me, what should I do?
A: make sure you followed the steps, if it still doesnt work you can open an issue and ill help you from there

Q: You suck at coding
A: i know

Contributing

If you would like to contribute, you can fork the repo and make a PR, or contact me via email @ [email protected]

Credits

OpenAI API
Commander
NPM

License

MIT