open-index/open-npm huggingface dataset:
npm package: @getdrip/much-selector-elm
Description: A fancy selector web component written (mostly) in elm.
Author: Jachin Rupe
Latest version: 0.0.11

# \<much-selector>

![Doge Meme](public/doge.jpg)

A web component - powered by Elm - that will create a powerful select menu.

## Prior Art/Inspiration/Goals

The project draws heavy inspiration from the jquery based [selectize.js](https://selectize.github.io/selectize.js/).

The need for this project is that we want to use selectize.js however we need the over all app to be built in [Elm](https://elm-lang.org/). Elm needs to "own" the DOM and selectize is built in a way that's not compatible with that. 

The goal for this project to achieve near feature parity with selectize using web components. The API will be different, so it will not be a drop in replacement but hopefully it will not be too hard to replace one with the other.

## Installation

```bash
npm i much-selector-elm
```

## Usage

The npm package gives you the class `MuchSelector` (which inherits from `HTMLElement`), what you need to do is use it to define your own element.

```javascript
import MuchSelector from "@getdrip/much-selector-elm";

if (!customElements.get("much-selector")) {
  // Putting guard rails around this because browsers do not like
  //  having the same custom element defined more than once.
  window.customElements.define("much-selector", MuchSelector);
}
```

## Development

To work on this project, clone the repo to your machine, then.

### Initial Setup

Just do like you'd expect to get started. Only development dependencies.

``` bash
npm install
```

### Watch and Develop

To run a webpack development server with the sandbox/demo page:

```bash
npm run watch
```

Now you can visit http://localhost:8000

### Production Build

To do a production build run

```bash
npm run build
```

## API

### DOM

#### Attributes

##### `selected`

The `selected` attribute is used to set the value of the `<much-selector>`.

##### `placeholder`

The `placeholder` attribute is used to set the placeholder in the text input of the `<much-selector>`. Just like in the `<input type="text">` it should only show up if the input is empty. 

#### Options

### Events

### Functions
npm package: @getelpida/adminjs-nestjs
Description: This is an official [AdminJS](https://github.com/SoftwareBrothers/adminjs) plugin which integrates it to [nestjs](https://nestjs.com) framework.
Latest version: 6.1.0-fix.3

# NestJS plugin for AdminJS

This is an official [AdminJS](https://github.com/SoftwareBrothers/adminjs) plugin which integrates it to [nestjs](https://nestjs.com) framework.

Version >3.0.0 might not be compatible with Nestjs 7 or lower. If adapter is not working, try downgrading adapter to version 2.*.*

## AdminJS

AdminJS is an automatic admin interface which can be plugged into your application. You, as a developer, provide database models (like posts, comments, stores, products or whatever else your application uses), and AdminJS generates UI which allows you (or other trusted users) to manage content.

Check out the example application here: https://adminjs-demo.herokuapp.com/admin/

Or visit [AdminJS](https://github.com/SoftwareBrothers/adminjs) github page.

## Usage

To see example usage see the [example-app](https://github.com/SoftwareBrothers/adminjs-nestjs/tree/master/example-app) or visit the [Nestjs section under AdminJS project page](https://softwarebrothers.github.io/adminjs-dev/module-@adminjs_nestjs.html)

## License

AdminJS is copyrighted © 2023 rst.software. It is a free software, and may be redistributed under the terms specified in the [LICENSE](LICENSE.md) file.

## About rst.software

<img src="https://pbs.twimg.com/profile_images/1367119173604810752/dKVlj1YY_400x400.jpg" width=150>

We’re an open, friendly team that helps clients from all over the world to transform their businesses and create astonishing products.

* We are available for [hire](https://www.rst.software/estimate-your-project).
* If you want to work for us - check out the [career page](https://www.rst.software/join-us).
npm package: @getengram/cli
Description: CLI for Engram — persistent memory for AI agents
Latest version: 0.1.0

# @getengram/cli

Command-line interface for [Engram](https://getengram.app) — persistent memory for AI agents.

## Install

```bash
# npm
npm install -g @getengram/cli

# or run directly
npx @getengram/cli search "your query"
```

## Setup

```bash
# Authenticate
engram auth login engram_sk_live_YOUR_API_KEY

# Or use environment variable
export ENGRAM_API_KEY=engram_sk_live_YOUR_API_KEY
```

## Commands

### Authentication

```bash
engram auth login <key>    # Save API key
engram auth logout         # Remove credentials
engram auth status         # Show auth status
```

### Conversations

```bash
# List all conversations
engram conversations list
engram conversations list --agent my-agent --tags prod,deploy

# Create a conversation
engram conversations create --title "Deploy Log" --tags prod

# Get conversation with messages
engram conversations get conv_abc123

# Delete a conversation
engram conversations delete conv_abc123 --force
```

### Store Messages

```bash
# Store a message
engram store -c conv_abc123 "Deployed v2.1.0 to production"

# Store with specific role
engram store -c conv_abc123 --role assistant "Deploy complete"

# Store tool output
engram store -c conv_abc123 --role tool --tool deploy "Success: v2.1.0"

# Pipe from stdin
echo "log output here" | engram store -c conv_abc123 --file -

# Store from file
engram store -c conv_abc123 --file ./deploy.log
```

### Search

```bash
# Semantic search across all memory
engram search "when did we deploy v2"

# Limit results
engram search "error handling" --limit 5

# Search within a conversation
engram search "config change" --conversation conv_abc123

# Filter by tags
engram search "production issues" --tags prod,api
```

### Output Formats

Every command supports `--json` for machine-readable output:

```bash
engram conversations list --json
engram search "deploy" --json | jq '.results[0].score'
```

## Configuration

Credentials are stored in `~/.engram/config.json`.

### Environment Variables

| Variable | Description |
|----------|-------------|
| `ENGRAM_API_KEY` | API key (overrides saved config) |
| `ENGRAM_BASE_URL` | Custom endpoint (default: `https://mcp.getengram.app`) |

## Examples

### Log agent sessions

```bash
# Create a session
CONV=$(engram conversations create --title "Agent Run $(date +%F)" --json | jq -r '.conversationId')

# Store messages as the agent runs
engram store -c $CONV "User asked to refactor auth module"
engram store -c $CONV --role assistant "Analyzing auth module..."
engram store -c $CONV --role tool --tool code_review "Found 3 issues"

# Later, search across all sessions
engram search "auth module issues"
```

### Pipe build output

```bash
npm run build 2>&1 | engram store -c conv_builds --file -
```

### Export conversation as JSON

```bash
engram conversations get conv_abc123 --json > conversation.json
```

## License

MIT — [getengram.app](https://getengram.app)