natural-selection VS pg-mem

Maybe https://github.com/frontaid/natural-selection can give you some pointers. It is a blueprint of a possible CSS file structure that applies globally. This covers at least 1. and 2. of your example.

[1] https://github.com/frontaid/natural-selection

PS: If you want to get a jump start for the global styling of your projects, you might want to have a look at https://github.com/frontaid/natural-selection

I rarely use any of the popular CSS frameworks. Unless you are making a small(ish) website where the styling is not important, it is actually more work to change an existing frameworks than to just use CSS yourself.

But what I do use sometimes is a CSS reset like https://github.com/necolas/normalize.css

And what I also use is this CSS boilerplate: https://github.com/frontaid/natural-selection (Disclaimer: I created it because I wanted to avoid the repetitive work of writing out all the selectors).

I'm working on a CSS framework without any styling (!). It is a collection of selectors and meant to be used as a clean CSS boilerplate. Thus it can jump start your your next project or design system.

https://github.com/frontaid/natural-selection

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)