hjson-js VS Lowdb

By the way.. if you use the hjson parser you can add comments to json files :) https://hjson.github.io/

I wish this took off https://hjson.github.io. I like it much more than yaml.

I don't know anything about VueJS either but HJSON is pretty cool in that regard https://hjson.github.io/

> Another difficult problem was checking for correct indentation visually (because the configuration is YAML-based and indentation matters).

why yaml? I hate it so much! my eyes hurt looking at it?

why not using https://hjson.github.io/ ?

HJSON [0] is also another format that tries to make it easier for humans to read / write json.

[0] https://hjson.github.io/

well there are json alternatives which fit this bill, such as HJSON.

https://hjson.github.io/

might not be as "common" but it has good implementations for many languages.

zdpack also pre-processes datapacks, allowing json files to be written in hjson or yaml, in addition to allowing a special extensible super-set of MCFunction I call CommandScript. You can check the github page for a quick overview of CommandScript.

https://github.com/typicode/lowdb is a cool option.

I just finished the first stable version of go-store, a lightweight embeeded database written in pure Go. It was heavily inspired by lowdb. The motivation was that I needed something simple to store information for another project and that I wanted to try out Go's generics.

https://jsondb.io/ or https://github.com/typicode/lowdb

By default, requests are stored locally in a JSON file with the help of LowDB.

For 1: Don't.* For 2: You're looking for a cache. I've published an OS npm module. Looking at the code might help: https://github.com/tq-bit/qache/blob/master/src/Cache.ts For 3: Maybe the code of lowdb can point you in the right direction: https://github.com/typicode/lowdb/tree/main/src

Another thing you might consider is literally using the filesystem as a database. There are plenty of vanillla ways to simply read/write to JSON or you could even use a JSON based db github.com/typicode/lowdb again you don't need to think about it as a db your just handling JS objects.

I did want something performant so that I would (hopefully) not run into issues when there are around 100-ish clients connected at the same time. I looked at low-db for a while but did not like that it would JSON.stringify my whole database on every change, which could become a problem when it becomes to big.