lmdb - npm Package Compare versions

Comparing version 2.7.3 to 2.7.4

dependencies/lmdb/libraries/liblmdb/midl-sparse.c

index.d.cts

package.json

		{
		"name": "lmdb",
		"author": "Kris Zyp",
		"version": "2.7.3",
		"version": "2.7.4",
		"description": "Simple, efficient, scalable, high-performance LMDB interface",
		@@ -46,2 +46,3 @@ "license": "MIT",
		"index.d.ts",
		"index.d.cts",
		"/*.ts",
		@@ -108,9 +109,9 @@ "/*.gyp",
		"optionalDependencies": {
		"@lmdb/lmdb-darwin-arm64": "2.7.2",
		"@lmdb/lmdb-darwin-x64": "2.7.2",
		"@lmdb/lmdb-linux-arm": "2.7.2",
		"@lmdb/lmdb-linux-arm64": "2.7.2",
		"@lmdb/lmdb-linux-x64": "2.7.2",
		"@lmdb/lmdb-win32-x64": "2.7.2"
		"@lmdb/lmdb-darwin-arm64": "2.7.4",
		"@lmdb/lmdb-darwin-x64": "2.7.4",
		"@lmdb/lmdb-linux-arm": "2.7.4",
		"@lmdb/lmdb-linux-arm64": "2.7.4",
		"@lmdb/lmdb-linux-x64": "2.7.4",
		"@lmdb/lmdb-win32-x64": "2.7.4"
		}
		}

README.md

		@@ -106,2 +106,4 @@ [![license](https://img.shields.io/badge/license-MIT-brightgreen)](LICENSE)

		By default, the maximum key size is 1978 bytes. If you explicitly set the `pageSize` to 8192 or higher, the maximum key size will be 4026, but this is the largest key size supported.

		You can override the default encoding of keys, and cause keys to be returned as binary arrays (`Buffer`s in NodeJS) using the `keyEncoding: 'binary'` database option (generally slower). Use `keyEncoding: 'uint32'` for keys that are strictly 32-bit unsigned integers, or provide a custom key encoder/decoder with `keyEncoder` (see custom key encoding).
		@@ -108,0 +110,0 @@

src/env.cpp

Sorry, the diff of this file is not supported yet

New alerts