open-index/open-npm huggingface dataset:
npm package: @metamorph/logtape
Description: Simple logging library with zero dependencies for Deno/Node.js/Bun/browsers
Author: Hong Minhee
Latest version: 0.10.3

<!-- deno-fmt-ignore-file -->

# LogTape

[![JSR][JSR badge]][JSR]
[![npm][npm badge]][npm]
[![GitHub Actions][GitHub Actions badge]][GitHub Actions]
[![Codecov][Codecov badge]][Codecov]

LogTape is a logging library for JavaScript and TypeScript. It provides a
simple and flexible logging system that is easy to use and easy to extend.
The highlights of LogTape are:

- _Zero dependencies_: LogTape has zero dependencies. You can use LogTape
  without worrying about the dependencies of LogTape.

- _[Library support]_: LogTape is designed to be used in libraries as well
  as applications. You can use LogTape in libraries to provide logging
  capabilities to users of the libraries.

- _[Runtime diversity]_: LogTape supports Deno, Node.js, Bun, edge functions,
  and browsers. You can use LogTape in various environments without
  changing the code.

- _[Hierarchical categories]_: LogTape uses a hierarchical category system
  to manage loggers. You can control the verbosity of log messages by
  setting the log level of loggers at different levels of the category
  hierarchy.

- _[Template literals]_: LogTape supports template literals for log messages.
  You can use template literals to log messages with placeholders and
  values.

- _[Dead simple sinks]_: You can easily add your own sinks to LogTape.

![](./screenshots/web-console.png)
![](./screenshots/terminal-console.png)

[JSR]: https://jsr.io/@logtape/logtape
[JSR badge]: https://jsr.io/badges/@logtape/logtape
[npm]: https://www.npmjs.com/package/@logtape/logtape
[npm badge]: https://img.shields.io/npm/v/@logtape/logtape?logo=npm
[GitHub Actions]: https://github.com/dahlia/logtape/actions/workflows/main.yaml
[GitHub Actions badge]: https://github.com/dahlia/logtape/actions/workflows/main.yaml/badge.svg
[Codecov]: https://codecov.io/gh/dahlia/logtape
[Codecov badge]: https://codecov.io/gh/dahlia/logtape/graph/badge.svg?token=yOejfcuX7r
[Library support]: https://logtape.org/manual/library
[Runtime diversity]: https://logtape.org/manual/install
[Hierarchical categories]: https://logtape.org/manual/categories
[Template literals]: https://logtape.org/manual/start#how-to-log
[Dead simple sinks]: https://logtape.org/manual/sinks

## Installation

LogTape is available on [JSR] and [npm]. You can install LogTape for various
JavaScript runtimes and package managers:

```sh
deno add @logtape/logtape  # for Deno
npm  add @logtape/logtape  # for npm
pnpm add @logtape/logtape  # for pnpm
yarn add @logtape/logtape  # for Yarn
bun  add @logtape/logtape  # for Bun
```

See also the [installation manual][Runtime diversity] for more details.

## Docs

The docs of LogTape is available at <https://logtape.org/>.
For the API references, see <https://jsr.io/@logtape/logtape>.
npm package: @metamorph/postgraphile-nest
Description: Nestjs module for incorporating PostGraphile into your application
Author: Alex Aldana
Latest version: 1.0.6

<p align="center">
<a href="https://www.graphile.org/postgraphile/" target="blank"><img width="120" height="120" title="PostGraphile logo" src="https://cdn.rawgit.com/graphile/graphile.github.io/a6225f8c3052df5c276ecef28aeb0cade1aec16a/logos/postgraphile.optimized.svg" /></a>
  <img src="https://svgshare.com/i/Ckm.svg" />
  <a href="http://nestjs.com/" target="blank"><img src="https://nestjs.com/img/logo_text.svg" width="320" alt="Nest Logo" /></a>
</p>

# PostGraphile for Nestjs

