open-index/open-npm huggingface dataset:
npm package: @nexload-sdk/pool-fetch
Description: Advanced, resilient, and modular fetch client for Node.js and Next.js with automatic connection pooling (undici powered)
Author: S. MohammadMahdi Zamanian
Latest version: 2.1.9

# @nexload-sdk/pool-fetch

Fast, resilient, modular fetch client for Node.js — with automatic undici connection pooling, runtime resilience, and full Next.js & SSR compatibility.

## Features

- ⚡ **Connection Pooling**: Automatic per-origin undici pooling for maximum Node.js network efficiency
- 🔄 **Graceful Fallback**: If undici fails, falls back to native fetch API with diagnostic headers
- 🛡 **Resilient by Design**: Handles connection cleanup, process shutdowns, and runtime detection (Next.js, Edge, CI)
- 🧩 **Modular Structure**: Clean layering — base client, pool manager, and undici-powered client
- 🔍 **Zero-Config Observability**: Health snapshot, detailed debug logs (via @nexload-sdk/logger)
- 🧪 **Full TypeScript & Workspace support**: Easy monorepo integration
- 🚀 **Latest standards**: Targets Next.js 15+, TypeScript 5.x, undici ^7.x

## Installation

```sh
pnpm add @nexload-sdk/pool-fetch
# or
npm install @nexload-sdk/pool-fetch
```

## Usage

Basic:

```typescript
import { UndiciHttpClient } from "@nexload-sdk/pool-fetch";

const httpClient = new UndiciHttpClient();

const resp = await httpClient.fetch("https://api.example.com/data", {
  method: "GET",
  headers: { "Authorization": "Bearer TOKEN" }
});

const json = await resp.json();
```

Advanced (Custom pool manager):

```typescript
import { UndiciHttpClient, ConnectionPoolManager } from "@nexload-sdk/pool-fetch";

const poolManager = ConnectionPoolManager.getInstance();

const client = new UndiciHttpClient(poolManager);

await client.fetch("https://microservice.internal/path");
```

## API

### `UndiciHttpClient`

- `.fetch(input, init?)`: Promise<Response>
  - Optimized pipeline: undici first, native fetch fallback
- Injectable poolManager for custom lifetime control

### `ConnectionPoolManager`

- `.getPool(url: string)`
- `.closeAll()`: Closes all pools
- `.getHealth()`: Returns health snapshot

### `BaseHttpClient` (for advanced extension)

- Provides reusable utility methods for HTTP client development

## Best Practices & Notes

- **Runs only in Node.js**: Not designed for browser execution
- **Optimized for SSR/ISR/Backend**
- **No runtime state sharing for Edge or on-demand stateless runners**
- Logs can be controlled via `@nexload-sdk/logger` config

## License

