open-index/open-npm huggingface dataset:
npm package: @hyperdx/lucene
Description: Lucene query parser and formatter for JavaScript created using PEG.js
Author: Ben Ripkens
Latest version: 3.1.1

# lucene &nbsp; [![Build Status](https://travis-ci.org/bripkens/lucene.svg?branch=master)](https://travis-ci.org/bripkens/lucene) [![Coverage Status](https://img.shields.io/coveralls/bripkens/lucene.svg)](https://coveralls.io/r/bripkens/lucene?branch=master) [![npm version](https://badge.fury.io/js/lucene.svg)](https://badge.fury.io/js/lucene)

Parse, modify and stringify lucene queries.

**[Installation](#installation) |**
**[Try It](https://runkit.com/npm/lucene) |**
**[Usage](#usage) |**
**[Grammar](#grammar) |**
**[History](#history)**

---

## Installation

```
npm install --save lucene
-or-
yarn add lucene
```

## Usage

```javascript
const lucene = require('lucene');

const ast = lucene.parse('name:frank OR job:engineer');
console.log(ast);
// {
//   left: {
//     field: 'name',
//     term: 'frank'
//   },
//   operator: 'OR',
//   right: {
//     field: 'job',
//     term: 'engineer'
//   }
// }

console.log(lucene.toString(ast));
// name:frank OR job:engineer
```


## Grammar
The parser is auto-generated from a PEG implementation in JavaScript called [PEG.js](https://pegjs.org/).

To test the grammar without using the generated parser, or if you want to modify it, try out [PEG.js online](http://pegjs.org/online). This is a handy way to test arbitrary queries and see what the results will be like or debug a problem with the parser for a given piece of data.


## History
This project is based on [thoward/lucene-query-parser.js](https://github.com/thoward/lucene-query-parser.js) and its forks (most notably [xomyaq/lucene-queryparser](https://github.com/xomyaq/lucene-queryparser)). The project is forked to allow some broader changes to the API surface area, project structure and additional capabilities.
npm package: @hyperengage/sdk-js
Description: Hyperengage JavaScript SDK
Author: Hyperengage Dev
Latest version: 1.0.3

# Hyperengage JavaScript SDK (hyperengage-js)

## Maintainers Guide

This section is indented only for package maintainers.

### Building and local debug

 * _**ATTENTION**_: Use `yarn` for everything except publishing
 * To spin off a local development server run `yarn devserver`, then open [http://localhost:8081](http://localhost:8081)
   * The server listens to all changes to src and rebuilds npm and `lib.js` automatically. Open test cases HTML files to see
     hyperengage in action
     * http://localhost:8081/test-case/embed.html - embedded Hyperengage
     * http://localhost:8081/test-case/embed-no-init.html - Hyperengage without automatic initialization
     * http://localhost:8081/test-case/segment-intercept.html - test segment interception
 * `yarn test` runs [Playwright](https://playwright.dev/) test
 * `yarn build` builds both npm package and `lib.js` browser bundle
 * `npm publish --public` to publish the package (change version in `package.json` manually). You need to run `npm login` with your personal
npmjs account beforehand (make sure you have access to Hyperengage team)

### Publishing new version

 * Login with your *personal* credentials with `npm login`
 * Run `yarn install && yarn build && yarn test && npm publish --access public`
npm package: @hyperexperience/typescript-config
Description: TypeScript configuration for Hyperx projects
Author: Hyperx
Latest version: 0.1.3

# @hyperx/typescript-config

Hyperx 프로젝트를 위한 TypeScript 설정 패키지입니다.

## 설치

```bash
npm install --save-dev @hyperx/typescript-config
```

## 사용법

### 기본 설정

```json
{
  "extends": "@hyperx/typescript-config/base"
}
```

### Node.js 프로젝트

```json
{
  "extends": "@hyperx/typescript-config/node"
}
```

### React 프로젝트

```json
{
  "extends": "@hyperx/typescript-config/react"
}
```

### Next.js 프로젝트

```json
{
  "extends": "@hyperx/typescript-config/next"
}
```

## 설정 옵션

각 설정은 다음과 같은 특징을 가집니다:

- **base**: 기본적인 TypeScript 설정
- **node**: Node.js 환경에 최적화된 설정
- **react**: React 프로젝트에 최적화된 설정
- **next**: Next.js 프로젝트에 최적화된 설정

## 라이선스

MIT
npm package: @hyperfixi/types-browser
Description: TypeScript type definitions for LokaScript browser globals
Author: LokaScript Contributors
Latest version: 2.3.1

# @lokascript/types-browser

TypeScript type definitions for LokaScript browser globals.

## Installation

```bash
npm install --save-dev @lokascript/types-browser
```

## Usage

Add to your `tsconfig.json`:

```json
{
  "compilerOptions": {
    "types": ["@lokascript/types-browser"]
  }
}
```

Now you get full TypeScript autocomplete for browser globals:

```typescript
// Full IDE autocomplete and type safety!
window.lokascript.execute('toggle .active', document.body);
window._hyperscript.compile('on click add .highlight');

window.LokaScriptSemantic.parse('トグル .active', 'ja');
window.LokaScriptSemantic.translate('toggle .active', 'en', 'ko');

window.LokaScriptI18n.translate('on click toggle .active', 'en', 'ja');
```

## Provided Types

### window.lokascript / window.\_hyperscript

Core LokaScript API (from `lokascript-browser.js` or `lokascript-multilingual.js`):

- `compile(source, options?)` - Compile hyperscript to AST
- `execute(source, element?, context?)` - Execute hyperscript
- `parse(source)` - Parse to AST
- `processNode(node)` - Process single DOM node
- `process(root?)` - Process entire document
- `createContext(element?, options?)` - Create execution context
- `isValidHyperscript(source)` - Validate syntax
- `version` - Get version string
- `createRuntime(options?)` - Create runtime instance

### window.LokaScriptSemantic

Semantic parsing API (from `lokascript-semantic.browser.global.js`):

- `parse(source, language)` - Parse in any of 13 languages
- `translate(source, fromLang, toLang)` - Translate between languages
- `getAllTranslations(source, sourceLang)` - Get all translations
- `createSemanticAnalyzer(options?)` - Create analyzer
- `supportedLanguages` - Array of supported language codes

### window.LokaScriptI18n

Grammar transformation API (from `lokascript-i18n.min.js`):

- `translate(source, fromLang, toLang)` - Transform with grammar rules
- `createTransformer(options?)` - Create transformer instance
- `supportedLocales` - Array of supported locales
- `getProfile(locale)` - Get language grammar profile

## Browser Bundle Loading

```html
<!-- Load LokaScript browser bundles -->
<script src="https://cdn.jsdelivr.net/npm/@lokascript/core/dist/lokascript-browser.js"></script>
<script src="https://cdn.jsdelivr.net/npm/@lokascript/semantic/dist/lokascript-semantic.browser.global.js"></script>
<script src="https://cdn.jsdelivr.net/npm/@lokascript/i18n/dist/lokascript-i18n.min.js"></script>

<!-- Now use with full TypeScript support -->
<script>
  // TypeScript knows about these globals!
  window.lokascript.execute('toggle .active');
  window.LokaScriptSemantic.parse('トグル .active', 'ja');
  window.LokaScriptI18n.translate('toggle .active', 'en', 'ja');
</script>
```

## License

MIT
npm package: @hyperflow-global/n8n-nodes-hyperflow-whatsapp
Description: n8n community node for Hyperflow WhatsApp API integration
Author: Hyperflow
Latest version: 1.0.10

# n8n-nodes-hyperflow-whatsapp

n8n community node for Hyperflow WhatsApp API integration.

## Installation

### In n8n Desktop App

1. Go to **Settings** > **Community Nodes**
2. Select **Install a community node**
3. Enter `@hyperflow-global/n8n-nodes-hyperflow-whatsapp`
4. Click **Install**

### Manual Installation

```bash
# Navigate to your n8n installation folder
cd ~/.n8n

# Install the package
npm install @hyperflow-global/n8n-nodes-hyperflow-whatsapp
```

### Development Installation (Local)

```bash
# Build the project
npm install
npm run build

# Link to n8n
npm link

# In your n8n installation
cd ~/.n8n
npm link @hyperflow-global/n8n-nodes-hyperflow-whatsapp
```

## Configuration

### Credentials: Hyperflow WhatsApp Account

1. In n8n, go to **Credentials** > **Add Credential**
2. Search for "Hyperflow WhatsApp Account"
3. Configure:
   - **API Key**: Your API key for authentication

## Available Nodes

### Hyperflow WhatsApp Trigger

Webhook trigger that starts workflows when WhatsApp events occur.

#### Supported Events

| Event | Description |
|-------|-------------|
| **Message Received** | Triggered when a message is received |
| **Message Status Update** | Triggered when message status changes (sent, delivered, read) |
| **Button Click** | Triggered when a button is clicked |
| **List Selection** | Triggered when a list item is selected |
| **Flow Response** | Triggered when a flow response is received |

#### Options

- **Filter Numbers**: Only trigger for specific phone numbers
- **Ignore Own Status**: Ignore status updates for messages sent by this number

#### Webhook URL

After activating the workflow, copy the webhook URL provided by n8n and configure it in your Hyperflow API settings.

---

### Hyperflow WhatsApp

Send WhatsApp messages through Hyperflow API. Supports multiple message types:

#### Message Types

| Type | Description |
|------|-------------|
| **Text** | Simple text message with optional buttons (postback, URL, voice call) |
| **Image** | Send an image with optional caption |
| **Video** | Send a video with optional caption |
| **Audio** | Send an audio file |
| **File** | Send a document (PDF, etc.) |
| **Sticker** | Send a WhatsApp sticker |
| **Location** | Send a location with coordinates |
| **Contact** | Send a contact card (vCard) |
| **List** | Interactive list with sections |
| **Template (HSM)** | Send approved message templates |
| **Flows** | Interactive WhatsApp Flows |
| **Generic Card** | Card with image, title, subtitle and buttons |
| **Product** | Single product from catalog |
| **Product List** | Multiple products from catalog |

## API Reference

This node integrates with the Hyperflow WhatsApp API. All requests are made to:

```
POST https://messaging.hyperflowapis.global/whatsapp/send-message
```

With authentication via `api-key` header.

## Support

- **Documentation**: https://help.hyperflow.global/docs/whatsapp-api-hyperflow/whatsapp-api-hyperflow
- **Email**: faleconosco@hyperflow.global

## License

MIT