Attempt to create a simplistic CLI

[Vizonex]

What do these changes do?

This change adds a standalone script requested by @ahaoboy This is nothing fancy and just passes along print statements and other various artifacts that were established in other PRs However this does close an old issue. My IRL Job has had me by the neck for a couple of weeks since this additional feature was requested. I kept this simple and wanted to use typer as the main system for various reasons (mainly time restraints that are on my plate and keeping things relatively easy to diagnose if cyjs decides to go haywire).

Are there changes in behavior for the user?

Nope have fun with the script if you need CLI please type the following, This will install typer as a requirement to utilize these tools.

Note

typer can be a bit slow and shouldn't be measured for benchmarking but perhaps tools for that could be added in the future for those who care about these sorts of things. They also have made reporting issues a large gate due to the number of AI/Bot Generated issues which in my opinion might be more awful than I expect but hopefully issue reporting will be more relaxed in the future. Otherwise I did have the idea of building my own using the same backend (click) but using it's actual pypi package (typer pretty much forked from click's modules).

uv pip install cyjs[cli]

I've already found ways to invoke it from the commandline although I didn't dig super deep with this mainly to keep the simplistic nature in tact although I would've preferred mimicking the QJSC standalone tool directly but perhaps a contributor or newcomer will step in help finish what I have started. :-/ seems a little grim but It's quite possible.

How to use

py -m cyjs -e "console.log('Hello Vizonex');"
Hello Vizonex

Is it a substantial burden for the maintainers to support this?

I have done everything in my power to ensure that this script does not cause me a developer burden in the growing years.
A Competing tool to typer might be invented in the future that could be a lot better than typer if I can figure out the complex logic that typer currently implements otherwise I could always fork it and make my own.

Related issue number

Closes #19

Checklist

• I think the code is well written
• Unit tests for the changes exist
• Documentation reflects the changes