Security News
RubyGems.org Adds New Maintainer Role
RubyGems.org has added a new "maintainer" role that allows for publishing new versions of gems. This new permission type is aimed at improving security for gem owners and the service overall.
See API docs at docs.holepunch.to
An append-only B-tree running on a Hypercore. Allows sorted iteration and more.
npm install hyperbee
const Hyperbee = require('hyperbee')
const db = new Hyperbee(feed, {
keyEncoding: 'utf-8', // can be set to undefined (binary), utf-8, ascii or and abstract-encoding
valueEncoding: 'binary' // same options as above
})
// if you own the feed
await db.put('key', 'value')
await db.del('some-key')
// if you want to insert/delete batched values
const batch = db.batch()
await batch.put('key', 'value')
await batch.del('some-key')
await batch.flush() // execute the batch
// if you want to query the feed
const node = await db.get('key') // null or { key, value }
// if you want to read a range
const rs = db.createReadStream({ gt: 'a', lt: 'd' }) // anything >a and <d
const rs = db.createReadStream({ gte: 'a', lte: 'd' }) // anything >=a and <=d
// get the last written entry
const rs = db.createHistoryStream({ reverse: true, limit: 1 })
Some of the internals are still being tweaked, but overall the API and feature set is pretty stable, if you want to try it out.
All of the above methods work with sparse feeds, meaning only a small subset of the full feed is downloaded to satisfy your queries.
const db = new Hyperbee(feed, [options])
Make a new Hyperbee instance. feed
should be a Hypercore.
Options include:
{
keyEncoding: 'utf-8' | 'binary' | 'ascii', // or some abstract encoding
valueEncoding: <same as above>
}
Note that currently read/diff streams sort based on the encoded value of the keys.
await db.put(key, [value], [options])
Insert a new key. Value can be optional. If you are inserting a series of data atomically, or you just have a batch of inserts/deletions available using a batch can be much faster than simply using a series of puts/dels on the db.
Options include:
{
cas (prev, next) { return true }
}
You have the option to pass a cas
function as an option to put
that controls whether the put
succeeds. Given bee.put(key, value, { cas })
, cas
is passed the current node (i.e. { seq, key, value }
) in bee
at key
and the next tentative node. Then put
succeeds only if cas
returns true
and fails otherwise.
const cas = (prev, next) => prev.value !== next.value
const db = new Hyperbee(feed, { keyEncoding: 'utf8', valueEncoding: 'utf8' })
await db.put('key', 'value')
console.log(await db.get('key')) // { seq: 1, key: 'key', value: 'value' }
await db.put('key', 'value', { cas })
console.log(await db.get('key')) // { seq: 1, key: 'key', value: 'value' }
await db.put('key', 'value*', { cas })
console.log(await db.get('key')) // { seq: 2, key: 'key', value: 'value*' }
{ seq, key, value } = await db.get(key)
Get a key, value. If the key does not exist, null
is returned.
seq
is the hypercore version at which this key was inserted.
await db.del(key, [options])
Delete a key
Options include:
{
cas (prev, next) { return true }
}
You can pass a cas
function as an option to del
that controls whether the del
succeeds. Given bee.del(key, { cas })
, cas
is passed the current node (i.e. { seq, key, value }
) in bee
at key
, and del
succeeds only if cas
returns true
and fails otherwise.
const cas = (prev) => prev.value === 'value*'
const db = new Hyperbee(feed, { keyEncoding: 'utf8', valueEncoding: 'utf8' })
await db.put('key', 'value')
console.log(await db.get('key')) // { seq: 1, key: 'key', value: 'value' }
await db.del('key', { cas })
console.log(await db.get('key')) // { seq: 1, key: 'key', value: 'value' }
await db.put('key', 'value*')
console.log(await db.get('key')) // { seq: 2, key: 'key', value: 'value*' }
await db.del('key', { cas })
console.log(await db.get('key')) // null
batch = db.batch()
Make a new batch.
await batch.put(key, [value], [options])
Insert a key into a batch.
Options include:
{
cas (prev, next) { return true } // see await db.put(key, value, { cas })
}
{ seq, key, value } = await batch.get(key)
Get a key, value out of a batch.
await batch.del(key, [options])
Delete a key into the batch.
Options include:
{
cas (prev, next) { return true } // see await db.del(key, { cas })
}
await batch.flush()
Commit the batch to the database.
batch.destroy()
Destroy a batch and releases any locks it has aquired on the db. Call this if you want to abort a batch without flushing it.
stream = db.createReadStream([options])
Make a read stream. All entries in the stream are similar to the ones returned from .get and the sort order is based on the binary value of the keys.
Options include:
{
gt: 'only return keys > than this',
gte: 'only return keys >= than this',
lt: 'only return keys < than this',
lte: 'only return keys <= than this',
reverse: false // set to true to get them in reverse order,
limit: -1 // set to the max number of entries you want
}
const { seq, key, value } = await db.peek([options])
Similar to doing a read stream and returning the first value, but a bit faster than that.
stream = db.createHistoryStream([options])
Create a stream of all entries ever inserted or deleted from the db.
Each entry has an additional type
property indicating if it was a put
or del
operation.
Options include:
{
live: false, // if true the stream will wait for new data and never end
reverse: false, // if true get from the newest to the oldest
gte: seq, // start with this seq (inclusive)
gt: seq, // start after this index
lte: seq, // stop after this index
lt: seq, // stop before this index
limit: -1 // set to the max number of entries you want
}
If any of the gte, gt, lte, lt arguments are < 0
then
they'll implicitly be added with the version before starting so
doing { gte: -1 }
makes a stream starting at the last index.
stream = db.createDiffStream(otherVersion, [options])
Efficiently create a stream of the shallow changes between two versions of the db. Each entry is sorted by key and looks like this:
{
left: <the entry in the db>,
right: <the entry in the other version>
}
If an entry exists in db but not in the other version, then left
is set
and right
will be null, and vice versa.
If the entries are causally equal (i.e. the have the same seq), they are not returned, only the diff.
Currently accepts the same options as the read stream except for reverse.
dbCheckout = db.checkout(version)
Get a readonly db checkout of a previous version.
dbCheckout = db.snapshot()
Shorthand for getting a checkout for the current version.
const sub = db.sub('sub-prefix', opts = {})
Create a sub-database where all entries will be prefixed by a given value.
This makes it easy to create namespaces within a single Hyperbee.
Options include:
{
sep: Buffer.alloc(1), // A namespace separator
valueEncoding, // optional sub valueEncoding (defaults to the parents)
keyEncoding // optional sub keyEncoding (defaults to the parents)
}
For example:
const rootDb = new Hyperbee(core)
const subDb = rootDb.sub('a')
// In rootDb, this will have the key ('a' + separator + 'b')
await subDb.put('b', 'hello')
// Returns { key: 'b', value: 'hello')
await subDb.get('b')
db.version
Current version.
await db.ready()
Makes sure internal state is loaded. Call this once before checking the version if you haven't called any of the other APIs.
await Hyperbee.isHyperbee(core, opts?)
Returns true if the core contains a hyperbee, false otherwise.
Queries the core, so ensure it is available and has updated length before calling this.
FAQs
An append-only B-tree running on a Hypercore.
The npm package hyperbee receives a total of 517 weekly downloads. As such, hyperbee popularity was classified as not popular.
We found that hyperbee demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
RubyGems.org has added a new "maintainer" role that allows for publishing new versions of gems. This new permission type is aimed at improving security for gem owners and the service overall.
Security News
Node.js will be enforcing stricter semver-major PR policies a month before major releases to enhance stability and ensure reliable release candidates.
Security News
Research
Socket's threat research team has detected five malicious npm packages targeting Roblox developers, deploying malware to steal credentials and personal data.