Vincent Weevers

@ronag The leveldown-as-a-base strategy has worked well for several years on `rocksdb` and is the only reason I've been willing to maintain `rocksdb` (ignoring my current hiatus). The many changes...

To clarify: I do _not_ want to start using Discord or Slack or any other secondary platform. GitHub all the way.

I'll look into ways of getting browser code coverage (with airtap). Would be really nice if each sauce labs job is displayed in coveralls (in addition to Travis jobs for...

> Would be really nice if each sauce labs job is displayed in coveralls (in addition to Travis jobs for node tests). Scratch that, I forgot about the plan to...

`encoding-down` down :)

There's a few ways to go about this: 1. Take an existing `abstract-leveldown` implementation and follow the [upgrade guide of `abstract-level`](https://github.com/Level/abstract-level/blob/main/UPGRADING.md). See also the [FAQ](https://github.com/Level/community#how-do-i-upgrade-to-abstract-level). 2. Start from scratch and...

This is by design, but [changing](https://github.com/Level/abstract-level/blob/main/UPGRADING.md) in `abstract-level` 2.0.0. Until then, do: ```js try { await db.get('example') } catch (err) { if (err.code === 'LEVEL_NOT_FOUND') { console.log('Not found') } }...

Until more folks express the need for this feature (give it a thumbs up if you do) this can be implemented in userland. Similar to [`level-exists`](https://github.com/juliangruber/level-exists) but optimized to use...

Re: keys vs values, see also https://github.com/Level/abstract-leveldown/issues/380 which proposes key-only and value-only iterators.

I can answer question 1: in the past, iterators weren't directly exposed (and async iterators weren't a thing) - level was all about streams