idb VS lets-play-bitburner

From this github issue and pr it seems to be a limitation with how union works in TypeScript.

I've worked on a core async app that used indexeddb heavily, but instead of using the indexeddb apis directly I used https://github.com/jakearchibald/idb for a the promise API. Worked well.

I use IndexedDB, specifically the idb library (https://github.com/jakearchibald/idb), or Dexie.js (https://dexie.org/) if you are more novice. This works great for large sets of data. For smaller amounts, Chrome Storage API will do.

This was also the library I landed on: Github link

I had good luck using IDB ( https://github.com/jakearchibald/idb ) It makes using IndexedDB easy.

That entire chunk of code is copied from a library https://github.com/jakearchibald/idb

So that kind of ends this simple setup. It's incredible how little help you're able to find online regarding all of this, so hopefully this will help myself in the future, and maybe some lost soul will stumble upon it as well. There's loads of other features that can be used, but I won't get into that right now. You can find more examples on Jake Archibald's library readme: https://github.com/jakearchibald/idb

I've had good experiences with

https://github.com/jakearchibald/idb

It's basically a promise-based version of the standard API.

Here is link number 1 - Previous text "idb"

So I grabbed the go.js from the EP4 branch (https://github.com/trhr/lets-play-bitburner/blob/ep4/go.js) and pasted that in. Ran it, got an error anyhow!