drkraken

main difference from all of this tools, that they try to create bridge between different shell types, instead of providing same API, integrated with other tools.

also, xeon.js, xeon github - 1 result

If I understand you right, child process is made by utility that check your local version and laters to notify your for updates. It should only be called once an hour

It not depend on Node.js.

Xeon just add ability to use npm as your package manager, why use tools like bpkg or something else if you can use great environment that trusted by thousands people.

Xeon bundle should be made on dev step, you should not bundle it on real server .etc where u use this script.

glag to see that you got my point, maybe for now its kind like early version, but it will make sense.

better management of your dependencies, also bundling to single file for easier distribution. In future transforming scripts with plugins means reusing fish shell functions in bash scripts .etc Also each shell has different syntax for sourcing files.