Hi thanks for the response. My use case would be to execute relatively small snippets of shell code/one-liners as part of an asset management pipeline without having to "shell-out" and invoke an external process, mostly at deploy-time, in a portable fashion, such as rendering a static HTML file upon change of dependent data, or rendering an image/icon from a vector format representation, and similar tasks. Requirements for shell control constructs are modest, but piping and redirection should work, as well as limited shell var/macros expansion, and maybe if/then. In Node.js-land, there's the shelljs package which is both an API for (synchronous-only AFAICS) shell-like ops (as in "shelljs.ls('file.???')" and a (very limited) shell syntax parser that could call those funcs from a string ("ls file.???") like yours as far as I can understand, but I guess yours is already more capable then the one shelljs uses. Still, shelljs is used as a dependency by quite a number of high-profile packages.
Node.js is much more useful simply because everything in js-land (asset management tools, web server backends) runs on Node.js rather than deno :)
