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

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

Version Compatibility

| Quasar | @isense-development/offline-requests | |:-----------------------------|:--------------------------------------| | | |

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

import offlineRequests from '~offline-requests';

let stores = {
    offlineRequests: offlineRequests.store,
}

Usage

<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

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.