Echo JS 0.11.0

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.

I don't think that the in the box options currently support that either.  Possibly with Temporal[1]

1. https://github.com/tc39/proposal-temporal

the polyfill.io call in src seems redundant as the use of import itself means that the other methods in the polyfill would already be there.

Only mentioned at the end, but definitely favor the work on Intl and related bits over libraries where available.

I think actually running tests would be more appropriate than simply making declarations.  SQLite's locking mechanism will synchronize a lot of activity anyway.

What you probably should do, if there's lots of other things going on, if you're using SQLite with Node.js, is segment your database requests into a separate worker.  This is going to be regardless of the SQL library you choose.

Beyond this, I'm not a fan of ORMs in scripted languages anyway.  It adds a lot of overhead for almost no real value.

Been playing with this for a while.  I setup a github project that will build via Lume and publish to Cloudfare Pages in about an hour.  The setup is relatively easy, I'd say it's a bit nicer than Jekyll and others I've tried.

Cool... Was considering ways to handle image positioning for my own blog setup.  Started playing with Lume a couple months ago, but didn't get much further than setting up some test entries and the generate/publish scripts.

I'm using Lume and publishing to a cloudflare pages site, which works pretty well.  Client-side search is interesting, inherited from the template I started with.  Will probably add MDX support for an Image component I can use for image positioning...

    <Image type={(left|right|full|expanded)} src={...} />

...type of thing.. basically want to handle either left/right or full, or expanded beyond text region.

Looks like I should be able to do this.

I'm really torn on removing this... it's OT (Python not JS based), but really interesting.  Thoughts?

When yarn started, it really was a performance improvement over npm at the time... but npm has gotten (much) better... I think it's just best to generally stick with npm, though the past couple jobs I've been at they were using yarn.