quickscript VS steggy

I also have have an example respository, which has already been already set up to consume the libraries and tools, build, and publish

I've been promising myself I'd make a post about my side project all year, and just barely making that goal. Been building out a set of custom libraries on top of the NestJS direct injection tooling, and one of my favorite core libraries is @steggy/tty. It started off as a set of extensions and custom widgets on top of inquirer, but has since gone its own direction with rebuilt internals.

As I mentioned with the title, @steggy is a wrapper around NestJS. I've taken to the pattern of replacing their annotations, and passing the call along or just doing the same work here. My goal when building the tools was to make it super easy to do very complex looking single file scripts. Here is another script, for more reference of what I was going for (@steggy/config-builder).

source for script, all the libraries can be found int eh libs folder at the root of the repo. The sampler app can be directly installed via NPM:

The backend - dockerized nodejs program that actually processes all the commands. It comes with a web ui (screenshots in the links there), which is used to configure things.

Been playing around with a little side project this year, link to the repo. It's a server application that sits around running the automations, and a TUI program that interacts with it via http commands.

1) Define a metadata file which describes your configuration variables the library / application consumes. - Matching JSON Shema 2. When defining a new configuration variable, define it first in the metadata file, then make it available inside the application - Nothing complicated here. Duplicating into the config file is technically optional (you could just use the string directly), but I'd recommend it as a good practice anyways 3. Inject the property into your Provider using @InjectConfig