MIT © [S. MohammadMahdi Zamanian](https://mm25zamanian.ir)
npm package: @nexload-sdk/typescript-config
Description: Shared TypeScript configuration presets for the Nexload SDK monorepo.
Latest version: 4.0.0

# @nexload-sdk/typescript-config

Shared TypeScript configuration presets for the Nexload SDK monorepo.

## Presets

- `base.json`: strict shared defaults
- `node.json`: Node.js library/package preset
- `react.json`: React library preset (declaration-only emit)
- `next.json`: Next.js app preset
- `vite.json`: Vite app preset

## Usage

`tsconfig.json` example:

```json
{
  "extends": "@nexload-sdk/typescript-config/node.json",
  "compilerOptions": {
    "outDir": "dist"
  }
}
```

## Notes

- `base.json` enables strict mode and declaration generation defaults
- `react.json` uses `jsx: react-jsx`
- `next.json` is app-oriented (`noEmit: true`)
- `vite.json` is app-oriented (`noEmit: true`, DOM libs enabled)
npm package: @nexly/core
Description: Nexly browser ingest core (sendBeacon, Nexly client, context, engagement)
Latest version: 0.8.2

# @nexly/core

JavaScript SDK for browser-side event ingestion with Nexly. No UI framework required.

For React apps, add **@nexly/react-web**. For Next.js App Router, use **@nexly/next**.

## Install

```bash
npm install @nexly/core
```

## Quick start

```ts
import { Nexly } from '@nexly/core'

const nexly = new Nexly(options)

nexly.pageview()
nexly.event({ name: 'click', type: 'engagement', data: { id: 'x' } })
```

Constructor options use the `NexlyInit` type from the published typings.

### Singleton

When using a provider (`@nexly/react-web` or `@nexly/next`), the client is also available as a singleton — useful for plain functions outside the React tree:

```ts
import { Nexly } from '@nexly/core'

Nexly.getInstance()?.event({ name: 'click', type: 'engagement' })
```

## API

The package ships `.d.ts` files; use your editor or `node_modules` typings for the full export list.

## License

MIT — see [LICENSE](./LICENSE).
npm package: @nexly/next
Description: Next.js App Router helpers for Nexly: route-aware auto pageview on top of @nexly/react-web
Latest version: 0.8.2

# @nexly/next

Next.js App Router helpers for **[@nexly/react-web](https://www.npmjs.com/package/@nexly/react-web)**.

The base `@nexly/react-web` provider fires a pageview once on mount. In Next.js App Router, client navigations do not remount the root layout, so subsequent route changes are missed. `@nexly/next` adds a thin wrapper that listens to `usePathname()` and sends a pageview on every route change.

## Install

```bash
npm install @nexly/next
```

`@nexly/react-web` and `@nexly/core` are installed automatically as transitive dependencies.

## Usage

```tsx
// app/providers.tsx
'use client'

import { NexlyNextProvider } from '@nexly/next'

export function Providers({ children }: { children: React.ReactNode }) {
  return (
    <NexlyNextProvider
      appId={process.env.NEXT_PUBLIC_NEXLY_APP_ID!}
      ingestKey={process.env.NEXT_PUBLIC_NEXLY_INGEST_KEY!}
      autoPageView
      autoEngagement
    >
      {children}
    </NexlyNextProvider>
  )
}
```

```tsx
// app/layout.tsx
import { Providers } from './providers'

export default function RootLayout({ children }: { children: React.ReactNode }) {
  return (
    <html lang="en">
      <body>
        <Providers>{children}</Providers>
      </body>
    </html>
  )
}
```

### Custom events

```tsx
'use client'

import { useNexlyClient } from '@nexly/next'

export function SignUpButton() {
  const client = useNexlyClient()
  return (
    <button onClick={() => client?.event({ name: 'sign_up', type: 'conversion' })}>
      Sign up
    </button>
  )
}
```

### Props

`NexlyNextProvider` accepts the same props as `NexlyProvider` from `@nexly/react-web`:

- **`appId`**, **`ingestKey`** — required credentials.
- **`autoPageView`** (default `false`) — send a pageview on mount and on every client-side route change.
- **`autoEngagement`** (default `false`) — attach scroll, click, visibility, and heartbeat listeners.

### Using outside React (plain functions)

The provider initializes a global singleton. Access it anywhere without hooks:

```ts
import { Nexly } from '@nexly/next'

Nexly.getInstance()?.event({ name: 'cta_click', type: 'conversion' })
```

### Re-exports

`useNexlyClient` and `Nexly` are re-exported for convenience — no need to install the base packages separately.

## License

MIT — see [LICENSE](./LICENSE).
npm package: @nexly/react-web
Description: React bindings for Nexly (@nexly/core): provider, client hook, engagement, optional auto pageview
Latest version: 0.8.2

# @nexly/react-web

React bindings for **[@nexly/core](https://www.npmjs.com/package/@nexly/core)**.

## Install

```bash
npm install @nexly/react-web react
```

`@nexly/core` is installed automatically as a dependency of `@nexly/react-web`.

## Usage

```tsx
import { NexlyProvider, useNexlyClient } from '@nexly/react-web'

function Root() {
  return (
    <NexlyProvider
      appId={appId}
      ingestKey={apiToken}
      autoPageView
      autoEngagement
    >
      <App />
    </NexlyProvider>
  )
}

function App() {
  const client = useNexlyClient()
  if (!client) return <p>Add credentials</p>
  return (
    <button type="button" onClick={() => client.event({ name: 'cta', type: 'conversion' })}>
      Track
    </button>
  )
}
```

### `NexlyProvider` props

- **`appId`**, **`ingestKey`** — required strings (`ingestKey` is the ingest API token; not named `key` because that is reserved in React).
- **`autoPageView`** (default `false`) — when a client exists, send one pageview on mount.
- **`autoEngagement`** (default `false`) — when **`true`** and a client exists (all three strings non-empty after trim), attach engagement listeners; otherwise no-op. Cleanup on unmount or when the client or flag changes.

### `useNexlyClient()`

Returns `Nexly | null` inside a provider (`null` if any credential trims to empty).

### Using outside React (plain functions)

The provider initializes a global singleton. Access it anywhere without hooks:

```ts
import { Nexly } from '@nexly/react-web'

Nexly.getInstance()?.event({ name: 'cta_click', type: 'conversion' })
```

## Next.js

For Next.js App Router (route-aware `autoPageView` on every navigation), use **[@nexly/next](https://www.npmjs.com/package/@nexly/next)** instead.

## License

MIT — see [LICENSE](./LICENSE).
npm package: @nexm-io/bitsnap
Description: Metamask snap to manage your bitcoin
Latest version: 0.1.8

# bitsnap [![0.0.1](https://badge.fury.io/js/bitsnap.png)](https://badge.fury.io/js/bitsnap)

![./images/icon.svg](./images/icon.svg)

`bitsnap` allows users to manage Bitcoin directly within the MetaMask interface without having to wrap tokens.
`bitsnap` is currently live on [Metamask](https://metamask.io/).

##

### MetaMask Snaps Introduction
Snap is a system that allows developers to build and expand the capabilities of MetaMask safely. It is a program run in an isolated environment with limited capabilities that can customize and modify MetaMask's wallet experience for end users. For example, a snap can add new APIs to MetaMask, thus adding support for different blockchains or change existing functionalities using internal APIs.

Additional information can be found [here](https://docs.metamask.io/guide/snaps.html).


##

### `bitsnap` Integration
If you would like to integrate `bitsnap` into your dapp, you can make use of our npm. Refer to the following document [here](https://github.com/nexm-io/bitsnap/tree/master/docs).

##

### How to run `bitsnap` on a wallet locally

```shell
yarn build && yarn test:snap
```

## Audit Report

Inprogress


## License

This project is dual-licensed under Apache 2.0 and MIT terms:
- [Apache License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0)
- [MIT license](http://opensource.org/licenses/MIT)
npm package: @nexm-io/reservoir-kit-ui
Description: ReservoirKit is the official frontend kit to get you started building dApps with the ReservoirProtocol.
Author: Reservoir Protocol
Latest version: 0.0.7

<h1 align="center">Reservoir UI Kit</h1>

## Installation

Use your favorite package manager to install reservoir-kit-ui:

`yarn add @reservoir0x/reservoir-kit-ui`

Make sure to install the required peer dependencies:

`yarn add wagmi viem react react-dom`

For more detailed installation instructions please refer to our [installation guide](https://docs.reservoir.tools/reference/installing-reservoirkit).

## Usage

Visit our [docs](https://docs.reservoir.tools/reference/reservoirkit) to learn more about how to use ReservoirKit.
npm package: @nexm-io/reservoir-sdk
Description: An SDK that can be used in any javascript/typescript context to easily interact with Reservoir liquidity APIs
Author: Reservoir Protocol
Latest version: 0.0.2

<h1 align="center">Reservoir SDK</h1>

## Installation

Use your favorite package manager to install the reservoir-sdk:

`yarn add @reservoir0x/reservoir-sdk`

Make sure to install the required peer dependencies:

`yarn add viem`

For more detailed installation instructions please refer to our [installation guide](https://docs.reservoir.tools/reference/reservoir-sdk-jstsnode).

## Usage

Visit our [docs](https://docs.reservoir.tools/reference/reservoir-sdk-jstsnode#configuring-the-reservoir-sdk) to learn more about how to use the Reservoir SDK.
npm package: @nexmoe/hexo-renderer-inferno
Description: Inferno.js JSX renderer for Hexo
Author: ppoffice
Latest version: 0.2.1

# [Inferno.js](https://infernojs.org/) renderer

[![test](https://github.com/nexmoe/hexo-renderer-inferno/workflows/Testing/badge.svg)](https://github.com/hexojs/hexo-renderer-inferno/actions?query=workflow%3ATesting)
[![npm package](https://badge.fury.io/js/hexo-renderer-inferno.svg)](https://www.npmjs.com/package/@nexmoe/hexo-renderer-inferno)
[![coverage](https://img.shields.io/coveralls/hexojs/hexo-renderer-inferno.svg)](https://coveralls.io/r/nexmoe/hexo-renderer-inferno?branch=master)

## Install

```sh
$ npm install hexo-renderer-inferno --save
```

## Examples

Please refer to

- [test/fixture](https://github.com/nexmoe/hexo-renderer-inferno/tree/master/test/fixture)

## Note

Change from <https://github.com/hexojs/hexo-renderer-inferno>
And add a feature that when you use `hexo server` to preview your blog, this render will automatically render the page when you change the file. Don't need to restart the server.