Echo JS 0.11.0

TLDR; use fetch api. (Node 18+ or node-fetch, Deno, Browser)

https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API

Generally, not a huge fan of templates for node, this is far more ready than most.  One change I would suggest is adding a test coverage requirement to the jest config, then maybe adding git action(s) preventing merge for PRs that don't meet the coverage requirement, and maybe another upping the coverage config to the new level when it's raised.

This is *NOT* EchoGolang... it's EchoJS.

As a carnivore, I find the messaging offensive.

Don't mind the abstraction over Redux too offensive, though one might consider making this (or something similar) work along with redux-micro-frontend [1].

1. https://www.npmjs.com/package/redux-micro-frontend

@fkereki, I didn't downvote this one... but please keep the posts on this site related to JavaScript... the high level (no code) articles like the one on "front end testing" that was just removed are off topic.

Commercial licensed product without clear licensing.

I usually have a default api root path... defaulted to /api... then I proxy /api in my dev host to my ui api instance... on deployed serviers/services, it's similar, where the load balancer will reroute the /api base path... or /api/v1.0.0/ etc in larger apps.

Often creating a tightly coupled api service for the UI, separated from any data services behind that.

I also set it to look for globalThis.__API_BASE__ that can be injected into *.html at build or deploy for other environments where a reverse-proxy is either a bad idea (S3, etc).

Beyond this, when the loading takes more than a second, I'll have the default html (especially in SPA) render a loader div along with the css for that loader... This renders the first part quickly, while being able to run updates as other pieces dynamically load in the beginning.  /api/v.../features as an example, that is feature flags and config options that will inform other loaded items... dynamically loaded components, for example.

I think the biggest issues with form components is the styling to integrate modern toolkits.  I really like bootstrap, I also like mui, and that's about all I really like as far as web based components.

Beyond this, just checked, seems like every browser in wide use now supports WebComponents, which is very cool.  May have to start playing with it again.  Previously, the shims needed were just crazy huge to say the least.  Not too fond of many smaller downloads, but would be cool to create something modern-like without too many external libraries.

Really appreciate seeing that this only depends on individual D3 libraries as opposed to a closed source, or otherwise commercial library.

Would *REALLY* prefer to see an actual instruction writeup of the content in addition to, or even instead of the Video.  When looking for answers for stuff like this, you don't always want to sit for a video for something that could be mostly copy-paste from an actual article.