open-index/open-npm huggingface dataset:
npm package: @spichkens/eslint-plugin-i18n-keys
Description: First, make sure you have [ESlint](https://www.npmjs.com/package/eslint) installed: ```bash npm i --save-dev eslint ```
Author: spichkens
Latest version: 1.0.5

# @spichkens/eslint-plugin-i18n-keys

## Installation

First, make sure you have [ESlint](https://www.npmjs.com/package/eslint) installed:
```bash
npm i --save-dev eslint
```

After that install `@spichkens/eslint-plugin-i18n-keys` plugin:
```bash
npm install --save-dev @spichkens/eslint-plugin-i18n-keys
```

## Usage

Example config:

```js
export default {
  plugins: ['@spichkens/i18n-keys'],
  rules: {
    '@spichkens/i18n-keys/no-missing-i18n-key': ['error', {
      localesPath: 'public/locales',
      defaultLocale: 'en',
      defaultNamespace: 'common'
    }]
  }
};

```

`localesPath` - Path to your locales folder relative to the eslint config file (default: public/locales)

`defaultLocale` - Default translations files folder name (default: en)

`defaultNamespace` - Default namespace name (default: common)
npm package: @spicy-hooks/bin
Description: Binary utilities used within the `@spicy-hooks` project, but useful for other projects as well. The included tool focus mainly on development and release process.
Latest version: 3.0.0

# @spicy-hooks/bin

Binary utilities used within the `@spicy-hooks` project, but useful for other projects as well. The included tool focus mainly on development and release process.

The package registers a single executable binary:

```shell script
spicy <command> [... command options ...]
```

Individual `<command>`s are briefly described below with links to detailed documentation.

This package is a part of [the `@spicy-hooks` family](https://github.com/salsita/spicy-hooks).
Be sure to checkout the other interesting packages we offer.

## Installation

Most-likely, you will need the binaries only during development and build process,
so you can install it as a `devDependency`:

```shell script
npm install @spicy-hooks/bin --save-dev
```
or
```shell script
yarn add @spicy-hooks/bin --dev
```

## Commands

### `redirect-refs`

Redirects any link pointing to the main-branch to a specific ref.

Read [more about `redirect-refs`](https://github.com/salsita/spicy-hooks/blob/next/packages/bin/docs/redirect-refs.md)

## Versioning

The whole `@spicy-hooks` project complies with [Semantic Versioning](https://semver.org/).
The `@spicy-hooks/bin` package is however just one package from the whole project.
Seeing the major version incremented therefore doesn't necessarily mean that there
is a breaking change in this particular package. Check the
[CHANGELOG.md](https://github.com/salsita/spicy-hooks/blob/next/packages/bin/CHANGELOG.md)
for accurate information.

It is guaranteed though, that when the major version doesn't change,
there has been no breaking change in this package.

**Warning:** The `internal` folder is excluded from any semantic versioning conventions.
Importing from this folder directly is strongly discouraged.

## Issues

Please submit any issue or feature request on [the main project](https://github.com/salsita/spicy-hooks/issues). _(issue templates coming soon)_

## Documentation

* [redirect-refs](https://github.com/salsita/spicy-hooks/blob/next/packages/bin/docs/redirect-refs.md)
npm package: @spicy-hooks/core
Description: **React Hooks of general use.**
Latest version: 3.0.0

# @spicy-hooks/core

**React Hooks of general use.**

When working on a particular React Hooks powered project you often find yourself creating
a low level reusable hook - it just feels right with React Hooks. You then copy paste that hook
into your next project as it's simply handy. Then you add another one and another one...

Well you get the point, it's not a bad idea to have a place where we can share these hooks
across teams, projects and even companies. This place is called `@spicy-hooks/core`.

Detailed description of all included hooks is available in our
[API reference](https://spicy-hooks.salsita.co/next/modules/_core_src_index_.html).

This package is a part of [the `@spicy-hooks` family](https://github.com/salsita/spicy-hooks).
Be sure to checkout the other interesting packages we offer.

## Installation

Just use the usual way:
```shell script
npm install @spicy-hooks/core --save
```
or
```shell script
yarn add @spicy-hooks/core
```

## Versioning

The whole `@spicy-hooks` project complies with [Semantic Versioning](https://semver.org/).
The `@spicy-hooks/core` package is however just one package from the whole project.
Seeing the major version incremented therefore doesn't necessarily mean that there
is a breaking change in this particular package. Check the
[CHANGELOG.md](https://github.com/salsita/spicy-hooks/blob/next/packages/core/CHANGELOG.md)
for accurate information.

It is guaranteed though, that when the major version doesn't change,
there has been no breaking change in this package.

**Warning:** The `internal` folder is excluded from any semantic versioning conventions.
Importing from this folder directly is strongly discouraged.

## Issues

Please submit any issue or feature request on [the main project](https://github.com/salsita/spicy-hooks/issues). _(issue templates coming soon)_

## Documentation

* [API reference](https://spicy-hooks.salsita.co/next/modules/_core_src_index_.html) - detailed description of every included hook
* [contribution guide](https://github.com/salsita/spicy-hooks/tree/next/docs) - when you want to get involved
npm package: @spicy-hooks/observables
Description: **React Hooks for easy plugging of RxJS observables into React.**
Latest version: 3.0.0

# @spicy-hooks/observables

**React Hooks for easy plugging of RxJS observables into React.**

> WORK IN PROGRESS - We're still gathering reasonable arguments to lure you into using our package.

Have you ever tried _"replacing Redux with Context API and React Hooks"_?
(By the way, this must be one of the most Googled phrases in the last two years)

If you had, you must have faced at least the following questions:
* How to **optimally** work with complex shapes without triggering thousands of unnecessary renders?
* How to share transformations of the state between multiple components? 
* How to keep logic at least a bit separated from components?
     
Our answer to those questions come in the form of `@spicy-hooks/observables` package.

This package is a part of [the `@spicy-hooks` family](https://github.com/salsita/spicy-hooks).
Be sure to checkout the other interesting packages we offer.

## Concept

_TODO Describe the overall concept of RxJS powered React_

Until the above TODO is resolved, feel free to get a general idea
by:
* [reading these slides](https://docs.google.com/presentation/d/1S1cSjh5vZhoSSf7EKO30aSAKVmVfMb481MvOskAEfJk/edit?usp=sharing)
* or [watching this talk](https://www.youtube.com/watch?v=T9Etvk8bIr8)

## Installation

The package uses RxJS under the hood, but we leave it up to you to choose the version you want to use. Make sure you have one installed though.

```shell script
npm install @spicy-hooks/observables rxjs --save
```
or
```shell script
yarn add @spicy-hooks/observables rxjs
```

## Versioning

The whole `@spicy-hooks` project complies with [Semantic Versioning](https://semver.org/).
The `@spicy-hooks/observables` package is however just one package from the whole project.
Seeing the major version incremented therefore doesn't necessarily mean that there
is a breaking change in this particular package. Check the
[CHANGELOG.md](https://github.com/salsita/spicy-hooks/blob/next/packages/observables/CHANGELOG.md)
for accurate information.

It is guaranteed though, that when the major version doesn't change,
there has been no breaking change in this package.

**Warning:** The `internal` folder is excluded from any semantic versioning conventions.
Importing from this folder directly is strongly discouraged.

## Issues

Please submit any issue or feature request on
[the main project](https://github.com/salsita/spicy-hooks/issues).
_(issue templates coming soon)_

## Documentation

* [API reference](https://spicy-hooks.salsita.co/next/modules/_observables_src_index_.html) - detailed description of every included hook, operator and utility function
* [contribution guide](https://github.com/salsita/spicy-hooks/tree/next/docs) - when you want to get involved
npm package: @spicy-hooks/utils
Description: **General utility functions and types**
Latest version: 3.0.0

# @spicy-hooks/utils

**General utility functions and types**

_used within the `@spicy-hooks` project, but useful for other projects as well_

While working a project you often end up with a bunch of utility functions (that you didn't find
in `lodash`) somewhere in your repo. It feels like a waste of time and good code to always
reinvent the wheel for each further project.

That's why we're publishing few utility functions and types we created
for the `@spicy-hooks` project and hoping that people will add their own so that
we can share them across the projects and eventually even across companies.

This package is a part of [the `@spicy-hooks` family](https://github.com/salsita/spicy-hooks).
Be sure to checkout the other interesting packages we offer.

## Installation

Just use the usual way:
```shell script
npm install @spicy-hooks/utils --save
```
or
```shell script
yarn add @spicy-hooks/utils
```

## Versioning

The whole `@spicy-hooks` project complies with [Semantic Versioning](https://semver.org/).
The `@spicy-hooks/utils` package is however just one package from the whole project.
Seeing the major version incremented therefore doesn't necessarily mean that there
is a breaking change in this particular package. Check the
[CHANGELOG.md](https://github.com/salsita/spicy-hooks/blob/next/packages/utils/CHANGELOG.md)
for accurate information.

It is guaranteed though, that when the major version doesn't change,
there has been no breaking change in this package.

**Warning:** The `internal` folder is excluded from any semantic versioning conventions.
Importing from this folder directly is strongly discouraged.

## Issues

Please submit any issue or feature request on [the main project](https://github.com/salsita/spicy-hooks/issues). _(issue templates coming soon)_

## Documentation

* [API reference](https://spicy-hooks.salsita.co/next/modules/_utils_src_index_.html) - detailed description of every included utility function
* [contribution guide](https://github.com/salsita/spicy-hooks/tree/next/docs) - when you want to get involved
npm package: @spicy-ui/core
Description: A themable and extensible React UI library, ready to use out of the box
Author: Alex Gabites
Latest version: 0.1.0-alpha.9

# spicy-ui

🌶️ A themable and extensible React UI library, ready to use out of the box

[![npm](https://img.shields.io/npm/v/@spicy-ui/core.svg)](https://www.npmjs.com/package/@spicy-ui/core)
[![Dependencies](https://david-dm.org/spicy-ui/core/status.svg)](https://david-dm.org/spicy-ui/core)
[![Dev Dependencies](https://david-dm.org/spicy-ui/core/dev-status.svg)](https://david-dm.org/spicy-ui/core?type=dev)

## Basic usage

Install Spicy UI to your React project with `npm i @spicy-ui/core styled-components`

```js
import React from 'react';
import { Button, ThemeProvider } from '@spicy-ui/core';

export const App = () => (
  <ThemeProvider>
    <Button>Hey hot stuff 🌶️</Button>
  </ThemeProvider>
);
```

See the [documentation](https://spicy-ui.netlify.app/) for components, theming and advanced usage.

## Issues and Bugs

If you happen to find any, please report them [here](https://github.com/spicy-ui/core/issues) so they can be squashed.

## Development and Contributing

Pull the repo and then install dependencies with `npm`.

In the root directory, use `npm run start:storybook` to run Storybook on `localhost:9000`

See the `package.json` for other scripts such as `clean`, `test` and `lint`.

## License

MIT, see the [LICENSE](./LICENSE) file.
npm package: @spicy-ui/styled-system
Description: Responsive, theme-based style props for building design systems with React
Author: Alex Gabites
Latest version: 0.0.1-alpha.3

# styled-system

🌶️ Responsive, theme-based style props for building design systems with React

[![npm](https://img.shields.io/npm/v/@spicy-ui/styled-system.svg)](https://www.npmjs.com/package/@spicy-ui/styled-system)
[![Dependencies](https://david-dm.org/spicy-ui/styled-system/status.svg)](https://david-dm.org/spicy-ui/styled-system)
[![Dev Dependencies](https://david-dm.org/spicy-ui/styled-system/dev-status.svg)](https://david-dm.org/spicy-ui/styled-system?type=dev)

## ⚠️ Caution

While it is _almost_ a direct port of [styled-system](https://github.com/styled-system/styled-system) to TypeScript it does have a few minor changes.

- `bg` is now for the `background` css property (but it still uses the `color` scale) and `bgColor` has been added
- there are a bunch of new aliased props (e.g. `h` for `height`, `maxW` for `max-width`, etc)
- there is an `extendedFlexbox` and `extendedGrid` parser which contains shorthands for `flexbox` and `grid` parsers (good for Flex and Grid components)
- the `css` function now supports a collection of pseudo selectors (e.g. `_hover` for `&:hover`)
- new `animation` and `transition` parsers (and scales) which are also rolled into the `css` function

A major part that is incomplete in this package is the types (both exported and internal and particulary around the `css` export) - if you're able and willing to have a crack at them please do, it would be super appreciated to get some help on this.

## Issues and Bugs

If you happen to find any, please report them [here](https://github.com/spicy-ui/core/issues) so they can be squashed.

## License

MIT, see the [LICENSE](./LICENSE) file.
npm package: @spicyclaws/openclaw-agentworld
Description: OpenClaw plugin that ships and manages AgentWorld runtime with auto session-follow UX.
Latest version: 0.1.0

# OpenClaw AgentWorld Plugin

Production plugin that packages and manages AgentWorld runtime inside OpenClaw.

## What this gives users

- one-command install via OpenClaw plugins
- automatic runtime start on gateway boot
- auto-follow active chat session (prevents wrong-session bug)
- built-in connection status + mismatch UX (in AgentWorld UI)
- dedupe protection for duplicate mirrored replies

## Install (user flow)

```bash
openclaw plugins install @spicyclaws/openclaw-agentworld
openclaw plugins enable openclaw-agentworld
openclaw gateway restart
```

## Install (local dev flow)

```bash
openclaw plugins install /absolute/path/to/openclaw-agentworld-plugin --link
openclaw plugins enable openclaw-agentworld
openclaw gateway restart
```

## Runtime commands

```bash
openclaw agentworld status
openclaw agentworld start
openclaw agentworld stop
openclaw agentworld restart
```

## Config

Set values under:

`plugins.entries.openclaw-agentworld.config`

Example:

```json5
{
  plugins: {
    entries: {
      "openclaw-agentworld": {
        enabled: true,
        config: {
          autoStart: true,
          autoRestart: true,
          host: "127.0.0.1",
          port: 8787,
          sessionMode: "auto",
          pollMs: 800,
          staleMs: 15000,
          dedupeMs: 12000
        }
      }
    }
  }
}
```

If you want to force a specific session:

```json5
{
  sessionMode: "pinned",
  pinnedSessionKey: "agent:main:telegram:direct:1327788336"
}
```

## Verify

```bash
openclaw agentworld status
curl -sS http://127.0.0.1:8787/api/pixel-agents/connection
```

## Publish

```bash
npm pack --dry-run
npm publish --access public
```
npm package: @spicyclaws/openclaw-pixel-agents
Description: OpenClaw plugin that ships and manages AgentWorld (Pixel Agents) runtime with auto session-follow UX.
Latest version: 0.1.0

# OpenClaw Pixel Agents Plugin (AgentWorld)

Production plugin that packages and manages AgentWorld runtime inside OpenClaw.

## What this gives users

- one-command install via OpenClaw plugins
- automatic runtime start on gateway boot
- auto-follow active chat session (prevents wrong-session bug)
- built-in connection status + mismatch UX (in AgentWorld UI)
- dedupe protection for duplicate mirrored replies

## Install (user flow)

```bash
openclaw plugins install @spicyclaws/openclaw-pixel-agents
openclaw plugins enable openclaw-pixel-agents
openclaw gateway restart
```

## Install (local dev flow)

```bash
openclaw plugins install /absolute/path/to/openclaw-pixel-agents-plugin --link
openclaw plugins enable openclaw-pixel-agents
openclaw gateway restart
```

## Runtime commands

```bash
openclaw agentworld status
openclaw agentworld start
openclaw agentworld stop
openclaw agentworld restart
```

## Config

Set values under:

`plugins.entries.openclaw-pixel-agents.config`

Example:

```json5
{
  plugins: {
    entries: {
      "openclaw-pixel-agents": {
        enabled: true,
        config: {
          autoStart: true,
          autoRestart: true,
          host: "127.0.0.1",
          port: 8787,
          sessionMode: "auto",
          pollMs: 800,
          staleMs: 15000,
          dedupeMs: 12000
        }
      }
    }
  }
}
```

If you want to force a specific session:

```json5
{
  sessionMode: "pinned",
  pinnedSessionKey: "agent:main:telegram:direct:1327788336"
}
```

## Verify

```bash
openclaw agentworld status
curl -sS http://127.0.0.1:8787/api/pixel-agents/connection
```

## Publish

```bash
npm pack --dry-run
npm publish --access public
```
npm package: @spicycoding/elmo
Description: This package helps you when you start with a new website. It includes default styles for form elements and you can also include our javascript to make it possible to add effects to your HTML elements.
Author: Spicy Coding
Latest version: 0.0.6

## Elmo
Elmo is a framework that includes **styled form elements** and javascript for **visual effects**.

<br>

## What packages do we use?
By installing **elmo**, you can:

 - Use the Tailwind CSS classes. Here you can find a [cheat sheet](http://nerdcave.com/tailwind-cheat-sheet).
 - Use the GSAP functionalities. For the documentation, go to [greensock.com](https://greensock.com/).

<br>

## Quick install
**NPM**:

    npm install @spicycoding/elmo


**Yarn**

    yarn add @spicycoding/elmo

<br>

## Add visual effects to your website
In your project, include our package like this:

    import elmo from '@spicycoding/elmo';
    
    elmo.start();
    
    

You can also change the offset so that the fade in effects will be triggered earlier or later.

    elmo.start({
        offset: 250
    });
    
    

    
The package will now automatically search for `data-effect` attributes. For example, when you have an image which should fadeIn you can use this code to make it work:

    <img src="/images/your-image.jpg" data-effect="fadeIn">

<br>

## Elements that are not immediately visible in the viewport
If (for example) your image is not yet visible on the page load, the effect will be added to a queue. When the visitor scrolls down and the element becomes visible, the effect will be triggered automatically.

<br>

## Documentation
***Basic usage:***
| Effect|Default duration|Example code|
|--|--|--|
| slideUp| 0.5 sec. |`data-effect="slideUp"`
| slideDown| 0.5 sec.|`data-effect="slideDown"`
| slideLeft| 0.5 sec.|`data-effect="slideLeft"`
| slideRight| 0.5 sec.|`data-effect="slideRight"`
| zoomIn| 0.5 sec.|`data-effect="zoomIn"`
| zoomOut| 0.5 sec.|`data-effect="zoomOut"`
| fadeIn| 1 sec.|`data-effect="fadeIn"`
| fadeOut| 1 sec.|`data-effect="fadeOut"`

<br>


***Multiple effects at once:***
| Effect|Default duration|Example code|
|--|--|--|
| slideUp and fadeIn| 0.5 sec. |`data-effect="slideUp|fadeIn"`

<br>


***Change the duration:***
| Effect|Custom duration|Example code|
|--|--|--|
| slideUp| 0.75 sec. |`data-effect="slideUp:0.75"`
| slideUp and fadeIn| 0.75 sec. and 1.75 sec. |`data-effect="slideUp:0.75|fadeIn:1.75"`

<br>

## Import styled form elements and Tailwind classes
If you also like to use our styled form elements and the Tailwind classes, you can import our all.css file:

    @import '~@spicycoding/elmo/css/all.css';

<br>

## Thank you for using Elmo!
Kind regards,<br>
Pim vd Molen ([Spicy Coding](https://spicycoding.nl))
npm package: @spicycoding/js-compiler
Description: This package compiles your javascript and transforms it using the .babelrc file which you should add to the root of your project.
Author: Pim vd Molen
Latest version: 1.1.0

**@spicycoding/js-compiler**  
This compiler has three main functionalities:
- Compile JS code and write it to the ./public/dist/ folder
- Watch for changes in the ./resources/assets/js/ folder
- Minifies code when using the --minify flag

**How to use**  
Install using NPM: `npm install @spicycoding/js-compiler`  
Install using Yarn: `yarn add @spicycoding/js-compiler`

**Development**  
`node ./node_modules/@spicycoding/js-compiler/src/cli.js build --target ./resources/assets/js/app.js --destination ./public/dist/app.js`

**Watcher**  
`node ./node_modules/@spicycoding/js-compiler/src/cli.js watch --target ./resources/assets/js/app.js --destination ./public/dist/app.js`

**Production**  
`node ./node_modules/@spicycoding/js-compiler/src/cli.js build --target ./resources/assets/js/app.js --destination ./public/dist/app.js --minify`

# Transform using babel
You can transform the output to support older browser by creating a .babelrc file which you should put in your project root. Example file:

```
{
  "presets": [
    [
      "@babel/preset-env",
      {
        "targets": {
          "browsers": [
            "last 3 versions",
            "> 2%"
          ]
        },
        "useBuiltIns": "usage",
        "corejs": "core-js@3",
        "debug": false
      }
    ]
  ]
}
```
npm package: @spicycoding/sass-compiler
Description: This package compiles your (for example) app.scss file and bundles it to one CSS file.
Author: Pim vd Molen
Latest version: 1.1.1

**Sass compiler**  
This bundler has four main functionalities:
- Compile SASS code (including Tailwind version 1 and above!) and write it to the destination folder (./public/dist/ in our example)
- Watch for changes in the target folder (./resources/assets/sass/ in our example)
- Minifies code when using the --minify flag
- Copies assets the destination folder when using the assetImporter command


**How to use**  
Install using NPM: `npm install @spicycoding/sass-compiler`  
Install using Yarn: `yarn add @spicycoding/sass-compiler`


**Import assets to the destination folder**   
`node ./node_modules/@spicycoding/sass-compiler/src/cli.js assetImporter --destination ./public/dist/ --import-assets ./node_modules/@fortawesome/fontawesome-free/webfonts/`

**Development**  
`node ./node_modules/@spicycoding/sass-compiler/src/cli.js build --target ./resources/assets/sass/app.scss --destination ./public/dist/app.css --configuration ./tailwind.js`

**Watcher**  
`node ./node_modules/@spicycoding/sass-compiler/src/cli.js watch --target ./resources/assets/sass/app.scss --destination ./public/dist/app.css --configuration ./tailwind.js`

**Production**  
`node ./node_modules/@spicycoding/sass-compiler/src/cli.js build --target ./resources/assets/sass/app.scss --destination ./public/dist/app.css --configuration ./tailwind.js --minify`
npm package: @spicycoding/vue-auto-suggest
Description: Auto suggest on an input field by providing an array of possible values.
Author: Pim vd Molen
Latest version: 1.0.2

This vue component displays suggestions based on the current value of the input field.

**How to install**  
Install using NPM: `npm install @spicycoding/vue-auto-suggest`  
Install using Yarn: `yarn add @spicycoding/vue-auto-suggest`

**Important note**
This package assumes that you have installed these packages:
- font-awesome
- tailwindcss

# How to use
```
import autoSuggest from '@spicycoding/vue-auto-suggest';

new Vue({
    components: {
        'auto-suggest': autoSuggest,
    },
});
```

```
<auto-suggest placeholder="What are you searching for?" :value="''" :on-input="myMethod" :options="['Netherlands', 'Belgium', 'Germany', 'Italy']"></auto-suggest>
```

In your own application, create a method that accepts one parameter:
```
myMethod(response) {
    console.log(response);
}
```