This is fantastic! It would be really great if the CLI supported summoning a specific Pokemon, is that planned at all?
Pokemonsay: Pokemon Version of Cowsay
51–54 of 54 posts
Re: Pokemonsay: Pokemon Version of Cowsay
#52Earlier quoted context omitted.
Most of the code here is for scraping images from a 3rd party and converting them into colored blank spaces to display in the terminal. The actual code used to pick a random Pokemon and display it is only a few dozen lines.
Where does the conversion from .png to tiles happen? Is it part of boxen? I can't seem to locate it within the source.
It's kinda hidden in the webpack config using a loader (written by the same guy!) that does the heavy lifting
Re: Pokemonsay: Pokemon Version of Cowsay
#53I built something similar, but it uses pokefusion ( https://pokemon.alexonsager.net/ ) to generate randomly fused Pokemon https://github.com/danjordan/pokefusion You can run it with `npx pokefusion`
Nice one. The combination of Flareon and Magneton looks like something from Futurama.
Edit: nitpick: have the selectors ordered alphabetically.
Re: Pokemonsay: Pokemon Version of Cowsay
#54Earlier quoted context omitted.
I think we should do this. When writing a tiny, trivial utility, it doesn't make sense to bring in a ton of dependencies. Disk space, memory usage, and download size all matter, especially to those of us who use old hardware on rural satellite connections. Your final paragraph had a good point, though. It's not just cowsay.
The complaint about "bringing in Node" and all the other dependencies is silly. Developers familiar with Node will already have it on their system - notch. Then the dependencies are just part of the ecosystem since this stuff ain't compiled. So, pointing it out is just being pedantic - that's all.
I'm baffled by this comment, as it seems to imply that cowsay and similar are developer tools.