open-index/open-npm huggingface dataset:
npm package: @simform_team/loggernodejs
Description: It's a module to catch all the customizable log
Author: simform
Latest version: 0.0.1

# Loggerr

<!-- [![NPM Version](https://img.shields.io/npm/v/loggerr.svg)](https://npmjs.org/package/loggerr)
[![NPM Downloads](https://img.shields.io/npm/dm/loggerr.svg)](https://npmjs.org/package/loggerr)
[![CI Test](https://github.com/wesleytodd/loggerr/workflows/Tests/badge.svg)](https://github.com/wesleytodd/loggerr/actions)
[![js-standard-style](https://img.shields.io/badge/code%20style-standard-brightgreen.svg)](https://github.com/standard/standard) -->

A very simple logger.

**Features:**

- Less dependency
- No Database dependency
- You can Show your log into Template Engine
- Customizzed Logging Techniques
- Always captures stack trace on error logs

## Install

```
$ npm i  @simform_team/loggernodejs
```

## Usage

```javascript
var express = require("express");
var app = express();
var loggernodejs = require("loggernodejs");
loggernodejs.init(app);
app.get("/", (req, res) => {
  try {
    res.send("connected");
    loggernodejs.LogDebug(req, "Debug Here");
    loggernodejs.LogInfo("Connected to port");
    console.log("You Req Executed");
  } catch (error) {
    loggernodejs.LogWarn("Warn Here");
    loggernodejs.LogError(error, "Can Not Get Path");
  }
});
app.listen(3000, () => {
  console.log("Connected on port 3000");
});
```

## Log Levels

Each log level can be directed to a different output stream
or disabled entirely. The default levels are as follows:

- `info`
- `warn`
- `debug`
- `error`

### Customize Levels

You can fully customize the module with your code and also can change database locally.

## UI INTEGRATION

You can also use UI which is atteched in Example folder where example project is craeted where you can see how to integrate UI and how to use it for use UI you have to Integrate all Router code.

And if you want your own customized UI and want Only data from Module you can use below mentioned function and call Data from them.

```Javascript
//Use In router file
const loggernodejs = require("loggernodejs");

let ErrorLogDataDebug = loggernodejs.ErrorLogDataDebug;
let ErrorLogDataWarn = loggernodejs.ErrorLogDataWarn;
let ErrorLogDataError = loggernodejs.ErrorLogDataError;
let ErrorLogDataINfO = loggernodejs.ErrorLogDataINfO;
let reqData = loggernodejs.reqData;
```
npm package: @simfyz/ngx-image-viewer
Description: Angular image viewer component with Ivy support
Author: Fayas Ismail
Latest version: 2.3.0

# NgxImageViewer

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 15.2.0.

## Code scaffolding

Run `ng generate component component-name --project ngx-image-viewer` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project ngx-image-viewer`.
> Note: Don't forget to add `--project ngx-image-viewer` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build ngx-image-viewer` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build ngx-image-viewer`, go to the dist folder `cd dist/ngx-image-viewer` and run `npm publish`.

## Running unit tests

Run `ng test ngx-image-viewer` to execute the unit tests via [Karma](https://karma-runner.github.io).

## Further help

To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI Overview and Command Reference](https://angular.io/cli) page.
npm package: @simfyz/ngx-range-slider
Description: Angular range slider component with Ivy support
Author: Fayas Ismail
Latest version: 2.0.0

# NgxRangeSlider

This project was generated with [Angular CLI](https://github.com/angular/angular-cli) version 15.2.5.

## Development server

Run `ng serve` for a dev server. Navigate to `http://localhost:4200/`. The application 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.

## 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 a platform of your choice. To use this command, you need to first add a package that implements end-to-end testing capabilities.

## Further help

To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI Overview and Command Reference](https://angular.io/cli) page.
npm package: @simfyz/pipe-function
Description: Pipe operator to execute functions from the template.
Author: Fayas Ismail
Latest version: 2.0.0

# PipeFunction

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 15.2.0.

## Code scaffolding

Run `ng generate component component-name --project pipe-function` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project pipe-function`.
> Note: Don't forget to add `--project pipe-function` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build pipe-function` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build pipe-function`, go to the dist folder `cd dist/pipe-function` and run `npm publish`.

## Running unit tests

Run `ng test pipe-function` to execute the unit tests via [Karma](https://karma-runner.github.io).

## Further help

To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI Overview and Command Reference](https://angular.io/cli) page.
npm package: @simgenius/talentui-dev-server
Description: ## 问题是什么
Author: Raymond Li
Latest version: 1.6.1
Deprecated: false

# talentui-dev-server

## 问题是什么

当进行前端开发的时候，前端在开发过程中的流程一般是这样的。

* 首先打开线上任何一个环境，（开发，测试，线上）
* 把前端资源服务器地址指向本地 （配host, 比如stnew03.beisen.com 127.0.01）
* 启动项目的dev server，监测项目文件变化 ，然后提供静态资源服务，这里会依赖一个类似webpack-dev-server这样的微型web server, 端口常用的是3000，8000，8080等。 （启动项目的开发环境）
* 安装IIS（windows）或者nginx(unix)的等web server，配置反向代理，这时启动的是80端口，对应线上环境的请求的端口。因为配置了host所有对应的请求会请求到web server上。(配置反向代理服务器)
* 在web server上对请求文件的路径进行解析，重写(rewrite) 比如，我请求一个stnew03.beisen.com/xxx/xxx/func.min.x39fd0fdfd.js 返回给我的是重新请求127.0.0.1:3000/dist/func.js文件 （url rewrite）
* 这时基本流程已经完成，打开线上环境，会发现请求真实返回结果是通过第3步服务提供的文件。此时本地开发环境配置基本完成。

这时有几个问题，

1. 首先这个流程很麻烦，
2. 需要的专业外的知识比较多，有的时候只能照着做不知道为啥
3. 对环境依赖比较严重，换台电脑就，或者重装系统就得再来一遍，还不一定能成功。
4. 如果项目换了，规则就需要调整，配置文件在哪，应该改哪里，这是个问题

## 反正就是不方便

那应该如何简化这个流程呢。

首先我们要看，整个流程中哪些是可以优化的，创建启动本地项目很简单，开发，测试环境的准备不需要前端怎么操作，**比较麻烦的是配置nginx 或者IIS代理的过程。**

* 第一个比较麻烦的，就是安装，安装IIS或者nginx首先是相当前端专业知识之外的东西，我记得我入职的时候就是照着文档一步一步搞的。有的时候照着文档做完了，中间步骤出了错，完全不知道怎么处理，还得去问其他同时，费时费力。
* 第二个比较麻烦的就是，一但开了代理，还得配置host，把比如xxx.com指向127.0.0.1, 这样一来所有的请求才能到达代理服务器，然后转发到本地项目上。当你不需要的时候还得记得关掉host，虽然有switchhost，还得请dns缓存
* 开启了代理和配置了host之后，来回切切也没啥，突然你发现一个问题，就是访问的页面是个iframe,一个产品的页面嵌入了另外一个产品的页面，这是两个前端的项目，而你本地只启了其中一个，另外一个因为没有资源服务文件全部404了，导致啥也看不着。不得己只能换域名了。
* 我可能只需要替换一个文件，nginx不合适，又得使用charles或者fiddler，但是mac下收费...，还得破解，其实我们的需求并不复杂，没那个必要啊。
* 哎呀，我要去另外一个项目去支援两天，上面的步骤还得再来一遍......

所以，我们需要一个专门满足我开发需求的东西，不需要复杂的配置，不需要太重，切换起来要方便，不需要来回切host，不需要匹配的文件可以直接走线上，调试起来方便。

这些问题已困绕很久了...直到有一天，我们决定改变他。

首先，我们要清楚流程是什么，请看图。
npm package: @simhateja/n8n-nodes-ibm-db2
Description: n8n node for executing queries on IBM DB2
Latest version: 0.1.0

# n8n Node for IBM DB2

This is a community node for [n8n](https://n8n.io/) that allows you to run SQL queries against an IBM DB2 database.

## Installation

Follow the installation guide in the [n8n documentation](https://docs.n8n.io/integrations/community-nodes/installation/).

1.  Go to **Settings > Community Nodes**.
2.  Select **Install**.
3.  Enter `@simhateja/n8n-nodes-ibm-db2` in the **Enter npm package name** field.
4.  Agree to the risks and click **Install**.

After installing the node, you can use it in your workflows.

## Usage

This node provides a single action: running a query.

1.  Drag the **IBM DB2** node into your workflow.
2.  Create new credentials by providing your DB2 database **Hostname, Port, Database name, User, and Password**.
3.  In the **Query** field, enter the SQL query you wish to execute.

The node will output the data returned by the `SELECT` statement, or an empty item for operations like `CREATE`, `INSERT`, `UPDATE`, or `DELETE`.

## Local Development & Testing

This node can be tested locally using the IBM DB2 Docker container.

1.  Run the local database:
    `docker run -itd --name db2_test -p 50000:50000 -e DBNAME=testdb -e DB2INSTANCE=db2inst1 -e DB2INST1_PASSWORD=password -e LICENSE=accept --privileged=true ibmcom/db2`
2.  Use the following credentials in n8n:
    *   **Hostname**: `localhost`
    *   **Port**: `50000`
    *   **Database**: `testdb`
    *   **User**: `db2inst1`
    *   **Password**: `password` # n8n