EJDB (Embedded JSON Database) is a lightweight, embedded NoSQL database engine for Node.js, providing a MongoDB-like query language for local JSON document storage. The `ejdb` npm package specifically provides the Node.js bindings for the first generation EJDB engine. This version, `1.2.12-44`, is stable but officially discontinued and has not been updated in over seven years. The project has entirely transitioned to its successor, `ejdb2_node`, which is a complete rewrite. Users should migrate to `ejdb2_node` for active development, maintenance, and new features, including security updates. EJDB v1.x was designed for Node.js versions >=4.0.0 and focused on providing fast, self-contained, file-based JSON document storage with indexing, without requiring a separate server process. Its release cadence was sporadic, with its last publish seven years ago. Its key differentiator was being a high-performance embedded JSON store suitable for small to medium-scale applications where a full-fledged database server was considered overkill.
npm install ejdbVerified import paths — ran on the pinned version, not inferred.
Demonstrates how to initialize EJDB, open a database file, insert a JSON document, and query for data using a MongoDB-like syntax.
Migrate your application to use the `ejdb2_node` package (https://www.npmjs.com/package/ejdb2_node). This will involve code changes as EJDB2 is a complete rewrite.
Ensure you have the necessary build tools installed for `node-gyp` (e.g., Python 2.7, Visual C++ Build Tools on Windows, `build-essential` on Linux). However, due to deprecation, migration to `ejdb2_node` is the recommended long-term solution, as some versions of `ejdb2_node` offer pre-compiled binaries.
Expeditiously migrate to the `ejdb2_node` package, which is actively maintained and supported by the developers.
Install `node-gyp` prerequisites (e.g., `npm install -g node-gyp`, then follow its setup instructions for your OS). For long-term stability, migrate to `ejdb2_node`.
Change your file to use CommonJS (`.js` file without `type: "module"`) or refactor your project to use `ejdb2_node` which may offer better ESM compatibility.
Run `npm install ejdb` again. Check the console output for `node-gyp` errors. If errors persist, ensure build tools are configured or consider migrating to `ejdb2_node`.
No dependency data recorded yet.