A small wrapper that makes IndexedDB usable
npm install @tempfix/idbThis is a tiny (~1.19kB brotli'd) library that mostly mirrors the IndexedDB API, but with small improvements that make a big difference to usability.
1. Installation
1. Changes
1. Browser support
1. API
1. openDB
1. deleteDB
1. unwrap
1. wrap
1. General enhancements
1. IDBDatabase enhancements
1. IDBTransaction enhancements
1. IDBCursor enhancements
1. Async iterators
1. Examples
1. TypeScript
``sh`
npm install idb
Then, assuming you're using a module-compatible system (like webpack, Rollup etc):
`js
import { openDB, deleteDB, wrap, unwrap } from 'idb';
async function doDatabaseStuff() {
const db = await openDB(…);
}
`
`html`
`html`
A global, idb, will be created, containing all exports of the module version.
See details of (potentially) breaking changes.
This library targets modern browsers, as in Chrome, Firefox, Safari, and other browsers that use those engines, such as Edge. IE is not supported.
This method opens a database, and returns a promise for an enhanced IDBDatabase.
`js`
const db = await openDB(name, version, {
upgrade(db, oldVersion, newVersion, transaction, event) {
// …
},
blocked(currentVersion, blockedVersion, event) {
// …
},
blocking(currentVersion, blockedVersion, event) {
// …
},
terminated() {
// …
},
});
- name: Name of the database.version
- (optional): Schema version, or undefined to open the current version.upgrade
- (optional): Called if this version of the database has never been opened before. Use it to specify the schema for the database. This is similar to the upgradeneeded event in plain IndexedDB.db
- : An enhanced IDBDatabase.oldVersion
- : Last version of the database opened by the user.newVersion
- : Whatever new version you provided.transaction
- : An enhanced transaction for this upgrade. This is useful if you need to get data from other stores as part of a migration.event
- : The event object for the associated upgradeneeded event.blocked
- (optional): Called if there are older versions of the database open on the origin, so this version cannot open. This is similar to the blocked event in plain IndexedDB.currentVersion
- : Version of the database that's blocking this one.blockedVersion
- : The version of the database being blocked (whatever version you provided to openDB).event
- : The event object for the associated blocked event.blocking
- (optional): Called if this connection is blocking a future version of the database from opening. This is similar to the versionchange event in plain IndexedDB.currentVersion
- : Version of the open database (whatever version you provided to openDB).blockedVersion
- : The version of the database that's being blocked.event
- : The event object for the associated versionchange event.terminated
- (optional): Called if the browser abnormally terminates the connection, but not on regular closures like calling db.close(). This is similar to the close event in plain IndexedDB.
Deletes a database.
`js`
await deleteDB(name, {
blocked() {
// …
},
});
- name: Name of the database.blocked
- (optional): Called if the database already exists and there are open connections that don’t close in response to a versionchange event, the request will be blocked until they all close.currentVersion
- : Version of the database that's blocking the delete operation.event
- : The event object for the associated 'versionchange' event.
Takes an enhanced IndexedDB object and returns the plain unmodified one.
`js`
const unwrapped = unwrap(wrapped);
This is useful if, for some reason, you want to drop back into plain IndexedDB. Promises will also be converted back into IDBRequest objects.
Takes an IDB object and returns a version enhanced by this library.
`js`
const wrapped = wrap(unwrapped);
This is useful if some third party code gives you an IDBDatabase object and you want it to have the features of this library.
Once you've opened the database the API is the same as IndexedDB, except for a few changes to make things easier.
Firstly, any method that usually returns an IDBRequest object will now return a promise for the result.
`js`
const store = db.transaction(storeName).objectStore(storeName);
const value = await store.get(key);
The library turns all IDBRequest objects into promises, but it doesn't know in advance which methods may return promises.
As a result, methods such as store.put may throw instead of returning a promise.
If you're using async functions, there's no observable difference.
TL;DR: Do not await other things between the start and end of your transaction, otherwise the transaction will close before you're done.
An IDB transaction auto-closes if it doesn't have anything left do once microtasks have been processed. As a result, this works fine:
`js`
const tx = db.transaction('keyval', 'readwrite');
const store = tx.objectStore('keyval');
const val = (await store.get('counter')) || 0;
await store.put(val + 1, 'counter');
await tx.done;
But this doesn't:
`js`
const tx = db.transaction('keyval', 'readwrite');
const store = tx.objectStore('keyval');
const val = (await store.get('counter')) || 0;
// This is where things go wrong:
const newVal = await fetch('/increment?val=' + val);
// And this throws an error:
await store.put(newVal, 'counter');
await tx.done;
In this case, the transaction closes while the browser is fetching, so store.put fails.
enhancementsIt's common to create a transaction for a single action, so helper methods are included for this:
`js`
// Get a value from a store:
const value = await db.get(storeName, key);
// Set a value in a store:
await db.put(storeName, value, key);
The shortcuts are: get, getKey, getAll, getAllKeys, count, put, add, delete, and clear. Each method takes a storeName argument, the name of the object store, and the rest of the arguments are the same as the equivalent IDBObjectStore method.
The shortcuts are: getFromIndex, getKeyFromIndex, getAllFromIndex, getAllKeysFromIndex, and countFromIndex.
`js`
// Get a value from an index:
const value = await db.getFromIndex(storeName, indexName, key);
Each method takes storeName and indexName arguments, followed by the rest of the arguments from the equivalent IDBIndex method.
enhancementsIf a transaction involves a single store, the store property will reference that store.
`js`
const tx = db.transaction('whatever');
const store = tx.store;
If a transaction involves multiple stores, tx.store is undefined, you need to use tx.objectStore(storeName) to get the stores.
Transactions have a .done promise which resolves when the transaction completes successfully, and otherwise rejects with the transaction error.
`js`
const tx = db.transaction(storeName, 'readwrite');
await Promise.all([
tx.store.put('bar', 'foo'),
tx.store.put('world', 'hello'),
tx.done,
]);
If you're writing to the database, tx.done is the signal that everything was successfully committed to the database. However, it's still beneficial to await the individual operations, as you'll see the error that caused the transaction to fail.
enhancementsCursor advance methods (advance, continue, continuePrimaryKey) return a promise for the cursor, or null if there are no further values to provide.
`js
let cursor = await db.transaction(storeName).store.openCursor();
while (cursor) {
console.log(cursor.key, cursor.value);
cursor = await cursor.continue();
}
`
You can iterate over stores, indexes, and cursors:
`js
const tx = db.transaction(storeName);
for await (const cursor of tx.store) {
// …
}
`
Each yielded object is an IDBCursor. You can optionally use the advance methods to skip items (within an async iterator they return void):
`js
const tx = db.transaction(storeName);
for await (const cursor of tx.store) {
console.log(cursor.value);
// Skip the next item
cursor.advance(2);
}
`
If you don't manually advance the cursor, cursor.continue() is called for you.
Stores and indexes also have an iterate method which has the same signature as openCursor, but returns an async iterator:
`js
const index = db.transaction('books').store.index('author');
for await (const cursor of index.iterate('Douglas Adams')) {
console.log(cursor.value);
}
`
This is very similar to localStorage, but async. If this is _all_ you need, you may be interested in idb-keyval. You can always upgrade to this library later.
`js
import { openDB } from 'idb';
const dbPromise = openDB('keyval-store', 1, {
upgrade(db) {
db.createObjectStore('keyval');
},
});
export async function get(key) {
return (await dbPromise).get('keyval', key);
}
export async function set(key, val) {
return (await dbPromise).put('keyval', val, key);
}
export async function del(key) {
return (await dbPromise).delete('keyval', key);
}
export async function clear() {
return (await dbPromise).clear('keyval');
}
export async function keys() {
return (await dbPromise).getAllKeys('keyval');
}
`
`js
import { openDB } from 'idb/with-async-ittr.js';
async function demo() {
const db = await openDB('Articles', 1, {
upgrade(db) {
// Create a store of objects
const store = db.createObjectStore('articles', {
// The 'id' property of the object will be the key.
keyPath: 'id',
// If it isn't explicitly set, create a value by auto incrementing.
autoIncrement: true,
});
// Create an index on the 'date' property of the objects.
store.createIndex('date', 'date');
},
});
// Add an article:
await db.add('articles', {
title: 'Article 1',
date: new Date('2019-01-01'),
body: '…',
});
// Add multiple articles in one transaction:
{
const tx = db.transaction('articles', 'readwrite');
await Promise.all([
tx.store.add({
title: 'Article 2',
date: new Date('2019-01-01'),
body: '…',
}),
tx.store.add({
title: 'Article 3',
date: new Date('2019-01-02'),
body: '…',
}),
tx.done,
]);
}
// Get all the articles in date order:
console.log(await db.getAllFromIndex('articles', 'date'));
// Add 'And, happy new year!' to all articles on 2019-01-01:
{
const tx = db.transaction('articles', 'readwrite');
const index = tx.store.index('date');
for await (const cursor of index.iterate(new Date('2019-01-01'))) {
const article = { ...cursor.value };
article.body += ' And, happy new year!';
cursor.update(article);
}
await tx.done;
}
}
`
This library is fully typed, and you can improve things by providing types for your database:
`ts
import { openDB, DBSchema } from 'idb';
interface MyDB extends DBSchema {
'favourite-number': {
key: string;
value: number;
};
products: {
value: {
name: string;
price: number;
productCode: string;
};
key: string;
indexes: { 'by-price': number };
};
}
async function demo() {
const db = await openDB
upgrade(db) {
db.createObjectStore('favourite-number');
const productStore = db.createObjectStore('products', {
keyPath: 'productCode',
});
productStore.createIndex('by-price', 'price');
},
});
// This works
await db.put('favourite-number', 7, 'Jen');
// This fails at compile time, as the 'favourite-number' store expects a number.
await db.put('favourite-number', 'Twelve', 'Jake');
}
`
To define types for your database, extend DBSchema with an interface where the keys are the names of your object stores.
For each value, provide an object where value is the type of values within the store, and key is the type of keys within the store.
Optionally, indexes can contain a map of index names, to the type of key within that index.
Provide this interface when calling openDB, and from then on your database will be strongly typed. This also allows your IDE to autocomplete the names of stores and indexes.
If you call openDB without providing types, your database will use basic types. However, sometimes you'll need to interact with stores that aren't in your schema, perhaps during upgrades. In that case you can cast.
Let's say we were renaming the 'favourite-number' store to 'fave-nums':
`ts
import { openDB, DBSchema, IDBPDatabase } from 'idb';
interface MyDBV1 extends DBSchema {
'favourite-number': { key: string; value: number };
}
interface MyDBV2 extends DBSchema {
'fave-num': { key: string; value: number };
}
const db = await openDB
async upgrade(db, oldVersion) {
// Cast a reference of the database to the old schema.
const v1Db = db as unknown as IDBPDatabase
if (oldVersion < 1) {
v1Db.createObjectStore('favourite-number');
}
if (oldVersion < 2) {
const store = v1Db.createObjectStore('favourite-number');
store.name = 'fave-num';
}
},
});
`
You can also cast to a typeless database by omitting the type, eg db as IDBPDatabase.
Note: Types like IDBPDatabase are used by TypeScript only. The implementation uses proxies under the hood.
`sh`
npm run dev
This will also perform type testing.
To test, navigate to build/test/` in a browser. You'll need to set up a basic web server for this.