[![Build Status](https://travis-ci.com/alex-ald/postgraphile-nest.svg?branch=master)](https://travis-ci.com/alex-ald/postgraphile-nest)
[![Coverage Status](https://coveralls.io/repos/github/alex-ald/postgraphile-nest/badge.svg)](https://coveralls.io/github/alex-ald/postgraphile-nest)
[![npm version](https://badge.fury.io/js/postgraphile-nest.svg)](https://badge.fury.io/js/postgraphile-nest)

## Description

A module for [Nest](https://github.com/nestjs/nest) that allows you to easily integrate [PostGraphile](https://www.graphile.org/postgraphile/) into your application.

## Installation

```bash
$ npm i --save postgraphile-nest postgraphile
```

## Documentation

Visit our [Wiki](https://github.com/alex-ald/postgraphile-nest/wiki) for documentiation and examples.

## Thanks

The maintainer of this project is [Alex Aldana](https://github.com/alex-ald)!

## License

[MIT licensed](LICENSE)
npm package: @metamorphik/react-scoped-events
Description: Scoped Event system with named, hierarchical event horizons for React
Author: Metamorphik
Latest version: 1.0.10

# react-scoped-events

Scoped, hierarchical event system for React — think of it like **pub/sub with boundaries**.  
You define **event horizons** (scopes) in your component tree, and decide whether an event stays local, bubbles to a project, or goes global.

---

## ✨ Features

- 🔹 **Scoped events** — emit/listen inside a local horizon only.  
- 🔹 **Named horizons** — `global`, `project:Earth`, `module:42`, etc.  
- 🔹 **Nested providers** — project inside global, module inside project.  
- 🔹 **Strict & safe APIs**  
  - strict hooks throw at render if you ask for an out-of-scope horizon.  
  - safe hooks resolve at call time and tell you if horizon is missing.  
- 🔹 **Lightweight** — no external deps beyond React.  

---

## 🎮 Live Demo

Try it instantly on CodeSandbox:

[![Play on CodeSandbox](https://img.shields.io/badge/Play%20on-CodeSandbox-151515?logo=codesandbox&logoColor=white)](https://codesandbox.io/p/sandbox/github/metamorphik/metamorphik-dev-tools/tree/main/packages/react-scoped-events/examples/org)

---

## 🚀 Quickstart

Install:
```bash
npm install react-scoped-events
```

Wrap your app in a top-level horizon:
```tsx
import {
  EventHorizonProvider,
  useEmitToEventHorizon,
  useOnEvent
} from "react-scoped-events";

function SenderPanel() {
  const emit = useEmitToEventHorizon();
  return (
    <button onClick={() => emit("hello", { msg: "Hi there" })}>
      Send hello
    </button>
  );
}

function ReceiverPanel() {
  useOnEvent("hello", (payload) => {
    alert("Got event: " + payload.msg);
  });
  return <div>👂 Listening for hello…</div>;
}

export default function App() {
  return (
    <EventHorizonProvider name="global">
      <div style={{ display: "flex", gap: 20 }}>
        <SenderPanel />
        <ReceiverPanel />
      </div>
    </EventHorizonProvider>
  );
}
```

Clicking the button in **SenderPanel** will trigger an alert in **ReceiverPanel**.

---

## 🧭 API overview

- **Provider**
  - `<EventHorizonProvider name="...">` — defines a scope.
- **Emit**
  - `useEmitToEventHorizon()` — emit in the current horizon.
  - `useEmitToNamedEventHorizon("global")` — emit to one of the enclosing horizon.
  - `useEmitToNamedEventHorizonSafe("foo")` — safe variant (returns `{ok,error}`).  
- **Listen**
  - `useOnEvent(type, handler)` — subscribe in current horizon.
  - `useOnNamedEventHorizon("global", type, handler)` — subscribe in one of the enclosing horizon.
  - `useOnNamedEventHorizonSafe("foo", type, handler)` — safe, silent if not visible.
- **HOC**
  - `withEventHorizonScope(Component)` — wrap any component to make it define a horizon if it receives `definesHorizon`.

---

## 📦 Why not Zustand?

We started with Zustand, but quickly realized horizons were naturally modeled by **React Context**:
- Clear ownership boundaries.
- Works without extra dependencies.
- Easier nesting & naming.

---

## 📝 License

MIT © 2025 Metamorphik
npm package: @metamorphosisjs/metamorphosis
Description: Lightweight JS framework for deploying Kakfa workers
Author: Brad Ash
Latest version: 0.7.0

# Metamorphosis

A super dope, pluggable NodeJS Kafka Framework for building Kafka workers like consumers, producers and stream processors.

## Requirements

-   Kafka cluster either BYO or run the install scripts below for a test cluster
-   Node 12.x
-   Yarn or NPM package managers (this project defaults to Yarn)
-   Docker (if testing without Kafka cluster)
-   Docker Compose

## Install

```
yarn install
```

## Config

Copy example `.env` and replace values with your own

```
cp .env.example .env
```

| Option               | Description                                                                                              | Default                      |
| -------------------- | -------------------------------------------------------------------------------------------------------- | ---------------------------- |
| KAFKA_BROKERS        | Comma-delimited string of brokers e.g. `10.10.10.1:9092,10.10.10.2:9092,...`                             | localhost:9092               |
| KAFKA_CLIENT_ID      | Unique ID used by consumers and producers in this app                                                    | metamorphosis                |
| KAFKA_TOPIC_CONSUMER | Topic to read from for a single-topic consumer app                                                       | metamorphosis.test           |
| KAFKA_TOPIC_PRODUCER | Topic to write to for a single-topic producer app                                                        | metamorphosis.test           |
| CONSUMER_GROUP_ID    | Group name responsible for tracking offsets on a consumer. This should be unique for every consumer app. | metamorphosis-consumer-group |

# Usage

See `/examples` folder for specific sample applications

## Services

Allow for consistent setup processing of Kafka topics using common tools for repeated tasks.

### Default Consumer

Pass a callback and perform work on each message in a single topic

### Default Producer

Generate a client connection with the ability to write messages into a Kafka topic.

### Webhook Producer

Define an endpoint to consume payloads and write to a Kafka topic.

### Database Adapter

Pass a database adapter into any service for reading and writing to a database.

# Testing

**Install either the `Kitchen Sink` package or pick and choose from the items below.**

## A) Kitchen Sink

Install everything needed to test Kafka and all database adapters

```sh
yarn setup:all
```

## B) Choose your components

You can use Kafka or database environments you are already running by setting them in the `.env` or the `config/{environment}.js` file

### Kafka Cluster

Setup local Kafka cluster with Zookeper and SSL/SASL connection

```sh
yarn kafka:start
```

### MySQL Database

Setup MySQL 8 database with sample schema and table

```sh
yarn mysql:start
```

## Run Mocha Tests

Run all tests from root of project. You can adjust the timeout and other settings in `.mocharc.json` and `test/config.js` as well as the standard application config.

```sh
yarn test
```
npm package: @metanames/sdk
Description: Meta Names SDK
Author: Yeboster
Latest version: 6.3.1

# Meta Names SDK

The Meta Names SDK library is a useful resource that allows for smooth communication with the Meta Names domain name system.

This library is specifically designed to work with the Partisia Blockchain, making it simple to integrate and manage DNS features. With this library, you can easily register a domain, handle domain records, and ensure seamless domain name resolution.

## Documentation
The documentation for the project can be found in the [official docs](https://docs.metanames.app) and the [auto generated documentation](https://metanames.github.io/sdk/).
npm package: @metaoslabs/cli
Description: METAOS CLI for agent development and testing
Author: METAOS LABS
Latest version: 1.0.0

# METAOS CLI

Command-line interface for METAOS agent development and testing.

## Installation

```bash
cd cli
npm link
```

## Usage

### Initialize a project

```bash
metaos init
```

This creates a `metaos.json` file:

```json
{
  "backendUrl": "http://localhost:3001",
  "authToken": null,
  "agents": []
}
```

### Add your JWT token

Get your token from the dashboard at `http://localhost:3000/login`, then add it to `metaos.json`:

```json
{
  "backendUrl": "http://localhost:3001",
  "authToken": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...",
  "agents": []
}
```

### Run an agent with an intent

```bash
metaos agent run travel --intent notes.write "Trip to Paris"
```

This will:
1. Call the backend Tool Gateway at `/v1/tools/call` with your JWT token
2. Execute the `storage.write` tool (if capabilities are granted)
3. Display the result

## Configuration

Edit `metaos.json` to point to your backend:

```json
{
  "backendUrl": "https://metaos-backend.onrender.com/v1",
  "authToken": "your-jwt-token-from-login",
  "agents": []
}
```

## Authentication

The CLI uses JWT tokens for authentication. Before using agent commands:

1. Sign up at the backend: `POST /v1/auth/signup`
2. Get your token from the response
3. Add it to `metaos.json` as `authToken`

All API calls will include `Authorization: Bearer <token>` header.

## Development

The CLI currently supports:
- `storage.write` tool for writing notes
- More tools coming soon!

## Testing with Local Backend

1. Start your NestJS backend: `cd backend && npm run start:dev`
2. Init CLI: `metaos init`
3. Run agent: `metaos agent run travel --intent notes.write "Hello backend"`