npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

idb-file-storage

v0.1.0

Published

Simple Promise-based IndexedDB wrapper to store files

Downloads

1,516

Readme

IDB File Storage

Build Status esdoc Coverage

Status: Prototype/Proposal.

This library wraps some of the IndexedDB features related to store files into a Promised API.

While on Chrome this library only provides a basic API to store File and Blob instances, on Firefox it also provides a Promise based API wrapper for the non-standard IDBMutableFile API.

The non-standard IDBMutableFile API allows to create and optionally persist into the an IndexedDB database a file object which provides an API to be able to read and change the file content without loading all its content in the memory.

This library should allow WebExtensions add-ons to be able to store and manipulate files more efficiently, without providing direct access to arbitrary files on the user filesystem.

The Promise based IDBMutableFile API is currently not available when this library runs on Chrome (e.g. as a Chrome extension), but it still works for storing and retrieving Blob and File instances. Even if not yet implemented, providing a polyfill for the IDBMutableFile API on Chrome based on Blob instances is technically possible.

A more detailed API reference (generated using esdoc from the inline comments), and a collection of small examples are available at the following urls:

  • API Reference: https://doc.esdoc.org/github.com/rpl/idb-file-storage/
  • Examples:
    • Live Demo: https://rpl.github.io/idb-file-storage/examples/
    • Source: https://github.com/rpl/idb-file-storage/tree/master/examples/

How to use it

The library is wrapped as an UMD module, and so it can be included as a CommonJS module using a CommonJS module loader (e.g. webpack, browserify, rollup, ...) or as an AMD module from a AMD module loader (e.g. RequireJS), as well as just included as a tag script into an HTML page.

async function testIDBFiles() {
  const tmpFiles = await IDBFiles.getFileStorage({name: "tmpFiles"});

  const file = await tmpFiles.createMutableFile("path/filename.txt");
  const fh = file.open("readwrite");

  const metadata = await fh.getMetadata();
  console.log(metadata.size); // -> 0

  await fh.append("new file content");

  const metadata = await fh.getMetadata();
  console.log(metadata.size); // -> updated size

  await fh.close();

  await file.persist();

  const fileNames = await tmpFiles.list();
  console.log(fileNames); // -> ["path/filename.txt"]

  const file = await tmpFiles.get("path/filename.txt");
  // Only open if its a mutable file.
  if (file.open) {
    const fh = file.open("readonly");
    const metadata = await fh.getMetadata();
    console.log(metadata.size); // -> updated size
  }

  await tmpFiles.clear(); // or tmpFiles.remove("path/filename.txt")
  const fileNames = await tmpFiles.list();
  console.log(fileNames); // -> []
}

Building, Testing and Hacking

Building the source file into a UMD module (and lint the javascript sources in the process):

$ npm run build
...

Running the karma tests (which also builds the library and open a Chrome and a Firefox instance and run the test on both):

$ npm run test

While working on the library or test sources, you may want to watch the sources for changes and lint, rebuild and re-run the tests accordingly:

$ npm run test:watch