Upstreaming suggestions?

[jpco]

Hi there,

I'm the most active developer on the "upstream" https://github.com/wryun/es-shell repo these days.

What you've got going on here is impressive. If there's any of it you want to upstream -- or anything you've done that you think I should do the work to upstream -- I'd be happy to talk. I would personally be especially grateful for anything in the space of bug fixes, performance/resource utilization improvements, tests, portability, build tooling, and the like.

(I'm also curious about the module system!)

[mveety]

I'd be interested in helping upstream some of my code. This branch has been pretty experimental and some of the experiments have landed pretty well. My modules system is sort of for that; I wanted a way to load new code into the shell actually in use and installed on my system. It's helped too in adding features without adding primitives or adding functionality leveraging outside dependencies without requiring them in the shell.

The line editor I wrote to replace readline would probably be a pretty useful thing to upstream. It's not totally 100% yet, but it might be a good addition because its more integrable into the shell. I can configure the editor and hook into it from the shell.

The library stuff has proven to be the most useful thing I've added. Being able to load files from a central path has been very useful. I think that might be pretty easy to upstream.

Some of the other things (dicts, etc) would be cool to add, but need work on the syntax end and also might be out of the scope or vision you guys have the shell.