Release node-idb 0.2.0 - #5
Merged
Merged
Conversation
kbaghini
marked this pull request as ready for review
July 21, 2026 11:58
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
0.2.0Core API with canonical statements, explicit lifecycle, read-only mode, backups, restore and inspection tools, streaming, cancellation, diagnostics, collection caching, and adaptive indexesnode-idbpackageWhy
This release replaces project arguments and implicit database creation with explicit database instances, strengthens reliability and operational controls, and provides a safe local UI for browsing, querying, structure inspection, diagnostics, and explicitly enabled maintenance.
User impact
This is a breaking
0.2release. Existing storage can be opened in place, but applications must create an instance withcreateIdb({ storagePath }), remove project arguments, and use the canonical statement spellings documented in the migration guide. Core remains available fromnode-idb; Studio is included atnode-idb/studiowith no second package.Validation
npm cinpm test: 141/141 runtime tests plus TypeScript contract checksnpm audit --omit=dev: zero vulnerabilitiesnpm run pack:check: 52 expected filesnpm publish --dry-run --access publicgit diff --check