This document describes breaking changes and how to upgrade. For a complete list of changes including minor and patch releases, please refer to the changelog.
Legacy range options have been removed (Level/community#86). If you previously did:
db.createReadStream({ start: 'a', end: 'z' })An error would now be thrown and you must instead do:
db.createReadStream({ gte: 'a', lte: 'z' })The same applies to db.iterator(), db.createKeyStream() and db.createValueStream().
This release also drops support of legacy runtime environments (Level/community#98):
- Node.js 6 and 8
- Internet Explorer 11
- Safari 9-11
- Stock Android browser (AOSP).
Lastly, in browsers, the immediate shim for process.nextTick() has been replaced with queue-microtask, except in streams.
Upgraded to [email protected]:
Support of keys & values other than strings and Buffers has been dropped. Internally
memdownnow stores keys & values as Buffers which solves a number of compatibility issues (Level/memdown#186). If you pass in a key or value that isn't a string or Buffer, it will be irreversibly stringified.
Upgraded to [email protected] and (through level-packager@5) levelup@4 and encoding-down@6. Please follow these links for more information. A quick summary: range options (e.g. gt) are now serialized the same as keys, { gt: undefined } is not the same as {}, nullish values are now rejected and streams are backed by readable-stream@3.
Support of IE10 and node 9 has been dropped.
Dropped support for node 4. No other breaking changes.