open-index/open-npm huggingface dataset:
npm package: @prxi/dev
Description: Localhost proxy server based on prxi
Author: Vladyslav Tkachenko
Latest version: 0.1.4

# @prxi/dev

Local development proxy server. Mainly used to inject custom headers to both request and response.

## Usage

Install globally:

```bash
npm i -g @prxi/dev
```

Create `.prxi.yml` inside you project like the following:

```yaml
# port to listen connections on
port: 4444
# upstream endpoint
upstream: http://localhost:8080
```

Run `prxi`

## CLI Options

- `-c --config [path]` - optional path to the configuration file, default one `.prxi.yml`
- `-o --option [name]` - optional name for the options file

## Custom Headers

Update `.prxi.yml` and add

```yaml
default:
  # additional request headers
  request:
    Authorization: Bearer 1

  # addition response headers
  response:
    X-Custom-Header: value
```

### Options

It is possible to define different options for the request/response headers that will be added to the default set, add the following to the `.prxi.yml`:

```yaml
options:
  option-name:
    # additional request headers
    request:
      Authorization: Bearer 2

    # addition response headers
    response:
      X-Custom-Header: value
```

Note: in the example above both `Authorization` and `X-Custom-Header` values will override the ones used in the `default` section.

To apply the options run `prxi` cli with the `-o --option` parameter, e.g:

```bash
prxi -o option-name
```

## Useful Links

- [prxi](https://www.npmjs.com/package/prxi) zero dependency reverse proxy Node.js library
- [fireblink/prxi-openid-connect](https://hub.docker.com/r/fireblink/prxi-openid-connect) an OpenID Connect reverse proxy server based on [prxi](https://www.npmjs.com/package/prxi)
npm package: @prxima/ngx-form
Description: This project was generated with [Angular CLI](https://github.com/angular/angular-cli) version 9.1.6.
Author: paulo.rettamozo
Latest version: 0.0.1

# NgxForm

This project was generated with [Angular CLI](https://github.com/angular/angular-cli) version 9.1.6.

## Development server

Run `ng serve` for a dev server. Navigate to `http://localhost:4200/`. The app will automatically reload if you change any of the source files.

## Code scaffolding

Run `ng generate component component-name` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module`.

## Build

Run `ng build` to build the project. The build artifacts will be stored in the `dist/` directory. Use the `--prod` flag for a production build.

## Running unit tests

Run `ng test` to execute the unit tests via [Karma](https://karma-runner.github.io).

## Running end-to-end tests

Run `ng e2e` to execute the end-to-end tests via [Protractor](http://www.protractortest.org/).

## Further help

To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI README](https://github.com/angular/angular-cli/blob/master/README.md).
npm package: @prxima/services-manager
Description: Próxima Service Control Manager
Author: paulo.rettamozo
Latest version: 1.2.1-beta.0

# Prxima Service Control Manager

[ status: partial ][ progress ███------- 30%]
'

---

Próxima Service Manager, run all-in-one. Simple and silent

---

Summary

1. [Introduction](#introduction)
2. [Getting Start](#getting-start)
3. [Recommendations](#recommendations)
4. [Specifications](#specifications)\
   4.1. [Add Service, `options`](#addservice-options)\
   4.2. [Status](#status)
5. [Features](#features)

---

## Introduction

Robust projects today require a variety of micro-services, customer services, and other resources running on our machines before we can proceed with development.

With that in mind the next team develops this little service manager. Easy to use, simple to set up.

## Getting Start

Install this package

```
npm i -D @prxima/services-manager
```

create file `serve-manager.js` on root npm project

```js
const { ServicesManager } = required("@prxima/services-manager");

new ServicesManager()
  .addService(
    "Client Service" /* service display name */,
    "npm run client" /* shell command to run*/,
    (data, info) => {
      return data.indexOf("success") > -1 ? 1 : 0;
    } /* callback to read out command and return status, 0 = offline and 1 = online */
  )
  .addService("Server Service", "npm run server", data =>
    data.indexOf("listening") > -1 ? 1 : 0
  );
```

add script into `package.json`

```json
{
  ...
  scripts:[
    ...
    "start": "node ./serve-manager.js",
    ...
  ],
  ...
}
```

now, time to code!
🎧💻📦

```
npm run start
```

---

## Specifications

// TODO:

### addService, `options`

### Status

Status code is used to inform the manager at what stage of execution of the command the service is in; Status is obtained by service callback or message combination in `options`

```js
-2; // Error and require re-boot command
-1; // Error and await
0; // service offline and await
1; // service online and active
```

---

## Features and North

1. [x] - Run shell commands in parallel; **v1.0.x** \
2. [x] - Associate callBack to status service; **v1.1.x** \
3. [x] - Colored notification whit all services status; **v1.0.x**\
4. [x] - Auto status math by partial message definition; v1.1.x\
5. [ ] - Reload command whit specified error; v1.2.x\
6. [ ] - API Service;\
   1. [ ] - Query Services info;\
   2. [ ] - Query Status services;\
7. [ ] - Web GUI Client;\

---

Powered with ❤👌
npm package: @prxm/clickhouse
Latest version: 0.6.1

# `@prxm/clickhouse` : A dead simple Clickhouse client



## Installation
`npm install @prxm/clickhouse`

## Usage
```javascript
const clickhouse = require('@prxm/clickhouse');
const config = {
  host: 'localhost',
  protocol: 'http',
  user: 'default',
  password: 'password',
};
const client = clickhouse(config);

(async () => {
  await client.open();
  const res = await client.selectJson('SELECT number FROM system.numbers LIMIT 10;');
  console.log(res);
  await client.close();
})();
```

## API
The clickhouse client exposes several internal methods for usage

### `client.query(query, ?[params], ?queryId): Promise`

Send an async query to the HTTP interface.

##### `query: string`
SQL query statement.

```javascript
const res = await client.query(`SELECT * FROM foo WHERE a=? AND b=?`, ['hello', 'world']);
console.log(res.data, res.meta);
```

##### `params: sqlstring params`
Used for passing params to the query as
```javascript
client.query(`SELECT * FROM foo WHERE a=? AND b=?`, ['hello', 'world']);
```

##### `queryId: string`
Used as a unique `queryId` for the query.
```javascript
client.query(`SELECT * FROM foo;`, [], 'xxx');
```

### `client.selectJson(query, [params], ?queryId): Promise<JSON>`
Sends an async JSON query to the HTTP interface.

##### `query: string`
SQL query statement.

##### `params: sqlstring params`
Used for passing params to the query as
```javascript
client.selectJson(`SELECT * FROM foo WHERE a=? AND b=?`, ['hello', 'world']);
```

##### `queryId: string`
Used as a unique `queryId` for the query.
```javascript
client.selectJson(`SELECT * FROM foo;`, [], 'xxx');
```

### `client.insertBatch({table, items}, ?queryId): Promise`
Batch instert for tables.

##### `{table: string}`
The table's name.

##### `{items: [{}]}`
The items to insert, keys are used as the corresponding column names.

```javascript
const items = [
  {a: 1, b: 'foo', c: 3},
  {a: 1, b: 'baz', c: 3},
];
client.insertBatch({ table: 'batch',items});
```


##### `queryId: string`
Used as a unique `queryId` for the query.
```javascript
client.insertBatch({ table: 'batch',items}, 'xxx')
```