# @isense-development/administration

> Administration package

Latest version **2.0.4** (published 2022-01-11) · MIT license · 0 weekly downloads

## Install

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

## 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.4 |
| Published | 2022-01-11 |
| First published | 2022-01-07 |
| Weekly downloads | 0 |
| License | MIT |
| TypeScript types | none |
| Module format | CommonJS |
| Node | >= 14.17.4 |
| Dependencies | 10 |
| Unpacked size | 96.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/administration
- npm.io page: https://npm.io/package/@isense-development/administration

## Dependencies (10)

- [axios](https://npm.io/package/axios.md) ^0.24.0
- [jszip](https://npm.io/package/jszip.md) ^3.5.0
- [bootstrap](https://npm.io/package/bootstrap.md) ^4.6.1
- [popper.js](https://npm.io/package/popper.js.md) ^1.16.1
- [@progress/kendo-ui](https://npm.io/package/@progress/kendo-ui.md) ^2021.3.1109
- [@progress/kendo-licensing](https://npm.io/package/@progress/kendo-licensing.md) ^1.2.1
- [@progress/kendo-theme-material](https://npm.io/package/@progress/kendo-theme-material.md) ^4.43.0
- [@progress/kendo-grid-vue-wrapper](https://npm.io/package/@progress/kendo-grid-vue-wrapper.md) ^2021.3.1109
- [@progress/kendo-dropdowns-vue-wrapper](https://npm.io/package/@progress/kendo-dropdowns-vue-wrapper.md) ^2021.3.1109
- [@progress/kendo-datasource-vue-wrapper](https://npm.io/package/@progress/kendo-datasource-vue-wrapper.md) ^2021.3.1109

## Recent versions

- 2.0.4 (latest) — 2022-01-11
- 2.0.3 — 2022-01-11
- 2.0.2 — 2022-01-10
- 2.0.1 — 2022-01-09
- 2.0.0 — 2022-01-07
- 0.1.4 — 2022-01-07
- 0.1.3 — 2022-01-07
- 0.1.2 — 2022-01-07

## README

# Administration module

This module expands the current application where all settings, users and configs ect are kept and can be managed.

## Installation

`npm i @isense-development/administration`

Add the package to the `env.json file`

```json
{
    "app": {
        "packages": [
            {"name": "administration"}
        ]
    }
}
```

## Version Compatibility

| Quasar                      | @isense-development/administration                            |
|:-----------------------------|:--------------------------------------|
| ![Quasar v2.x][quasar_2_x] | ![@isense-development/administration v2.x][@isense-development/administration_2_x]     |

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

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

## Auto generated alias

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

## Register the routes

You need to register the routes in the `src/router/routes.js` file and assign them to which layout you want to use them

```js
/* Add here the packages that have included routes */
import administration from '~administration';

/* push your package routes to the router
 The layout refers to which parent you want to add the routes as children
 */
packageRoutes.push({ name: 'administration', package: administration.router, layout: 'main-layout' });
```

## 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/administration · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._