open-index/open-npm huggingface dataset:
npm package: @nirbanroy/n8n-nodes-nasapics
Description: This is a test node for n8n that fetches NASA pictures.
Author: nirban
Latest version: 0.1.0

![Banner image](https://user-images.githubusercontent.com/10284570/173569848-c624317f-42b1-45a6-ab09-f0ea3c247648.png)

# n8n-nodes-starter

This repo contains example nodes to help you get started building your own custom integrations for [n8n](https://n8n.io). It includes the node linter and other dependencies.

To make your custom node available to the community, you must create it as an npm package, and [submit it to the npm registry](https://docs.npmjs.com/packages-and-modules/contributing-packages-to-the-registry).

If you would like your node to be available on n8n cloud you can also [submit your node for verification](https://docs.n8n.io/integrations/creating-nodes/deploy/submit-community-nodes/).

## Prerequisites

You need the following installed on your development machine:

* [git](https://git-scm.com/downloads)
* Node.js and npm. Minimum version Node 20. You can find instructions on how to install both using nvm (Node Version Manager) for Linux, Mac, and WSL [here](https://github.com/nvm-sh/nvm). For Windows users, refer to Microsoft's guide to [Install NodeJS on Windows](https://docs.microsoft.com/en-us/windows/dev-environment/javascript/nodejs-on-windows).
* Install n8n with:
  ```
  npm install n8n -g
  ```
* Recommended: follow n8n's guide to [set up your development environment](https://docs.n8n.io/integrations/creating-nodes/build/node-development-environment/).

## Using this starter

These are the basic steps for working with the starter. For detailed guidance on creating and publishing nodes, refer to the [documentation](https://docs.n8n.io/integrations/creating-nodes/).

1. [Generate a new repository](https://github.com/n8n-io/n8n-nodes-starter/generate) from this template repository.
2. Clone your new repo:
   ```
   git clone https://github.com/<your organization>/<your-repo-name>.git
   ```
3. Run `npm i` to install dependencies.
4. Open the project in your editor.
5. Browse the examples in `/nodes` and `/credentials`. Modify the examples, or replace them with your own nodes.
6. Update the `package.json` to match your details.
7. Run `npm run lint` to check for errors or `npm run lintfix` to automatically fix errors when possible.
8. Test your node locally. Refer to [Run your node locally](https://docs.n8n.io/integrations/creating-nodes/test/run-node-locally/) for guidance.
9. Replace this README with documentation for your node. Use the [README_TEMPLATE](README_TEMPLATE.md) to get started.
10. Update the LICENSE file to use your details.
11. [Publish](https://docs.npmjs.com/packages-and-modules/contributing-packages-to-the-registry) your package to npm.

## More information

Refer to our [documentation on creating nodes](https://docs.n8n.io/integrations/creating-nodes/) for detailed information on building your own nodes.

## License

[MIT](https://github.com/n8n-io/n8n-nodes-starter/blob/master/LICENSE.md)
npm package: @nirbaram/orca-cli
Description: LLM-powered deployment troubleshooting assistant for Orca
Author: Syntero
Latest version: 1.0.0
Deprecated: Moved to @syntero/orca-cli

# Orca Deployment Assistant (TypeScript CLI)

LLM-powered deployment troubleshooting assistant for Orca.

## Installation

### Global Install

```bash
# Install globally
npm install -g orca-deploy-assistant

# Run
orca-deploy-assistant
```

### Using npx

```bash
npx orca-deploy-assistant
```

### Local Development

```bash
# Install dependencies
npm install

# Build
npm run build

# Run
npm start
```

## Usage

```bash
# Interactive mode (default)
orca-deploy-assistant

# Single query
orca-deploy-assistant "Why is the backend restarting?"

# Force interactive mode
orca-deploy-assistant --interactive

# Configure credentials
orca-deploy-assistant --login

# Specify deployment directory
orca-deploy-assistant -d /path/to/deployment
```

## Commands (Interactive Mode)

| Command | Description |
|---------|-------------|
| `/login` | Configure LLM provider credentials |
| `/settings` | Show current settings (secrets masked) |
| `/models` | List available models |
| `/model` | Change model for current provider |
| `/provider <name>` | Switch provider (anthropic, openai, azure) |
| `/clear` | Clear conversation history |
| `/help` | Show available commands |
| `quit`, `exit` | Exit the assistant |

## Supported Providers

- **Anthropic** (Claude) - Default
- **OpenAI** (GPT)
- **Azure OpenAI**

## Features

- Multi-provider support with easy switching
- Streaming responses
- Tool use for deployment inspection:
  - `run_command` - Execute shell commands
  - `read_file` - Read configuration files
  - `list_directory` - List directory contents
  - `inspect_env` - View .env with secrets redacted
  - `query_database` - Read-only SQLite queries
  - `search_logs` - Search container logs
  - `check_container_health` - Container health reports
- Settings persistence (~/.deployment_assistant.json)
- Cancellation with 'q' or Ctrl+C

## Configuration

Settings are stored in `.deployment_assistant.json` in the deployment directory. The file is automatically created on first run and contains:

- Provider selection
- API keys (stored locally)
- Model preferences

## Development

```bash
# Install dependencies
npm install

# Build TypeScript
npm run build

# Run development
npm run dev
```

## Requirements

- Node.js 18+
- Docker (for container inspection tools)
- SQLite (via better-sqlite3)

## Environment Variables

- `DEPLOYMENT_DIR` - Override the deployment directory path

## License

MIT
npm package: @nire0510/jdom
Description: Transform web pages DOM to JSON and query it with JMESPath
Author: Nir Elbaz
Latest version: 1.0.3

# jsdom
Transform web pages DOM to JSON and query it with JMESPath.

## Installation
`npm i @nire0510/jdom`

## Usage
```javascript
import jdom from '@nire0510/jdom';

const output = await jdom(params);

console.log(output, null, 2);
```

### params
```
{
  jmespath?: string | { [key: string]: string },;
  timeout?: number;
  url: string;
  viewport?: {
    width: number;
    height: number;
  };
  waitForSelector?: string;
  waitUntil: 'load' | 'domcontentloaded' | 'networkidle0' | 'networkidle2';
}
```
* `jmespath` (string | object, optional) - The jmespath filter to apply on the DOM before returning the output. It could be either a single string filter or a dictionary of filters, e.g.  
  ```
  {
    jmespath: {
      rooms: '[]...',
      employees: '[]...',
    }
  }
  ```
* `timeout` (number, optional) - The timeout in milliseconds after which the script should fail.
* `url` (string, mandarory) - The URL of the web page from which you want to extract its DOM.
* `viewport` (object, optional) - The dimensions of the browser.
* `waitForSelector` (string, optional) - The selector of an element to wait for before running extracting the web page DOM.
* `waitUntil` (string, optional) - Waits for a specific event in the web page's life cycle before running extracting the web page DOM.
npm package: @nire0510/wql-cli
Description: Query the web with SQL like syntax from your terminal
Author: Nir Elbaz
Latest version: 2.1.5

wql-cli
=======
Query the web with SQL like syntax from your terminal

## Installation

`npm i -g @nire0510/wql-cli`

## Usage

`> wql '{query}'`  
For example:  
`> wql 'SELECT text from "https://www.google.com"'`  
* URLs in the `FROM` clause must be wrapped in parentheses, e.g. "https://www.google.com".
* Method arguments (i.e. `attr`, `data` & `style`) must be wrapped in parentheses, e.g. `attr("id")`.
* For more information about the query syntax, please visit [@nire0510/wql](https://www.npmjs.com/package/@nire0510/wql#syntax) npm package homepage.

### Running on Linux Server
1. Install Chromium browser:  
   `sudo apt-get install chromium-browser`
1. Call `wql` with the `--executablePath` option:  
   `wql -ep '/usr/bin/chromium-browser' 'SELECT...'`

## Help

`> wql --help`