# @isense-development/offline-requests

> Offline-requests module

Latest version **2.0.3** (published 2022-01-10) · MIT license · 0 weekly downloads

## Install

```sh
npm install @isense-development/offline-requests
pnpm add @isense-development/offline-requests
yarn add @isense-development/offline-requests
bun add @isense-development/offline-requests
```

## Health

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

Positive: no vulnerabilities.

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

Negative: abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 2.0.3 |
| Published | 2022-01-10 |
| First published | 2022-01-07 |
| Weekly downloads | 0 |
| License | MIT |
| TypeScript types | none |
| Module format | CommonJS |
| Node | >= 14.17.4 |
| Dependencies | 2 |
| Unpacked size | 8.1 KB |
| Known vulnerabilities | 0 (+23 in 1 direct dependencies) |
| Install scripts | yes |
| Author | Hemelaers Jan |
| Maintainers | isense-development |

## Links

- npm: https://www.npmjs.com/package/@isense-development/offline-requests
- npm.io page: https://npm.io/package/@isense-development/offline-requests

## Dependencies (2)

- [axios](https://npm.io/package/axios.md) ^0.24.0
- [localbase](https://npm.io/package/localbase.md) ^0.7.4

## Recent versions

- 2.0.3 (latest) — 2022-01-10
- 2.0.2 — 2022-01-09
- 2.0.1 — 2022-01-09
- 2.0.0 — 2022-01-07
- 0.1.1 — 2022-01-07

## README

# Offline request processing module

With this module you can handle offline requests storage to sync when you are back online

## Installation

`npm i @isense-development/offline-requests`

Add the package to the `env.json file`

```json
{
    "app": {
        "packages": [
            {"name": "offline-requests"}
        ]
    }
}
```

## Version Compatibility

| Quasar                      | @isense-development/offline-requests                            |
|:-----------------------------|:--------------------------------------|
| ![Quasar v2.x][quasar_2_x] | ![@isense-development/offline-requests v2.x][@isense-development/offline-requests_2_x]     |

[quasar_2_x]:  https://img.shields.io/badge/version-2.x-blue

[@isense-development/offline-requests_2_x]:   https://img.shields.io/badge/version-2.x-blue

## Auto generated alias

In the `quasar.conf.json` the alias is automatically created '~offline-requests' based on the module name in the `env.json` file

## Register the store

You need to register the store in the `src/store/package-stores.js` file

```js
import offlineRequests from '~offline-requests';

let stores = {
    offlineRequests: offlineRequests.store,
}
```

## Usage

```vue

<template>
  <div id="app">
    <btn-offline-sync-requests/>
  </div>
</template>

<script>
import { defineComponent } from 'vue'
import BtnOfflineSyncRequests from '~offline-requests/components/btn-offline-sync-requests'

export default defineComponent({
  name      : 'main-header',
  components: { BtnOfflineSyncRequests }
})
</script>
```

## How update packages?

[4 Safe Steps to Update npm Packages](https://josipmisko.com/posts/how-to-update-npm-packages-in-4-easy-steps)

Cheat Sheet: 6 Commands To Help You Update npm Packages

This cheat sheet will make it easy to safely update npm packages in your node application. It includes a list of commands that will help you keep up with the latest updates and avoid breaking changes.

* Use `npm list` --depth 0 to list all the packages in your package directory
* Use `npm audit` to find out which of your npm dependencies are vulnerable.
* Use `npm outdated` to list the packages that are out of date with respect to what is installed in package.json
* Use `npm update package_name` to update an individual package that has already been installed.
* Use `npm uninstall package_name` and npm install package_name@version to revert to a specific version.
* Use `npm cache clean --force` to clear npm's cache of all the packages that have been installed.

---
_Source: https://npm.io/package/@isense-development/offline-requests · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._