# cached-gdrive

> An offline-first Google-Drive-backed storage system for progressive web apps.

Latest version **0.2.1** (published 2017-09-05) · MIT license · 0 weekly downloads

## Install

```sh
npm install cached-gdrive
pnpm add cached-gdrive
yarn add cached-gdrive
bun add cached-gdrive
```

## Health

**Score 15/100 (F)** — status: abandoned.

Positive: no vulnerabilities.

Warnings: low downloads; no types; no esm support; pre 1.0.

Negative: abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 0.2.1 |
| Published | 2017-09-05 |
| First published | 2017-08-25 |
| Weekly downloads | 0 |
| License | MIT |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 7 |
| Known vulnerabilities | 0 |
| Install scripts | no |
| Author | Dan Mercer |
| Maintainers | drmercer |

## Links

- npm: https://www.npmjs.com/package/cached-gdrive
- Repository: https://github.com/drmercer/cached-gdrive
- Homepage: https://github.com/drmercer/cached-gdrive#readme
- Issues: https://github.com/drmercer/cached-gdrive/issues
- npm.io page: https://npm.io/package/cached-gdrive

## Dependencies (7)

- [shortid](https://npm.io/package/shortid.md) ^2.2.8
- [immutable](https://npm.io/package/immutable.md) ^3.8.1
- [eventemitter3](https://npm.io/package/eventemitter3.md) ^2.0.3
- [gdrive-simple](https://npm.io/package/gdrive-simple.md) ^0.11.0
- [promise-retry](https://npm.io/package/promise-retry.md) ^1.1.1
- [json-merge-patch](https://npm.io/package/json-merge-patch.md) ^0.2.3
- [immutable-merge-patch](https://npm.io/package/immutable-merge-patch.md) ^1.0.1

## Recent versions

- 0.2.1 (latest) — 2017-09-05
- 0.2.0 — 2017-09-04
- 0.1.1 — 2017-08-25
- 0.1.0 — 2017-08-25

## README

# cached-gdrive

TODO

# Limitations
- **cached-gdrive** is currently best suited for use in the app data folder, since
  files there can only be changed by your app. This library doesn't track files
  being moved, so things might get messy if you use it with files the user can
  move.
- When going from offline to online, it handles errors properly (at least, it's
  designed to do so), but I'm pretty sure there's no way to consume network
  errors from JavaScript, which means network failures still get logged in
  debugging consoles. *(See the [Tips](#tips) section for help with hiding those
  errors.)*

# Tips
- When debugging network-change capabilities, you'll probably want to filter out
  Google-API-related network errors from your console. In Chrome Dev Tools, you
  can use this RegEx as a filter to accomplish that:
  `/^(?!.*(?:google|gstatic).*net::ERR)/`

---
_Source: https://npm.io/package/cached-gdrive · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._