Echo JS 0.11.0

I updated the URL to the repo itself, since it's actually mostly written in JS/TS... but as a completely separate language, it's otherwise borderline off-topic.

Edit: not knocking the tooling at all, which is pretty interesting.  I've been a relatively heavy proponent of just using scripting language(s) and some unified libraries as much as possible for different ETL work... especially variations on data ingress/egress.  Where it's sometimes easier to manage many different solutions for each resource over trying to create more complex tooling.

Interesting... I might take a look once you have PostgreSQL and/or SQLite support working in the box.  Would suggest looking at some of the database extensions that are used with VS Code for refinement and inspiration... the MS-SQL extension is one of the better ones, you can run in docker pretty easily for the server instance, though on arm mac, you'll need Rosetta2 configured with Docker.

I would also suggest using the Rust side to handle at least the main portions of theming as much as possible... Windows, Mac, Linux (Gnome/GTK or KDE/Qt theme detection) to establish a baseline light/dark and appropriate accent/highlight color for buttons, etc.  This is an area were you can go a long way with just a minor amount of time ensuring appropriate fonts/colors for the environment by default.  Much easier with Rust than Electron even.

On the AI front, Not sure if it would be worth trying to train a relatively limited cpu-based model, given a populated database/schema table(s) constructed to a more common format... the variance will really come down to db specific characteristics...  MySQL/Maria's back-tick usage vs pg's case handling and ansi-quotes and MS-SQL's square brackets.  They all also have different schema interrogation to get the schema structure as well as varying behaviors.  SQLite in particular is both better and worse than MySQL in some ways depending on your schema definitions vs usage.

Other than the variance, the SQL language itself is really pretty succinct and limited enough that you should be able to minimize the need for more expensive interactions for most usage.

Adjacent would suggest supporting a migrations project structure, similar to say grate or similar tooling in order to facilitate db "projects" associated against a db instance.  Not to be MS centric, I just find the tooling around MS-SQL and Grate to be relatively nice to work with compared to others.  My DB preference is PostgreSQL though.

For those curious, you can find the source of the website here...

https://github.com/pakastin/pakastin

Really need for Safari to adopt this feature for it to be broadly applicable.  You should be able to use it now for server-side code environments like current versions of Node and Deno, looks like Bun doesn't have it yet..

It's a feature I really appreciate in C#, especially since you don't need to wrap into a closure anymore, it just inherits the containing closure, like JS/TS implementation.

https://caniuse.com/mdn-javascript_statements_await_using

Just a relatively quick/small image viewer module that will display an image(url) via a full-screen overlay.  Injects and cleans up after itself in the DOM.

Not quite vibe-coded, I wish I'd saved my Claude Code log... it kept trying to make things much, much, more complex with CSS transforms and was about 2x the size.  Final result is under 700 lines of JS, with CSS embedded.

Mostly a quick and dirty component module I needed for work that I thought I'd share.  Aside, publishing ton NPM from Github Action was kind of a pain... need to force the latest npm install and clear the auth token when running publish.  Also, need to set npm to the parent task/workflow not the sub-workflow I had it defined in.

Another point of fun continues to be getting AI, Deno and Vite working together without AI trying to revert to node/npm and other issues.  Mostly int he testing/demo app.

The module itself took about 90 minutes with a lot of back and forth on zoom behavior/implementation.  Getting the publishing working took about as long figuring out why the OICD or whatever it's called isn't working.  I wish that NPM's blog post about removing their old token style would add a link to a step by step article on setting up under Githuub/Gitlab, including the auth bug with the current actions to configure Node.  I finally found an article that did outline things, and even then, my parent/sub-workflow was still kind of an issue, which feels weird... I think the deno config was much smoother... jsr publish worked second try (I had a typo in my repo name).

[AI] is for both tooling around AI usage or build with/using AI whole or in part.  It's not a value judgement, just a tag.

FWIW: I think it looks cool and upvoted.

Didn't verify either way, it specifically mentioned iOS and not Android... so just took it as is.

The dashboard itself looks cool.. I like TUI options myself, that said a lot of the crowd here are not into a lot of posts surrounding financial markets, in particular crypto or for that matter AI content, though I've relaxed a little and will just [AI] tag posts for AI generated tools/projects so long as they aren't generic "clone of X" type things.

LOL @ my using [Ask HN] instead of [Ask EchoJS] ... sorry, fixed.

Updated title to match non-marketing segment in project description and tagged [AI] as the project is almost definitely using an AI code assist tool.