open-index/open-npm huggingface dataset:
npm package: @kalaomer/esnek
Description: ## Project setup ``` yarn install ```
Author: kalaomer
Latest version: 1.0.2

# esnek

## Project setup
```
yarn add @kalaomer/esnek
```

### Compiles and hot-reloads for development
```
yarn serve
```

### Compiles and minifies for production
```
yarn build
```

### Customize configuration
See [Configuration Reference](https://cli.vuejs.org/config/).
npm package: @kalarrs/serverless-local-dev-server
Description: Develop Alexa-Skill and HTTP functions in Serverless without deploying to AWS
Author: Kalarrs Topham
Latest version: 1.2.1

Serverless Local Dev Server Plugin With Multi Project Support
=============================================================

[![Build Status](https://travis-ci.org/kalarrs/serverless-local-dev-server.svg)](https://travis-ci.org/kalarrs/serverless-local-dev-server)

### This is a fork of the Local Dev Server Plugin from  [DieProduktMacher/serverless-local-dev-server](https://github.com/DieProduktMacher/serverless-local-dev-server)

This plugin exposes Alexa-Skill, Schedule, and HTTP events as local HTTP endpoints, removing the need to deploy every code change to AWS Lambda. You can connect these endpoints to Alexa, Facebook Messenger or other services via forwardhq, ngrok or any other forwarding service.

Supported features:

* Expose `alexa-skill`, `schedule`, and `http` events as local HTTP endpoints
* Environment variables
* Basic HTTP integration


# How To

### 1. Install the plugin

```sh
yarn add @kalarrs/serverless-local-dev-server --dev
```

### 2. Add the plugin to your serverless project configuration file

*serverless.yml* configuration example:

```yaml
provider:
  name: aws
  runtime: nodejs8.10

functions:
  hello:
    handler: handler.hello
    events:
      - alexaSkill
      - http: GET /hello
      - schedule: rate(1 day)

# Add serverless-local-dev-server to your plugins:
plugins:
  - "@kalarrs/serverless-local-dev-server"

custom:
  # optional: add folder for serving static files (relative to service path)
  localDevStaticFolder: path/to/static/files
  # optional: set the port the server starts on
  localDevPort: 5000
  # optional: set the path name for schedule to be in local vs utc
  localDevScheduleShowLocalTime: true
```



### 3. Start the server

```sh
serverless local-dev-server
```

On default the server listens on port 5005. You can specify another one with the *--port* argument:

```sh
serverless local-dev-server --port 5000
```

You can also set the port in the serverless.yml
```yaml
  localDevPort: 5000
```

To see responses returned from Lambda and stack traces, prepend SLS_DEBUG=*

```sh
SLS_DEBUG=* serverless local-http-server
```

### 4. For Alexa Skills

#### 4.1 Share localhost with the internet

For example with forwardhq:

```sh
forward 5005
```

#### 4.2 Configure AWS to use your HTTPS endpoint

In the Configuration pane, select HTTPS as service endpoint type and specify the forwarded endpoint URL.

As method for SSL Certificate validation select *My development endpoint is a sub-domain of a domain that has a wildcard certificate from a certificate authority*.


# License & Credits

Licensed under the MIT license.
npm package: @kalarrs/serverless-project-utils
Description: serverless project utilites
Author: Kalarrs Topham
Latest version: 2.2.1

Serverless Project Utils
====================================

[![Build Status](https://travis-ci.org/kalarrs/serverless-project-utils.svg)](https://travis-ci.org/kalarrs/serverless-project-utils)

This plugin helps manage multiple serverless projects with multiple developers.

# License & Credits

Licensed under the MIT license.
npm package: @kalarrs/serverless-shared-api-gateway
Description: Share a single AWS Api Gatewy between multiple serverless projects
Author: Kalarrs Topham
Latest version: 1.0.9

Serverless Shared API Gateway Plugin
====================================

[![Build Status](https://travis-ci.org/kalarrs/serverless-shared-api-gateway.svg)](https://travis-ci.org/kalarrs/serverless-shared-api-gateway)

This plugin allows you to have multiple serverless projects update a single api gateway on aws.

Supported features:

* AWS Api Gateway

This package requires node >= 6.0


# How To

### 1. Install the plugin

```sh
npm install @kalarrs/serverless- --save-dev
```

### 2. Add the plugin to your serverless configuration file

*serverless.yml* configuration example:

```yaml
provider:
  name: aws
  runtime: nodejs6.10

functions:
  hello:
    handler: handler.hello
    events:
      - http: GET /hello

# Add serverless-shared-api-gateway to your plugins:
plugins:
  - "@kalarrs/serverless-shared-api-gateway"
```


# License & Credits

Licensed under the MIT license.
npm package: @kalarrs/serverless-stage-selection
Description: Prompt users to select stage before deploying or packaging
Author: Kalarrs Topham
Latest version: 1.0.0

Serverless Stage Selection Plugin
====================================

[![Build Status](https://travis-ci.org/kalarrs/serverless-stage-selection.svg)](https://travis-ci.org/kalarrs/serverless-stage-selection)

This plugin allows you to be prompted to select a stage before deploy or package.


# How To

### 1. Install the plugin

```sh
npm install @kalarrs/serverless-stage-selection --save-dev
```

### 2. Add the plugin to your serverless configuration file

*serverless.yml* configuration example:

```yaml
provider:
  name: aws
  runtime: nodejs8.10

functions:
  hello:
    handler: handler.hello
    events:
      - http: GET /hello

# Add serverless-stage-selection to your plugins:
plugins:
  - "@kalarrs/serverless-stage-selection"
```

# License & Credits

Licensed under the MIT license.
npm package: @kalarrs/serverless-workspace-utils
Description: Easily manage multiple serverless projects
Author: Kalarrs Topham
Latest version: 1.0.2

Serverless Workspace Utils
==========================

[![Build Status](https://travis-ci.org/kalarrs/serverless-workspace-utils.svg)](https://travis-ci.org/kalarrs/serverless-workspace-utils)

This plugin helps manage multiple serverless projects with multiple developers.

# License & Credits

Licensed under the MIT license.
npm package: @kalashnikov/kumpulyuk-rolldate
Description: rolldate 多格式、功能强大的移动端日期选择插件
Author: 雾空
Latest version: 0.0.1
Deprecated: false

# Modified rolldate

1. Open /dist/rolldate.js
2. Edit css
3. Minify https://javascript-minifier.com/
4. Paste rolldate.min.js
5. ???
6. Profit

## Usage
### es6
```js
import Rolldate from 'rolldate'
new Rolldate({
  el:'#date'
})
```
### commonJS
```js
var Rolldate = require('rolldate');
new Rolldate({
  el:'#date'
})
```
### amd
```js
require(['rolldate'],function(Rolldate){
  new Rolldate({
    el:'#date'
  })
})
```
### cmd
```js
seajs.use('rolldate',function(undefined){
    new Rolldate({
      el:'#date'
    })
});
```

Original by weijhfly (https://www.npmjs.com/package/rolldate)
npm package: @kalbekalu/logger
Description: An all in one logging package!
Author: Kalkidan Bekalu
Latest version: 2.0.11

# Logger README

A simple logging utility for Node.js applications, designed to log messages to various destinations, including a remote API endpoint, console, and a local log file.

## Installation

```bash
npm install @kalbekalu/logger
```

## Usage

### Importing the Logger

```javascript
import Logger from "./Logger";
```

### Creating an instance of Logger

```javascript
const logger = new Logger(appInfo);
```

- `appInfo` (any): Additional information about the application (e.g., name, version) to include in each log entry.

### Logging to a Remote API Endpoint

```javascript
logger.logToUrl(level, logData, config);
```

- `level` (string): Log level (TRACE, INFO, DEBUG, WARN, ERROR, FATAL).
- `logData` (Record<string, any>): Additional data to be logged - can be any valid record object - Required.
- `config` (AxiosRequestConfig, optional): Additional Axios configuration options for the API request.

### Logging to Console

```javascript
logger.standard(level, logData);
```

- `level` (string): Log level (TRACE, INFO, DEBUG, WARN, ERROR, FATAL) - Required.
- `logData` (Record<string, any>): Additional data to be logged - can be any valid record object - Required.

### Logging to a Local File

```javascript
logger.file(level, logData, logFilePath);
```

- `level` (string): Log level (TRACE, INFO, DEBUG, WARN, ERROR, FATAL) - Required.
- `logData` (Record<string, any>): Additional data to be logged - can be any valid record object - Required.
- `logFilePath` (string, optional, default: "./app.log"): Path to the local log file - Required.

## Example

```javascript
const logger = new Logger({
  appName: "MyApp",
  appVersion: "1.0.0",
});

logger
  .logToUrl("INFO", { message: "Application started" })
  .then((response) => console.log("Log sent successfully"))
  .catch((error) => console.error("Error sending log:", error));

logger.standard("DEBUG", { message: "Debugging information" });

logger.file("ERROR", { message: "An error occurred" }, "./errors.log");
```

In this example, logs are sent to a remote API endpoint, printed to the console, and appended to a local log file.

## License

This code is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
npm package: @kale-stew/ui
Description: A component library for @kale-stew website usage
Author: Kylie Stewart
Latest version: 0.1.0

# @kale-stew's Component Library

## a.k.a. `@kale-stew/ui` or `kale-ui`

This is an experiment in publishing and maintaining a component library for my own usage!

- [x] Add `Footer`
- [x] Add `Header`
- [ ] Add `headshot.png`
- [ ] Add storybook tests
- [x] First publish
- [ ] _Eventually:_ automate publish on merge w/ CI
- [ ] _Eventually:_ Publish interactive storybook via gh-pages

## Usage

```sh
# Install the package
$ yarn add @kale-stew/ui
```

```js
// No props necessary!
<KaleHeader />
<KaleFooter />
```

## Development

#### Testing changes to the library

```sh
# Start the example server
$ yarn run dev
# Navigate to localhost:3000
```

#### Releasing the library

```sh
# Before release
$ yarn run test
$ yarn run check-ci

# Version & publish an update to npm
$ npm version [patch|minor|major|<version>]
$ npm publish
$ git push && git push --tags
```
npm package: @kaleabdenbel/llmweb
Description: A compiler for LLM-readable truth from static and dynamic sources.
Author: Kaleab Denbel
Latest version: 1.0.6

# llmweb 🛸

The data compiler that transforms messy application state into LLM-readable truth.

## The Mental Model

`llmweb` is not just a metadata library. it's a compiler for your website's soul.

- **Static Truth**: Your contract with the world. Deterministic. Versioned.
- **Dynamic Truth**: Live data from APIs, Server Actions, or DB calls.
- **The Engine**: Compiles these into a single, structured JSON object for LLMs.
- **Framework Adapters**: Utilities for [Next.js](docs/next.md), [React](docs/react.md), [Express](docs/express.md), and [Vanilla JS](docs/vanilla.md).

## Quick Start

The fastest way to get started is using the CLI:

```bash
npx llmweb init
```

For a deep dive into the **Bridge Pattern**, **Server Actions**, and **Advanced Mapping**, check out our [Definitive Guide](docs/guide.md).

---

## Integration (Next.js)

### 1. Define your Truth

Create an LLM route to expose your site's data.

```typescript
// app/llm/route.ts
import { createLLMHandler } from "@kaleabdenbel/llmweb/adapters/next";
import { getStaffList } from "@/actions/getStaffList";

const config = {
  static: "./llm.json", // Path to your static contract

  dynamic: {
    announcements: {
      from: { type: "fetch", url: "https://api.site.com/news" },
      map: {
        title: "headline",
        body: "content",
        publishedAt: "date",
      },
    },
    staff: {
      from: { type: "fn", call: getStaffList },
      map: {
        name: "full_name",
        role: "role_title",
      },
    },
  },
};

export const GET = createLLMHandler(config);
```

### 2. Use the Component

Render the compiled truth directly in your admin or SEO pages.

```tsx
import { LLMJson } from "llmweb/adapters/next";

export default function LlmTruthPage() {
  return (
    <div className="p-8">
      <h1>LLM Truth Engine</h1>
      <LLMJson
        config={config}
        className="bg-gray-900 text-green-400 p-4 rounded"
      />
    </div>
  );
}
```

## The Engine Features

- **Brutal Mapping**: Rename, pick, omit, and compute fields easily.
- **Parallel Resolution**: All dynamic sources are resolved in parallel.
- **Error Boundaries**: Configurable `failLoudly` mode for strict data integrity.
- **Timeouts**: Prevent slow APIs from hanging your truth route.
- **Deterministic Merging**: Static structure defines the slots; dynamic data fills them.
- **AI-Friendly JSON-LD**: Automatically generate Schema.org metadata for LLM context discovery.

## Advanced Mapping

```typescript
map: {
  fullName: (s) => `${s.first} ${s.last}`, // Computed field
  meta: {
     tags: "categories", // Nested renames
  }
}
```

## License

MIT
npm package: @kalebu2468/editor-lessons
Description: Lesson Tool for Editor.js
Author: Kalebu2468
Latest version: 0.0.15

# Lesson Tool

![Version of EditorJS that the plugin is compatible with](https://badgen.net/badge/Editor.js/v2.0/blue)

Provides Lesson Blocks for the [Editor.js](https://ifmo.su/editor).

## Installation

Get the package

```shell
yarn add @kalebu2468/editor-lessons
```

Include module at your application

```javascript
import Lessons from "@kalebu2468/editor-lessons";
```

## Usage

Add a new Tool to the `tools` property of the Editor.js initial config.

```javascript
var editor = EditorJS({
  ...

  tools: {
    ...
    lessons: Lessons,
  },

  ...
});
```

## Shortcut

You can insert this Block by a useful shortcut. Set it up with the `tools[].shortcut` property of the Editor's initial config.

```javascript
var editor = EditorJS({
  ...

  tools: {
    ...
    lessons: {
      class: Lessons,
    },
  },

  ...
});
```

## Config Params

All properties are optional.

| Field        | Type       | Description                 |
| ------------ | ---------- | --------------------------- |
| placeholder  | `string`   | lesson's placeholder string |
| levels       | `number[]` | enabled lesson levels       |
| defaultLevel | `number`   | default lesson level        |

```javascript
var editor = EditorJS({
  ...

  tools: {
    ...
    lessons: {
      class: Lessons,
      config: {
        placeholder: 'Enter a lesson',
        levels: [2, 3, 4],
        defaultLevel: 3
      }
    }
  }

  ...
});
```

## Tool's settings

![An image showing the lesson block tool](https://capella.pics/634ad545-08d7-4cb7-8409-f01289e0e5e1.jpg)

You can select one of six levels for heading.

## Output data

| Field | Type     | Description     |
| ----- | -------- | --------------- |
| text  | `string` | lesson's text   |
| level | `number` | level of lesson |

```json
{
  "type": "lessons",
  "data": {
    "text": "Why Telegram is the best messenger",
    "level": 2
  }
}
```
npm package: @kalebu2468/editor-subpoints
Description: SubPoints Tool for Editor.js
Author: kalebu2468
Latest version: 0.0.12

# Heading Tool

![Version of EditorJS that the plugin is compatible with](https://badgen.net/badge/Editor.js/v2.0/blue)

Provides SubPoints Blocks for the [Editor.js](https://ifmo.su/editor).

## Installation

Get the package

```shell
yarn add @kalebu2468/editorjs-subpoints
```

Include module at your application

```javascript
import SubPoint from "@kalebu2468/editorjs-subpoints";
```

## Usage

Add a new Tool to the `tools` property of the Editor.js initial config.

```javascript
var editor = EditorJS({
  ...

  tools: {
    ...
    subpoints: SubPoints,
  },

  ...
});
```

## Shortcut

You can insert this Block by a useful shortcut. Set it up with the `tools[].shortcut` property of the Editor's initial config.

```javascript
var editor = EditorJS({
  ...

  tools: {
    ...
    subpoints: {
      class: SubPoints,
    },
  },

  ...
});
```

## Config Params

All properties are optional.

| Field        | Type       | Description                   |
| ------------ | ---------- | ----------------------------- |
| placeholder  | `string`   | subpoint's placeholder string |
| levels       | `number[]` | enabled subpoint levels       |
| defaultLevel | `number`   | default subpoint level        |

```javascript
var editor = EditorJS({
  ...

  tools: {
    ...
    subpoints: {
      class: SubPoints,
      config: {
        placeholder: 'Enter a subpoint',
        levels: [4],
        defaultLevel: 4
      }
    }
  }

  ...
});
```

## Tool's settings

![An image showing the subpoint block tool](https://capella.pics/634ad545-08d7-4cb7-8409-f01289e0e5e1.jpg)

You can select one of six levels for heading.

## Output data

| Field | Type     | Description       |
| ----- | -------- | ----------------- |
| text  | `string` | subpoint's text   |
| level | `number` | level of subpoint |

```json
{
  "type": "subpoints",
  "data": {
    "text": "Why Telegram is the best messenger",
    "level": 4
  }
}
```
npm package: @kalebu2468/editorjs-points
Description: Point Tool for Editor.js
Author: kalebu2468
Latest version: 0.0.16

# Point Tool

![Version of EditorJS that the plugin is compatible with](https://badgen.net/badge/Editor.js/v2.0/blue)

Provides Points Blocks for the [Editor.js](https://ifmo.su/editor).

## Installation

Get the package

```shell
yarn add @kalebu2468/editorjs-points
```

Include module at your application

```javascript
import Point from "@kalebu2468/editorjs-points";
```

Optionally, you can load this tool from CDN [JsDelivr CDN](https://cdn.jsdelivr.net/npm/@editorjs/header@latest)

## Usage

Add a new Tool to the `tools` property of the Editor.js initial config.

```javascript
var editor = EditorJS({
  ...

  tools: {
    ...
    points: Point,
  },

  ...
});
```

## Shortcut

You can insert this Block by a useful shortcut. Set it up with the `tools[].shortcut` property of the Editor's initial config.

```javascript
var editor = EditorJS({
  ...

  tools: {
    ...
    points: {
      class: Point,
    },
  },

  ...
});
```

## Config Params

All properties are optional.

| Field        | Type       | Description                |
| ------------ | ---------- | -------------------------- |
| placeholder  | `string`   | point's placeholder string |
| levels       | `number[]` | enabled point levels       |
| defaultLevel | `number`   | default point level        |

```javascript
var editor = EditorJS({
  ...

  tools: {
    ...
    points: {
      class: Point,
      config: {
        placeholder: 'Enter a point',
        levels: [3],
        defaultLevel: 3
      }
    }
  }

  ...
});
```

## Tool's settings

![An image showing the point block tool](https://capella.pics/634ad545-08d7-4cb7-8409-f01289e0e5e1.jpg)

You can select one of six levels for point.

## Output data

| Field | Type     | Description    |
| ----- | -------- | -------------- |
| text  | `string` | point's text   |
| level | `number` | level of point |

```json
{
  "type": "points",
  "data": {
    "text": "Why Telegram is the best messenger",
    "level": 3
  }
}
```
npm package: @kalebu2468/editorjs-topic
Description: Topic Tool for Editor.js
Author: kalebu2468
Latest version: 0.0.18

# Topic Tool

![Version of EditorJS that the plugin is compatible with](https://badgen.net/badge/Editor.js/v2.0/blue)

Provides Topic Blocks for the [Editor.js](https://ifmo.su/editor).

## Installation

Get the package

```shell
yarn add @kalebu2468/editorjs-topic
```

Include module at your application

```javascript
import Topic from "@editorjs/editorjs-topic";
```

## Usage

Add a new Tool to the `tools` property of the Editor.js initial config.

```javascript
var editor = EditorJS({
  ...

  tools: {
    ...
    topics: Topics,
  },

  ...
});
```

## Shortcut

You can insert this Block by a useful shortcut. Set it up with the `tools[].shortcut` property of the Editor's initial config.

```javascript
var editor = EditorJS({
  ...

  tools: {
    ...
    topics: {
      class: Topics,
    },
  },

  ...
});
```

## Config Params

All properties are optional.

| Field        | Type       | Description                |
| ------------ | ---------- | -------------------------- |
| placeholder  | `string`   | topic's placeholder string |
| levels       | `number[]` | enabled topic levels       |
| defaultLevel | `number`   | default topic level        |

```javascript
var editor = EditorJS({
  ...

  tools: {
    ...
    topics: {
     class: Topics,
        config: {
          placeholder: "Enter a Topic",
          levels: [1],
          defaultLevel: 1,
        },
    }
  }

  ...
});
```

## Output data

| Field | Type     | Description    |
| ----- | -------- | -------------- |
| text  | `string` | topic's text   |
| level | `number` | level of topic |

```json
{
  "type": "topic",
  "data": {
    "text": "Why Telegram is the best messenger",
    "level": 1
  }
}
```