Echo JS 0.11.0

Updated link to github repo.

Not surprised that for-loop was fastest followed by reduce.

Kinda weird in the comparison section... Would probably compare this with Caddy and Nginx, and no detail in terms of throughput or perf, where I think either of the mentioned would outdo this server.

Just came across this... seems to be relatively API compatible with node, with a much lower cold start and latency time compared to Node/Deno.  It's being developed to target Lambda at Amazon, but should work with other environments.

Would work on expanding the test harness... the application breakdown may not lead to good testing structure.  Also, I would recommend having the test next to the module being tested as a general rule.

On the latter part, some projects (looking at you ASP.Net) will break up structure into mirrored trees... you'll have a controller, view, js, etc all with the same name sitting in different directories... the same for tests (in this case), where you wind up hunting across directories looking for things that are the same contextual concern.  I prefer to see a structure based on the context/feature concern where the different types of files are next to each other in the directory, so they're easy to navigate between when working in that context and this includes tests imo.

I didn't dig into the code, so can't comment much on what is or isn't in place.  I'm generally not a big fan of ORMs in general, especially in a scripted language, as you can usuaally do type inference from a simpler mapping from direct SQL. With a taggeed template string processor in the case of JS.

As for Joi, tend to prefer Zod myself, as it has *much* better TS inference imo.

This is EchoJS, not EchoPython

Probably worth looking at xterm.js[1] for a more fully featured terminal client for browser usage.  It's the core of what's used in VS Code's terminal tab as well as Tabby and other terminal apps.

1. http://xtermjs.org/

make sure body,html are set width: 1vw, minHeight: 1vh ... or 100%.

You would need to update the target domain to return appropriate CORS headers, allowing your resource domain, there's nothing you can do from the client.  If you don't control the resource domain, you will need to setup a reverse proxy.

I've generally used Caddy in a Docker container to serve static app resources and revere proxy an /api route as needed.  Most web frameworks will have the option to do the same for while you're in watch/dev mode.

Mentions Node's Buffer, but no mention on converting strings to/from Uint8Array (typed array) to/from base64.  The inverse methods should also be present or linked.