open-index/open-npm huggingface dataset:
npm package: @org.ai/types
Description: Shared type definitions for AI primitives packages
Latest version: 2.1.3

# @org.ai/types

**You're building AI-powered applications, but TypeScript keeps fighting you.** Your AI functions return `any`, your workflow contexts are untyped blobs, and refactoring means breaking things you cannot see.

`@org.ai/types` gives you the type safety you need to build AI applications with confidence.

## The Problem

```typescript
// Without types: runtime errors waiting to happen
const result = await aiFunction(input) // What does this return?
workflow.on('event', (data) => {       // What's in data?
  workflow.state.user = data           // Is this right?
})
```

## The Solution

```typescript
import type { AIFunctionType, WorkflowContextType, EventHandlerType } from '@org.ai/types'

// With types: autocomplete, refactoring, and compile-time safety
const summarize: AIFunctionType<Summary, Document> = async (doc) => {
  // TypeScript knows doc is Document, return must be Summary
}

const handler: EventHandlerType<void, UserEvent> = (data, ctx) => {
  // data is UserEvent, ctx has full WorkflowContextType methods
  ctx.send('notification', { userId: data.userId })
}
```

## Quick Start

### 1. Install

```bash
npm install @org.ai/types
```

### 2. Import the types you need

```typescript
import type {
  AIFunctionType,
  EventHandlerType,
  WorkflowContextType,
  RelationshipOperatorType,
  ParsedFieldType,
} from '@org.ai/types'
```

### 3. Build with confidence

Your IDE now understands your AI code. Refactor fearlessly.

## Type Reference

| Type | Purpose |
|------|---------|
| `AIFunctionType<TOutput, TInput, TConfig>` | Generic AI function with output-first parameter order |
| `EventHandlerType<TOutput, TInput>` | Workflow event handlers with typed context |
| `WorkflowContextType` | The `$` workflow proxy with `send`, `try`, `do`, `on`, `every` |
| `RelationshipOperatorType` | Database relationship operators (`->`, `~>`, `<-`, `<~`) |
| `ParsedFieldType` | Schema field definitions with relationship metadata |

## Why Output-First Generics?

Just like `Promise<T>` puts the important part first, `AIFunctionType<TOutput>` leads with what matters most:

```typescript
// Natural reading order: "an AI function that returns a Summary"
type Summarizer = AIFunctionType<Summary>

// vs the awkward alternative
type Summarizer = AIFunctionType<Document, Summary>  // Wait, which is which?
```

## Part of the org.ai Ecosystem

This package provides shared types for:
- [@org.ai/ai-functions](../ai-functions) - AI function primitives
- [@org.ai/ai-workflows](../ai-workflows) - Workflow orchestration
- [@org.ai/ai-database](../ai-database) - AI-native database with relationships
- And [more packages](../) in the org.ai monorepo

## License

MIT
npm package: @org.slashlib/ng-providers-mat-svg
Description: slashlib.org - @angular/material provider for loading and displaying svg
Author: Dirk Brenckmann
Latest version: 0.1.0

## angular scalable vector graphics (svg) provider ##

Provides inline scalable vector graphics for @angular/material projects.

This projects SVG graphics are provided by:
* https://material.io/tools/icons/?style=baseline ([Apache License V. 2.0](https://www.apache.org/licenses/LICENSE-2.0.txt))<br />
  https://github.com/google/material-design-icons/

## building the library ##

* Browse https://github.com/org-slashlib/ng-project-template and download (no fork required!) a zip/tar of the the project template.
* Run <code> npm install </code> in the project template folder.
* Download or fork this project and link it into the templates subfolder.
* Run: <code> grunt </code>
* Change to build directory: <code> cd build </code>
* Call <code> ng build </code>
* Change to dist directory: <code> npm pack </code>
* <code> npm install path/to/@org.slashlib-ng-providers-mat-svg-&lt;version&gt;.tgz</code>

## installing ##

This guide assumes, that you are familiar with the use of npm.  

Download <code>org.slashlib-ng-providers-mat-svg-&lt;version&gt;.tgz</code><br />
and install <code> npm install path/to/org.slashlib-ng-providers-mat-svg-&lt;version&gt;.tgz</code>

or

<code>npm install @org.slashlib/ng-providers-mat-svg --save-dev</code>

