open-index/open-npm huggingface dataset:
npm package: @sjvair/web-widget
Description: SJVAir's monitor widget for the web!
Latest version: 2.0.1

# The Official Web Widget for [SJVAir.com](https://www.sjvair.com)

## Accessing

- #### Embedding (Recommended)

    Our widget can be easily embedded into a website by utilizing an `iframe`. You can use the iframe code below, which includes the recommended attributes and styles, replacing `[ MONITOR_ID ]` with the desired monitor ID:  
`<iframe src="https://www.sjvair.com/widget/#/[ MONITOR_ID ]" frameborder="0" allowtransparency="true" style="overflow: hidden; width: 290px; height: 390px;"></iframe>`

- #### Self Host (Build From Source)

    Follow the [Getting Started](#getting-started) section to verify the build is working locally, then run:

    ```
    npm run build
    ```

    The production ready bundles will be located under the `dist/` directory.

## Development

#### Prerequisites

Working on this widget requires access to the SVJAir API. Make sure you have followed the [setup guide](https://github.com/SJVAir/sjvair.com#setup-guide) for getting the sjvair.com development server up and running. These instructions assume you are using the default settings for the sjvair.com development server.

#### Getting Started

1. Clone this repo and install the project dependencies:  

    ```
    git clone https://github.com/SJVAir/web-widget.git
    cd web-widget
    npm i
    ```

2. Create your `.env` file  

    ```
    cp .env.template .env
    ```

3. Start the dev server:  
    `npm run dev`

#### Recommended IDE Setup

[VS Code](https://code.visualstudio.com/) + [Svelte](https://marketplace.visualstudio.com/items?itemName=svelte.svelte-vscode).
npm package: @sjwie/gemini-cli-mcp
Description: MCP server for delegating tasks to Gemini CLI
Latest version: 0.1.1

# @sjwie/gemini-cli-mcp

MCP server for delegating tasks to Gemini CLI. This allows you to invoke Gemini CLI agent capabilities from other MCP-enabled tools.

## Prerequisites

- [Gemini CLI](https://github.com/google-gemini/gemini-cli) must be installed and configured
- The `gemini` command must be available in your PATH

## Installation

### For Gemini CLI

Add to your `~/.gemini/settings.json`:

```json
{
  "mcpServers": {
    "gemini-delegate": {
      "command": "bunx",
      "args": ["@sjwie/gemini-cli-mcp@latest"]
    }
  }
}
```

### For Cursor

Add to your `~/.cursor/mcp.json`:

```json
{
  "mcpServers": {
    "gemini-delegate": {
      "command": "bunx",
      "args": ["@sjwie/gemini-cli-mcp@latest"],
      "env": {
        "GEMINI_CLI_PATH": "/path/to/gemini"
      }
    }
  }
}
```

### For Claude Code

Add to your Claude Code MCP configuration:

```json
{
  "mcpServers": {
    "gemini-cli-mcp": {
      "command": "bunx",
      "args": ["@sjwie/gemini-cli-mcp@latest"]
    }
  }
}
```

### Environment Variables

| Variable | Description |
|----------|-------------|
| `GEMINI_CLI_PATH` | Path to the `gemini` executable. Use when `gemini` is not in your PATH (e.g. `/path/to/gemini` or `C:\path\to\gemini.cmd` on Windows). |

## Usage

Once installed, you can use the `task` tool to delegate tasks to Gemini CLI:

```
@gemini-delegate task("Create a Python script that prints hello world", cwd="/path/to/project")
```

### Parameters

- `task` (required): The task description to delegate to Gemini CLI
- `cwd` (required): The working directory where Gemini CLI should run (must be an absolute path)
- `historyId` (optional): Continue from a previous session (use the `session_id` from a previous response)

### Allowed Tools

The following gemini-cli tools are automatically allowed and will run without confirmation:

- `read_file` - Reading file contents
- `write_file` - Creating or modifying files
- `edit` - Editing files
- `run_shell_command` - Executing shell commands
- `web_fetch` - Retrieving content from URLs
- `google_web_search` - Searching the web
- `save_memory` - Persisting information across sessions
- `write_todos` - Managing task lists

## How it Works

This MCP server wraps the Gemini CLI and allows other tools to programmatically invoke it. When you call the `task` tool:

1. The MCP server spawns the `gemini` CLI with your task
2. It uses `--output-format stream-json` to get structured responses
3. The response is streamed back through the MCP protocol
4. The conversation session ID is preserved for follow-up tasks

### Response Format

The tool returns a JSON object with:

- `result`: The assistant's response text
- `session_id`: The session ID for continuing the conversation
- `total_cost_usd`: The total cost of the request (if available)

## Development

```bash
# Install dependencies
bun install

# Build
bun run build

# Test locally
bun run dist/index.js
```
npm package: @sjzx/projectx-ui
Description: ## Project setup ``` npm install ```
Latest version: 0.0.13

# projectx-ui

## Project setup
```
npm install
```

### Compiles and hot-reloads for development
```
npm run serve
```

### Compiles and minifies for production
```
npm run build
```

### Lints and fixes files
```
npm run lint
```

### Customize configuration
See [Configuration Reference](https://cli.vuejs.org/config/).
npm package: @sk-framework/sk-core
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 11.2.4.
Latest version: 0.0.2

# SkCore

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

## Code scaffolding

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

## Build

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

## Publishing

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

## Running unit tests

Run `ng test sk-core` 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.
npm package: @sk-framework/sk-lib
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 11.2.4.
Latest version: 0.0.3

# SkLib

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

## Code scaffolding

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

## Build

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

## Publishing

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

## Running unit tests

Run `ng test sk-lib` 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.