forgo VS pg-mem

ForgoJS: a 4KB React alternative that gets rid of framework specific DOM access techniques and state management. For example: let people use closures for managing component state rather than something new like hooks.

Here's a preview: https://github.com/forgojs/forgo

I'll do a Show HN once it's ready.

I've used pgmem https://github.com/oguimbal/pg-mem for the last couple of years for the same thing.

I was wondering the other day how to classify tests that use a test double like pg-mem, which isn't a mock but isn't the Dockerized test DB either :

https://github.com/oguimbal/pg-mem

In my case, I use TypeORM with PostgreSQL, and there's pg-mem to run an instance in memory, it supports most of the common functionality of PostgreSQL but you will need to do some adjustment to your code to be within the limits.

Postgres in the browser is possible through pg-mem: "pg-mem is an experimental in-memory emulation of a postgres database" but it also suffers from no persistence. If you can persist to a file somewhere then read it in on startup (and if your local data isn't huge) this might work.

Dont get me wrong: I am trying to contribute to opensource as well, so I get that supporting small projects can be demanding. There's nothing wrong in not spending your weekends on OS. But not asking for help, nor specifying that a project is unmaintained, nor even answering issues & pull requests for years feels just wrong.

A pure Javascript in memory emulation of Posgres, to help writing better node tests https://github.com/oguimbal/pg-mem

Okay, I had a bit of spare time,I've implemented that, and it is now available with [email protected]

To get a glimpse of what I'm talking about, you can clone this repo and follow "Development" instructions (by the way this is a small OS lib I maintain, I wrote about it here)