## usage ##

Add the following lines to your app module.

```javascript
import { LocalSVGProvider }           from "@org.slashlib/ng-providers-mat-svg";
import { svgProviderFactory }         from "@org.slashlib/ng-providers-mat-svg";

@NgModule({
  imports:      [ ... ],
  declarations: [ ... ],
  providers:    [
    LocalSVGProvider,                 // inline loading of svg (icons))
    { provide:    APP_INITIALIZER,
      useFactory: svgProviderFactory,
      deps:       [LocalSVGProvider],
      multi:      true }              // load svg (icons) on app start
  ],
  bootstrap:    [ ... ]
})
export class AppModule { }

```

In your components html, you can now use all icons provided in
version 2.2.0 of https://material.io/tools/icons/?style=baseline

```html
<mat-icon svgIcon="svg_icon_name"></mat-icon>
```
npm package: @org.slashlib/ng-services-core
Description: slashlib.org core services for angular6/7
Author: Dirk Brenckmann
Latest version: 0.1.1

## org.slashlib core services for angular ##

Basic services for reuse with angular6/7 projects

## getting started ##

This guide assumes, that you are familiar with the use of npm.  

Download <code>org.slashlib-ng-services-core-&lt;version&gt;.tgz</code> or

<code>npm install @org.slashlib/ng-services-core --save-dev</code>

## building the library ##

* Browse https://github.com/org-slashlib/ng-project-template and download (no fork required!) a zip/tar of the the project template.
* Run <code> npm install </code> in the project template folder.
* Download or fork this project and link it into the templates subfolder.
* Run: <code> grunt </code>
* Change to build directory: <code> cd build </code>
* Call <code> ng build </code>
* Change to dist diectory: <code> npm pack </code>
* <code> npm install path/to/@org.slashlib-ng-services-core-<version>.tgz</code>
npm package: @org21/n8n-nodes-org21
Description: n8n community node that sniffs workflow metadata, logs, timing, and errors, then triggers a sub-flow via webhook or n8n API.
Author: Org21
Latest version: 0.1.0

# @org21/n8n-nodes-org21

n8n community node that **sniffs workflow metadata, logs, timing, and errors** from any flow — then triggers a sub-flow via **webhook** or **n8n API**.

Use it for observability, auditing, debugging, or orchestrating complex multi-workflow pipelines.

## Installation

### Community Nodes (recommended)

1. Go to **Settings > Community Nodes** in your n8n instance
2. Select **Install a community node**
3. Enter `@org21/n8n-nodes-org21`
4. Agree to the risks and click **Install**

### Manual

```bash
cd ~/.n8n/nodes
npm install @org21/n8n-nodes-org21
```

## Nodes

### Flow Sniffer

Drop this node into any workflow to capture execution data and trigger a sub-flow.

#### What it captures

| Toggle | Data | Default |
|--------|------|---------|
| **Metadata** | Workflow ID/name, execution ID, node name, timestamp | On |
| **Item Data** | The actual JSON items passing through the node | On |
| **Timing** | Execution timing, input/output item counts | On |
| **Errors** | Error details from items with errors | On |
| **Environment** | Process environment variables (filtered for safety) | Off |

#### Trigger modes

- **Webhook POST** — POST sniffed data to any URL (typically a sub-flow's Webhook trigger)
- **n8n API** — Trigger a specific workflow via the n8n REST API (requires API key)

#### Options

- **Pass Through** — When enabled (default), original items pass through unchanged so the main flow continues normally. When disabled, the node outputs the sniffed payload instead.
- **Additional Headers** — Add custom HTTP headers to the trigger request.

## Credentials

### Org21 API (n8n API Key)

Required only when using **n8n API** trigger mode. Enter your n8n instance API key.

Generate one at: **Settings > API > Create API Key** in your n8n instance.

## Example use cases

1. **Audit trail** — Sniff every execution and POST to a logging sub-flow that writes to a database
2. **Error monitoring** — Capture errors and trigger an alerting workflow (Slack, email, PagerDuty)
3. **Pipeline orchestration** — Chain workflows together by sniffing completion data and triggering the next stage
4. **Cost tracking** — Capture execution metadata and aggregate it in a reporting workflow

## Compatibility

- n8n >= 1.0.0
- Node.js >= 22

## License

MIT