v0.6.1 Enhancements

[alex996]

• build for node (cjs), bundlers like webpack (esm), and browser (umd)
• separate FS and memory DBs into /lib/fs and lib/mem dirs
  • this way we bypass node-only code in rollup and avoid warnings like below (resulting from the output format being umd)
    
• add DB helpers with a proxy
• add examples of use

Breakdown of the current build folder:

/build
  /cli # Executable files in CommonJS
    cmds
    jsongo-cli.js
  /esm # Same as /lib but in ES Modules
    fs
    mem
    shared
    index.js
  /lib # Entrypoint in CommonJS
    fs
    mem
    shared
    index.js
  jsongo.min.js # UMD bundle

Breakdown of the fields in package.json:

• "bin" - when you run jsongo CLI, it resolves to /build/cli
• "main" - when you require("jsongo") in Node, it resolves to /build/lib
• "module" - when you import jsongo with a front-end bundler (e.g. webpack), it resolves to /build/esm
• "unpkg" - when you load jsongo from a CDN, it serves up /build/jsongo.min.js

[alex996]

Ran into circular errors in rollup saying that only one of output.dir or output.file is permitted in rollup.config.js, while at the same time output.dir is required when "ourDir" is specified in tsconfig.json. Solved by removing "outDir" entirely; it gets populated in tsconfig.build.json instead.