open-index/open-npm huggingface dataset:
npm package: @lexiq/types
Description: Shared TypeScript types for LexIQ services
Author: Remodl AI
Latest version: 1.1.0

# @lexiq/types

Shared TypeScript types for LexIQ services. This package provides type definitions used across both cf-workers and lexiq-server projects.

## Installation

```bash
npm install @lexiq/types
```

## Usage

### Import all types

```typescript
import { AgentSession, KnowledgeURI, SearchResponse } from '@lexiq/types';
```

### Import specific type categories

```typescript
// Auth types
import { AgentSession, ApiKeyData } from '@lexiq/types/auth';

// Knowledge types
import { KnowledgeURI, KnowledgeMetadata } from '@lexiq/types/knowledge';

// API response types
import { SearchResponse, KnowledgeResponse } from '@lexiq/types/api';
```

## Type Categories

### Auth Types (`/auth`)
- Authentication and session types
- API key structures
- Multi-tenancy context types

### Knowledge Types (`/knowledge`)
- Universal Knowledge URI types
- Knowledge metadata structures
- Source type enumerations

### API Types (`/api`)
- Search endpoint response types
- Knowledge retrieval response types
- Common API structures

## Development

This package supports both CommonJS and ES Modules:

- ESM: `dist/esm/`
- CJS: `dist/cjs/`

### Building

```bash
npm run build       # Build both ESM and CJS
npm run build:esm   # Build ES modules only
npm run build:cjs   # Build CommonJS only
```

## License

MIT
npm package: @lexiraeanna/node-red-contrib-google-drive
Description: A Node-RED node to interact with Google Drive using OAuth2
Author: Lexi Love
Latest version: 2.0.8

** THIS IS A WORK IN PROGRESS. I will be making a new version, as this one is not updating correctly. **

# Node-RED Google Drive Integration

This Node-RED module provides nodes to interact with Google Drive using OAuth2.

## Installation

To install, use the following command in your Node-RED directory:

```sh
npm install @lexiraeanna/node-red-contrib-google-drive
```
## Setup

### Google API Credentials Configuration

1. Drag and drop the **Google Drive API** node into your Node-RED flow.
2. Click on "Add new google-credentials" to create a **google-credentials** configuration node.
3. Configure the node with your OAuth 2.0 credentials:
   - **Client ID**: Your OAuth 2.0 Client ID obtained from Google Cloud Console.
   - **Client Secret**: Your OAuth 2.0 Client Secret obtained from Google Cloud Console.
   - **Redirect URI**: URL where Google should redirect after authorization (e.g., `http://localhost:1880/google-credentials/auth/callback`).
   - **Scopes**: Scopes required for Google Drive API access (e.g., `https://www.googleapis.com/auth/drive`).

4. Click **Start Authorization** to begin the OAuth 2.0 authorization process.

### Google Drive API Node Configuration

1. Add the **Google Drive** API node to your Node-RED flow.
2. Configure the node:
   - **Name**: Give your node a descriptive name.
   - **Google Credentials**: Select the configured Google Credentials node.
   - **Operation**: Choose the operation you want to perform (e.g., list, get, create, update, delete).
   - Configure additional parameters based on the selected operation:
     - **Folder ID**: ID of the folder for operations like list or create.
     - **File ID**: ID of the file for operations like get, update, or delete.
     - **File Name**: Name of the file to create or update.

3. Deploy your Node-RED flow to apply the changes.

## Usage

- Use the configured Node-RED flow to interact with Google Drive:
  - **List Files**: Lists files in a specified folder.
  - **Get File**: Retrieves metadata or content for a specific file.
  - **Create File**: Uploads a new file to Google Drive.
  - **Update File**: Updates metadata or content of an existing file.
  - **Delete File**: Deletes a file from Google Drive.
  - **Export File**: Exports a file in a specified MIME type.

- If you would like to preview the file's contents prior to deploying your flow, click on the "Fetch File Content" button next to the file ID. Your file's data will populate in the content and metadata fields, and as an alert pop-up for the operations without them.
npm package: @lexitgroup/cordova-plugin-lexit-btprint
Description: Cordova Bluetooth Print plugin
Author: Lexit Group Norway AS
Latest version: 1.0.8

[![npm version](https://badge.fury.io/js/%40lexitgroup%2Fcordova-plugin-lexit-btprint.svg)](https://badge.fury.io/js/%40lexitgroup%2Fcordova-plugin-lexit-btprint)

# cordova-plugin-lexit-btprint

Print to Zebra QLn220 over bluetooth
npm package: @lexluthordev/igw-sdk
Description: Cliente IGAMEWIN API em JavaScript (Node 18+)
Author: Lex Luthor
Latest version: 0.1.1

# igw-sdk (JS)

Cliente mínimo para a API IGAMEWIN (`POST https://igamewin.com/api/v1`).

> Requisitos: Node 18+ (fetch nativo). Logger é silencioso por padrão.

## Instalação
```bash
npm i @lexluthordev/igw-sdk
```

## Uso (ESM)
```js
import { createClient } from "@lexluthordev/igw-sdk";

const igw = createClient({
  agentCode: "lexluthor",
  agentToken: "SEU_TOKEN",
});

const r = await igw.providerList();
console.log(r);
```

## Uso (CommonJS)
```js
const { createClient } = require("@lexluthordev/igw-sdk");

(async () => {
  const igw = createClient({ agentCode: "lexluthor", agentToken: "SEU_TOKEN" });
  const r = await igw.providerList();
  console.log(r);
})();
```

## Convenções
- Dinheiro sempre em **centavos** (inteiros), exatamente como na documentação.
- Enviamos apenas campos documentados (snake_case). Sem campos extras.
- Em falha (`status: 0`), o cliente lança erro com `code = msg`.

## Métodos principais
- `createUser({ user_code, is_demo? })`
- `deposit({ user_code, amount })`
- `withdraw({ user_code, amount })`
- `resetUserBalance({ user_code })`
- `resetAllUsersBalance()`
- `setDemo({ user_code })`
- `launchGame({ user_code, provider_code, game_code?, lang? })`
- `providerList()`
- `gameList({ provider_code })`
- `moneyInfo()` / `moneyInfoForUser({ user_code })` / `moneyInfoAllUsers()`
- `getGameLog({ user_code, game_type, start, end, page?, perPage? })`
- `raw(method, payload)`

## Erros mapeados
`INVALID_METHOD`, `INVALID_PARAMETER`, `INVALID_AGENT`, `INVALID_AGENT_ROLE`, `BLOCKED_AGENT`, `INVALID_USER`, `MAX_DEMO_USER`, `INSUFFICIENT_AGENT_FUNDS`, `INSUFFICIENT_USER_FUNDS`, `DUPLICATED_USER`, `INVALID_PROVIDER`, `INTERNAL_ERROR`, `EXTERNAL_ERROR`, `API_CHECKING`, `AGENT_SEAMLESS`.