level / mem

A convenience package bundling levelup and memdown.

level-mem

A convenience package that bundles levelup, encoding-down and memdown and exposes levelup on its export.

📌 This module will soon be deprecated, because it is superseded by memory-level.

Usage

Use this package to avoid having to explicitly install memdown when you want to use memdown with levelup for non-persistent levelup data storage.

const level = require('level-mem')

// Create our in-memory database
const db = level()

// Put a key & value
await db.put('name', 'Level')

// Get value by key
const value = await db.get('name')
console.log(value)

See levelup and memdown for more details.

If you are upgrading: please see UPGRADING.md.

Contributing

Level/mem is an OPEN Open Source Project. This means that:

Individuals making significant and valuable contributions are given commit-access to the project to contribute as they see fit. This project is more like an open wiki than a standard guarded open source project.

See the Contribution Guide for more details.

Donate

Support us with a monthly donation on Open Collective and help us continue our work.

License

MIT

mem's Issues

switch to plain MIT

Release 3.0.0

Dependent on

• Level/packager#53
• Level/memdown#157

An in-range update of tape is breaking the build 🚨

Version 4.9.1 of tape was just published.

Branch	Build failing 🚨
Dependency	tape
Current Version	4.9.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

tape is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

Commits

The new version differs by 10 commits.

• 050b318 v4.9.1
• 73232c0 [Dev Deps] update js-yaml
• 8a2d29b [Deps] update has, for-each, resolve, object-inspect
• c6f5313 [Tests] add eclint and eslint, to enforce a consistent style
• 45788a5 [Dev Deps] update concat-stream
• ec4a71d [fix] Fix bug in functionName regex during stack parsing
• 7261ccc Merge pull request #433 from mcnuttandrew/add-trb
• 6cbc53e Add tap-react-browser
• 9d501ff [Dev Deps] use ~ for dev deps; update to latest nonbreaking
• 24e0a8d Fix spelling of "parameterize"

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

release new major version

@rvagg Mind adding me as owner on npm?

Drop node 4

release v2

destroy/repair?

perhaps level-mem's destroy/repair should be "successful" noops so this can be a happy one-for-one level replacement? i.e. disable the skipDestroyTest skipRepairTest flags?

Update packager and memdown

• Update memdown (once v2 is out)
• Update packager
• Add node version badge etc
• Drop 0.12
• Fix badges

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml
• The new Node.js version is in-range for the engines in 1 of your package.json files, so that was left alone

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

• engines was only updated if it defined a single version, not a range.
• .nvmrc was updated to Node.js 10
• .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

rename repository to Level/mem

shall we do this?

Remove "location" from readme example

An in-range update of memdown is breaking the build 🚨

Version 1.2.5 of memdown just got published.

Branch	Build failing 🚨
Dependency	memdown
Current Version	1.2.4
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

memdown is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Commits

The new version differs by 8 commits.

• 1abc47b 1.2.5
• 90e51b1 Merge pull request #69 from Level/greenkeeper/initial
• f0b4b76 split up zuul on multiple matrix entries for each browser + test on latest only
• 2610905 :arrow_up: bump abstract-leveldown
• b9eb981 Update README.md
• 9131113 docs(readme): add Greenkeeper badge
• fb4a9cb chore(travis): whitelist greenkeeper branches
• fe61dcd chore(package): update dependencies

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Release v3.0.1

Add standard (and remove .jshintrc)

add CHANGELOG