open-index/open-npm huggingface dataset:
npm package: @nazo6/react-component-library-boilerplate
Description: react-component-library-boilerplate
Author: nazo6
Latest version: 0.1.3

# react-component-library-boilerplate

Boilerplate for react library.

## Usage

1. Clone this repository.
2. Install deps.

   ```
   pnpm i
   ```

3. Before starting dev server, you need to execute this command.

   ```
   pnpm build
   ```

4. Start dev server.

   ```
   pnpm start
   ```
npm package: @nazo6/remark-zenn-directive
Description: A remark plugin to support Zenn directives in Markdown.
Author: nazo6
Latest version: 0.1.4

# remark-zenn-directive

[Zennの独自記法](https://zenn.dev/zenn/articles/markdown-guide#zenn-%E7%8B%AC%E8%87%AA%E3%81%AE%E8%A8%98%E6%B3%95)であるディレクティブをHTMLに変換するためのremarkプラグイン。

## Example

```typescript
import { unified } from "unified";
import remarkParse from "remark-parse";
import remarkStringify from "remark-stringify";
import remarkZennDirective from "@nazo6/remark-zenn-directive";

const file = await unified()
  .use(remarkParse)
  .use(remarkZennDirective)
  .use(remarkStringify)
  .process(input);

console.log(String(file));
```

以上のようなコードで、以下のような変換が行われます。

```markdown
::::details title

:::message

Warning

:::

:::message alert

Alert

:::

::::
```

↓

```markdown
<details><summary>title</summary>

<div class="message-warning">

Warning

</div>

<div class="message-alert">

Alert

</div>

</details>
```
npm package: @nbaglivo/ctx
Description: Build curated markdown context files from tagged notes
Author: Nicolas Baglivo
Latest version: 0.1.2


<img src="logo.svg" alt="ctx logo" width="240" />

# ctx

Build curated markdown context files from tagged notes. Scans a directory of markdown files with YAML frontmatter, filters by tags, and produces a single merged context file — ideal for feeding to AI assistants.

## Install

```bash
npm install -g @nbaglivo/ctx
```

Or run directly:

```bash
npx @nbaglivo/ctx --tags job-hunting
```

## Usage

```
ctx --context <name>        Resolve tags from a named context in context.json
ctx --tags <a,b,c>          Comma-separated tags to match
ctx --list                  Show all tags found across files
ctx --list-contexts         Show named contexts from context.json
ctx --dir <path>            Notes directory to scan (default: cwd)
ctx --output <path>         Output file (default: .claude-context.md)
```

Flags can be combined:

```bash
ctx --context job-hunting --tags AI
```

When neither `--context` nor `--tags` is given, only files tagged `global` are included.

## context.json

Place a `context.json` in your notes root to define named contexts:

```json
{
  "contexts": {
    "job-hunting": {
      "tags": ["job-hunting", "projects", "search-profile"]
    },
    "writing": {
      "tags": ["writing-style", "philosophy"]
    }
  }
}
```

Each context maps a name to a set of tags. The format is extensible — future fields like `description`, `output`, or `excludeTags` can be added per context.

## Frontmatter format

Your markdown files should have YAML frontmatter with a `tags` field:

```markdown
---
tags: [job-hunting, projects]
title: Selected Contributions
---

Your content here...
```

Tags can be a YAML array (`[a, b]`) or a single string (`tags: global`).

## Development

```bash
npm install
npm run build        # build with tsup
npm run typecheck    # type-check with tsc
npm run dev          # watch mode
```

## Release

Push a version tag to trigger the release workflow:

```bash
npm version patch
git push --follow-tags
```

This runs CI checks and publishes to npm via GitHub Actions (requires `NPM_TOKEN` secret).
npm package: @nbai/k10s
Description: ## The Name **k10s** works on top of **k8s**, to rollout/uninstall resources. More specifically it utilizes following software:
Author: chang@nextbillion.ai
Latest version: 1.0.19

# Project K10S

## The Name
**k10s** works on top of **k8s**, to rollout/uninstall resources. More specifically it utilizes following software:

 1. [kubectl](https://kubernetes.io/docs/reference/kubectl/)
 2. [helm](https://helm.sh/)
 3. [gsg](https://github.com/nextbillion-ai/gsg)

> Note: you need all these binaries locatable in `PATH` before you can use **k10s**

## The Config
```
basePath: gs://<bucket-and-path-to-k10s>
cluster: <cluster-name>
namespaceVersion: <namespace-version>
globalSpecPlugins: []
```

### basePath
a gcs path that stores all `assets` and `resources`, see `The Concepts` section below.

### cluster
name of the k8s `cluster` for `resource` identification purpose, see `Resource` section under `The Concepts` below.

### namespaceVersion
verison of namespace `asset`, which will be used to create namespace if not exists.

## The Concepts
### Asset
Assets are proper **named and versioned** helm charts.
An Asset is stored in `<base-path>/foreman/operator/assets/<asset-name>/releases/<asset-version>/`
under the above path, there are always 2 files: 

 1. chart.tgz
 2. schema.json

where schema.json is [json schema](https://json-schema.org/) of configurable values of chart.

### Resource
Resources are combination of an `asset` and `values`.
```
asset:
  type: gateway
  release: 1.0.20
app:
  ...
```

> NOTE: object `app` has configurable values of the **asset** (helm chart with specific version) and will be validated against **asset schema**

resources are stored in `<base-path>/foreman/operator/resources/<cluster-name>/<namespace>/<resource-name>.yaml`

## Install and Run
### Install
`yarn global add @nbai/k19s`

### Run
 - make sure your `kubectl` is configured to access the target clsuter
 - create a proper `~/.k10s.yaml` config file.

`k10s rollout <namespace>/<resource-name> -f resource.yaml`
where `resource.yaml` contains the resource definition, if `-f` argument is not supplied, `k10s` will try to download and use from resource gcs path. `k10s` will always upload the resource to its path during rolling out.
`k10s uninstall <namespace>/<resource-name>`
`k10s` will uninstall all k8s objects installed perviously under the <resource-name> in the <namespace>
npm package: @nbai/mcp
Description: NextBillion.ai MCP Server - Provides geolocation, routing, and navigation tools via Model Context Protocol
Author: yun@nextbillion.ai
Latest version: 0.1.0

# NextBillion.ai MCP Server

A Model Context Protocol (MCP) server that provides geolocation, routing, and navigation tools powered by NextBillion.ai APIs.

## Installation

```bash
npx @nbai/mcp
```

## Usage

### With Claude Desktop

Add to your Claude Desktop configuration:

```json
{
  "mcpServers": {
    "nbai": {
      "command": "npx",
      "args": ["@nbai/mcp"],
      "env": {
        "NBAI_API_KEY": "your-api-key-here"
      }
    }
  }
}
```

### Environment Variables

- `NBAI_API_KEY` - Your NextBillion.ai API key (required)

## Available Tools

- **geocode** - Convert addresses to coordinates
- **reverse_geocode** - Convert coordinates to addresses
- **search_places** - Search for places by query
- **place_details** - Get detailed information about a place
- **distance_matrix** - Calculate distances between multiple points
- **directions** - Get routing directions between points
- **navigation** - Get turn-by-turn navigation instructions

## API Key

Get your API key at [NextBillion.ai](https://nextbillion.ai)

## License

MIT
npm package: @nbai/nudge
Description: The linter take an `input directory` and use it to find `package.json` within the input and its parents.
Author: chang
Latest version: 1.0.3

# nudge linter

The linter take an `input directory` and use it to find `package.json` within the input and its parents.

If a `package.json` is located, nudge lint will check for:

- type === "module"
- `standard` is in `dependencies` or `devDependencies`

it will also use `main` attributes defined in `package.json` to find files for validation.
for examples:
-  `main` === `index.js` nudge will scan project root directory, of course ignoring `node_modules`
- `main` === `src/index.js` nudge will scan `src` directory

If everything is fine, nudge will perform the following:

- invoke `standard` to lint the project and quit on error
- analyse `.js` source code files into `AST`s and cross check for cases where `async` functions are called without `await` as this is one most observed mistake programmers make.

## can we beat the default async check?
Yes.
nudge will only check for function imported or declared locally `AS IS`.
```
async function a1(){...}

async function main(){
  a1()//nudge will report error here
  let b = a1
  b()//nudge does not complain this.
}
```
npm package: @nbalazs/angular2-toaster
Description: An Angular Toaster Notification library based on AngularJS-Toaster
Author: Stabzs
Latest version: 17.3.7

Fork of https://github.com/dbonicelli-oa/Angular2-Toaster

| Version | Angular |
|---------|---------|
| 12.x.x  | 12      |
| 13.x.x  | 13      |
| 14.x.x  | 14      |
| 15.x.x  | 15      |
| 16.x.x  | 16      |
| 17.x.x  | 17      |


# Angular2Toaster

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 10.2.0.

## Code scaffolding

Run `ng generate component component-name --project angular2-toaster` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project angular2-toaster`.
> Note: Don't forget to add `--project angular2-toaster` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build angular2-toaster` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build angular2-toaster`, go to the dist folder `cd dist/angular2-toaster` and run `npm publish`.

## Running unit tests

Run `ng test angular2-toaster` to execute the unit tests via [Karma](https://karma-runner.github.io).

## Further help

To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI Overview and Command Reference](https://angular.io/cli) page.