savioxavier / discord-neofetch

Display your Discord information - neofetch style!

Hey, I'm Savio

I develop CLI tools, libraries and webapps. See my collection of repos for more.

cat github.ts

/* eslint-enable better-readme */
const self = (
  l: Language<'python' | 'go' | 'typescript' | 'javascript'>,
  f: Framework<'next' | 'react' | 'vue' | 'nuxt' | 'svelte'>,
  s: Shell<'zsh' | 'bash' | 'powershell'>,
  e: Editor<'vscode' | 'neovim' | 'pycharm'>
): GitHubProfile => gh.update('savioxavier', { l, f, s, e })

GET /stats

`

☕

discord-neofetch's Issues

ANSI color codes don't work when in production

Currently, the bot uses chalk-template for the ANSI escape codes, and node:fs for rendering the ascii arts right, but apparently, after the bot was hosted on Railway, none of the above stuff worked.

The ascii arts aren't aligned correctly too, here's a picture for demo purposes:

Not sure what the issue is, might be because I used node:fs instead of fs, but should not affect anything, I guess. Or maybe chalk-template's colors are somehow stripped and don't show up for some reason in production.

Edit: no change as of commit 0294780
Edit 2: no change as of commit 1cf120e

Known issues and required features

Bot is currently kinda unstable (due to bad code) and needs a few fixes

• Better interaction handling. Bot usually crashes due to an "Unknown Message" error (and usually restarts, thanks to Railway) but that's a problem that needs to be fixed
• Better error handling, due to errors like "Unknown Interaction" and "Unknown Message" crashing the bot, I had to pass empty catch statements all over the code, which is bad practice really
• Button interaction error: interactions usually fail sometimes. Not good.
• Better slash command deployment handling. Currently the bot registers slash command on every run in production and I'm not really sure if that's a good idea. For some reason, I couldn't execute two scripts in succession in Railway, even with a process.exit() in the code to move on to the next script
• A proper logger (eg: pino)
• Command cleanup and refactoring
• A few bug fixes. A lot of bug fixes

If you do know how to fix these issues, please submit a PR, that would be much appreciated.