open-index/open-npm huggingface dataset:
npm package: @gridnt/ngplus
Description: ngplus vue components
Author: gridnt
Latest version: 1.0.3

# ng-plus

> ngplus vue components

## Build Setup

``` bash
# install dependencies
npm install

# serve with hot reload at localhost:8080
npm run dev

# build for production with minification
npm run build

# build for production and view the bundle analyzer report
npm run build --report

# run unit tests
npm run unit

# run e2e tests
npm run e2e

# run all tests
npm test
```

For a detailed explanation on how things work, check out the [guide](http://vuejs-templates.github.io/webpack/) and [docs for vue-loader](http://vuejs.github.io/vue-loader).
npm package: @gridonic/client-services
Description: A service library for our projects respecting application boundaries and encapsulating dependencies.
Latest version: 0.3.0

# Gridonic Client Services

A service library for our projects respecting application boundaries and encapsulating dependencies.

It works best for projects created with [@gridonic/cli](https://www.npmjs.com/package/@gridonic/cli).

## Concepts

The library is designed to provide services used repeatedly in projects.

- Provides interfaces for each exported service and model
- The services are mostly independent from each other, so they can be added selectively to the projects
- Written in typescript 

### Benefits

- Standardizes our projects by using interfaces for common services and models
- Encapsulates dependencies, making it possible to replace them easier if needed
- No magic or restrictions: services can be extended, copied or completely replaced if they are not suiting the project
- Only used services get compiled into project

## Usage in Projects

Services can be imported selectively into a project. It is recommended to do all imports in one file in each project
and exporting the types. This prevents the code from being cluttered with import statements from this library.

## Developing the library

### Local project setup

Install dependencies
```
npm install
```

Run unit tests
```
npm run test
```

Lints and fixes files
```
npm run lint
```

### Publishing

When ready to release, execute the following steps, given that all changes are commited in the master branch:
- List changes in the CHANGELOG.md
- Bump your version and automatically create a git tag with `npm version <type>`, where type is patch, minor or major
- Push the master branch `git push` and the tags `git push --tags`
- Create a release in github. A github action will then automatically publish the package to npm

### Guidelines

- Every service must be documented
- Every service must implement an interface
- Every service must be unit-tested