Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ANSI color codes don't work when in production #1

Closed
savioxavier opened this issue Feb 9, 2022 · 2 comments · Fixed by #2
Closed

ANSI color codes don't work when in production #1

savioxavier opened this issue Feb 9, 2022 · 2 comments · Fixed by #2
Labels
bug Something isn't working help wanted Extra attention is needed

Comments

@savioxavier
Copy link
Owner

savioxavier commented Feb 9, 2022

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:
image

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

@savioxavier savioxavier added bug Something isn't working help wanted Extra attention is needed labels Feb 9, 2022
@savioxavier
Copy link
Owner Author

Here's a preview of what it should look like:

image

The issue might have something to do with the Railway hosting, since I didn't see any chalk colored outputs in the deploy logs either. Is it possible that the hosting service is the reason?

@savioxavier
Copy link
Owner Author

Fixed in #2, and no, the culprit wasn't fs, it was chalk.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant