I did a similar thingy a while back: https://github.com/alganet/coral/blob/master/doc/spec/require.md https://github.com/alganet/coral/blob/master/doc/spec/req

I did a similar thingy a while back: https://github.com/alganet/coral/blob/master/doc/spec/require.md https://github.com/alganet/coral/blob/master/doc/spec/requir... It also does references (`require `something from inside modules) and some stuff. It is missing the download component though. I've also worked on https://github.com/Mosai/workshop https://github.com/Mosai/workshop, a previous attempt at shell tooling (please do not use it!) Also, there was a popular https://github.com/pixelomer/bashpm https://github.com/pixelomer/bashpm at some point. Most stable thing would probably be: https://github.com/shellfire-dev https://github.com/shellfire-dev Here are my thoughts working in this "hobby" for the last 6 years: - External tools are bad for shell portability and performance. It costs more to invoke "cut" than to do a loop and a couple of parameter expansions. Tools like cut, sed and similar are not suited for small strings, they are for large files. - ksh93 and ksh2020 support is possible, see: https://gist.github.com/bk2204/9dd24df0e4499a02a300578ebdca4728 https://gist.github.com/bk2204/9dd24df0e4499a02a300578ebdca4... These kshs are fast, I want them as supported engines. - Pipes are bad for performance. Local variable buffer is faster in all shells. There is a proof here somewhere: https://github.com/alganet/shell-proto https://github.com/alganet/shell-proto - We need to create a shell "dialect". Leave a lot of stuff out to simplify its syntax, so we can write a shell parser written in pure shell. This is a crucial point towards a better shell ecosystem. I have some research related to these issues, I'd love to collaborate in something. Standards, maybe? I think the shell community needs to talk as much as the early JS community did in the past.