Release abstract-level and dependents

[vweevers]

• Add to FAQ: how do I upgrade to abstract-level? community#109
• abstract-level (replacement for abstract-leveldown and more)
  • 1.0.0
• memory-level (replacement for memdown and level-mem)
  • Create repository
  • Replace links to level-mem and memdown in Level/community
  • 1.0.0
• level-read-stream
  • Use nextv() and decide on default hwm read-stream#1 (needs memory-level for tests)
  • Bump engines.node in package.json
  • 1.0.1
• classic-level (replacement for leveldown)
  • Create repository
  • Figure out how nextv() and _landed logic should interact
  • Replace links to leveldown in Level/community
  • Breaking: rename highWaterMark to highWaterMarkBytes classic-level#1
  • Write guide for upgrading from leveldown classic-level#3
  • Breaking: bump Python from 2.x to 3.x (#15) prebuild/docker-images#23
  • Bump Python to 3 and drop Node.js < 12 prebuild/prebuildify-cross#12
  • 1.0.0
• browser-level (replacement for level-js)
  • Create repository
  • Replace links to level-js in Level/community
  • 1.0.0
• level
  • Optionally Create location directory recursively classic-level#6
  • Breaking: switch to classic-level and browser-level level#215
  • 8.0.0
• rocks-level (replacement for rocksdb and level-rocksdb)
  • Create repository
  • Diff against leveldown, copy classic-level, apply diff
  • 1.0.0
• many-level (replacement for multileveldown)
  • Document error codes of classic-level and many-level #20
  • Add hidden abortOnClose option to iterators #21
  • 1.0.0
• rave-level (replacement for level-party, depends on level@8)
  • Yield LEVEL_LOCKED error when lock is held classic-level#8
  • 1.0.0

Side tasks:

• Add npm owners (also to level-web-stream)
• Level/webpack-starter@c6db89d
• Level/browserify-starter@2afa2c0
• Level/level-ws@94a2a8e

[vweevers]

rave-level is shaping up, iterating (as a follower) at twice the speed of level-party, bringing it closer to classic-level:

Click to expand

[vweevers]

Published many-level.

[ronag]

@vweevers any indication on many-level vs local redis perf?

[vweevers]

Depends on what functionality you need. Without iterators, simple GET and SET commands suffice and can easily be benchmarked against Level modules. For iterators, you need hashes and/or sorted sets, or perhaps Redis Streams which I'm not familiar with, but either way the performance characteristics will be different. Buffer support will slow it down. Etc.

[vweevers]

I got side tracked by a Node.js bug on Windows (nodejs/node#42496) but that seems to be an edge case so I went ahead and published rave-level.