open-index/open-npm huggingface dataset:
npm package: @mothership-gmbh/nuxt-shopware-caching
Description: Nuxt-Module, that provides a system to set shopware cache-tags for later use in e.g. a full-page cache.   This module is meant to be used together with the [companion bundle for Shopware](https://github.com/mothership-gmbh/headless-shopware-varnish-cache)
Latest version: 2.1.0

# nuxt-shopware-caching
Nuxt-Module, that provides a system to set shopware cache-tags for later use in e.g. a full-page cache.  
This module is meant to be used together with the [companion bundle for Shopware](https://github.com/mothership-gmbh/headless-shopware-varnish-cache)

# Installation
- NPM: `npm install @mothership-gmbh/nuxt-shopware-caching`
- pnpm: `pnpm install @mothership-gmbh/nuxt-shopware-caching`
- Yarn: `yarn add @mothership-gmbh/nuxt-shopware-caching`

# Usage
## Add the module
Add the module in your `nuxt.config.js`:
```js
{
    modules: [
        "@mothership-gmbh/nuxt-shopware-caching"
    ],
        
    nuxtShopwareCaching: {
        cacheKeyHeader: 'X-Cache-Tags', // Optional
        cacheKeySeparator: ',',  // Optional
        useXKey: true // Optional: set to true if you intend to use Varnish xkey. If set, also overrides cacheKeyHeader and cacheKeySeparator accordingly.
    }
}
```

## Use the composable in your vue components

```vue
<script setup>
  const {addProductCacheTag} = useCache();
  addProductCacheTag('1234');
</script>
```
The module will then aggregate all cache tags on the page and attach them
- in a comma-separated list to the HTTP response as a `X-Cache-Tags`-header (default configuration)
- in a space-separated list to the HTTP response as a `xkey`-header (if you provided the option in your nuxt config).

Example HTTP-Response headers:
```
X-Cache-Tags: topbar-route,base-navigation,navigation-route-e41d381d990346bebff2a736b7b12c5c,cms-page-da2ad0281b4d4fc4ae7c6f3a68700e59,product-5b5e2f24dced46cdba488c01b9c12130,product-1c150aab458940c28a30202abc404b96
```
or
```
xkey: topbar-route base-navigation navigation-route-e41d381d990346bebff2a736b7b12c5c cms-page-da2ad0281b4d4fc4ae7c6f3a68700e59 product-5b5e2f24dced46cdba488c01b9c12130 product-1c150aab458940c28a30202abc404b96
```

## Reference
### composable useCache
```typescript
export declare const useCache: () => {
    addCacheTag: (tag: string) => void;
    addProductCacheTag: (productId: string) => void;
    addProductListingCacheTag: (productId: string) => void;
    addCategoryCacheTag: (categoryId: string) => void;
    addNavigationRouteCacheTag: (categoryId: string) => void;
    addBaseNavigationCacheTag: () => void;
    addCmsPageCacheTag: (cmsPageId: string) => void;
    addLandingPageCacheTag: (landingPageId: string) => void;
};
```

## Development

- Run `npm run dev:prepare` to generate type stubs.
- Use `npm run dev` to start [playground](./playground) in development mode.
npm package: @mothership-rpg/characters
Description: A library for creating characters in Mothership RPG
Latest version: 1.0.2

# @mothership-rpg/characters

![](https://badgers.space/npm/name/@mothership-rpg/characters)
![](https://badgers.space/github/release/MothershipRPGTools/generators-ts)
![](https://badgers.space/github/license/MothershipRPGTools/generators-ts)
![](https://badgers.space/codeberg/stars/MothershipRPGTools/generators-ts)


# Character generation

```bash
❯ npm install @mothership-rpg/characters
```

```typescript
import { Character } from "@mothership-rpg/characters";

const character = new Character();
console.log(character);
```

Output:

```typescript
Character {
  maxWounds: 2,
  skills: [
    TrainedSkill { name: 'Industrial Equipment', dependsOn: undefined },
    TrainedSkill { name: 'Zero-G', dependsOn: undefined },
    ExpertSkill { name: 'Pathology', dependsOn: [Array] },
    TrainedSkill { name: 'Botany', dependsOn: undefined }
  ],
  classType: Teamster {
    TRAUMA_RESPONSE: 'Once per session, you may take advantage on a panic check.'
  },
  saves: { sanity: 30, fear: 38, body: 23 },
  stats: { strength: 49, speed: 34, intellect: 50, combat: 38 },
  name: 'Jill Robel'
}
```
npm package: @mothership-rpg/wounds
Description: A library for generating wounds in Mothership RPG
Latest version: 1.0.2

# @mothership-rpg/wounds

![](https://badgers.space/npm/name/@mothership-rpg/wounds)
![](https://badgers.space/github/release/MothershipRPGTools/generators-ts)
![](https://badgers.space/github/license/MothershipRPGTools/generators-ts)
![](https://badgers.space/codeberg/stars/MothershipRPGTools/generators-ts)


# Wound generation

```bash
❯ npm install @mothership-rpg/wounds
```

```typescript
import { Wound, BluntForce } from "@mothership-rpg/wounds";

const wound = new Wound(BluntForce);
console.log(wound.rollSeverity());
```

Output:

```typescript
Character {
  maxWounds: 2,
  skills: [
    TrainedSkill { name: 'Industrial Equipment', dependsOn: undefined },
    TrainedSkill { name: 'Zero-G', dependsOn: undefined },
    ExpertSkill { name: 'Pathology', dependsOn: [Array] },
    TrainedSkill { name: 'Botany', dependsOn: undefined }
  ],
  classType: Teamster {
    TRAUMA_RESPONSE: 'Once per session, you may take advantage on a panic check.'
  },
  saves: { sanity: 30, fear: 38, body: 23 },
  stats: { strength: 49, speed: 34, intellect: 50, combat: 38 },
  name: 'Jill Robel'
}
```
npm package: @mothershipvc/vue-contenteditable
Description: Vue.js plugin providing a <contenteditable/> element supporting v-model. It also provides some (optional) features, like preventing html input / paste or new lines.
Author: Léo Flaventin Hauchecorne
Latest version: 1.0.3

vue-contenteditable
===================

This plugin provides a ``<contenteditable/>`` element supporting ``v-model``. It also provides some (optional) features, like preventing html input / paste or new lines.

It is inpired by the nice (but limited by design) https://github.com/asconwe/vue-contenteditable-directive .

Contrary to ``vue-contenteditable-directive``, this plugin has full support of v-model reactivity.

Should you use a content editable ?
-----------------------------------

The response is generally **NO**.

But... there are edge cases where neither ``<input/>`` nor ``<textarea>`` could suit, for example when you need a dynamic object size to adapt to user input text size.

Installation
------------

With a build system
```````````````````

.. code:: 

    npm install --save vue-contenteditable

In your ``main.js`` :

.. code:: javascript

    import contenteditable from 'vue-contenteditable'
    Vue.use(contenteditable)

(Re)build
`````````

The needed files are already provided in ``dist/``, but if you want to re build, simlply run :

.. code::

    npm run build

Directely in html
`````````````````

.. code:: html

	 <script src="contenteditable.min.js"></script>

Usage
-----

Where you need a ``contenteditable`` element :

.. code:: javascript

    <template>
      <contenteditable tag="div" :contenteditable="isEditable" v-model="message" :noNL="true" @returned="enterPressed" />
    </template>
     
    <script>
    export default {
      data() {
        return {
          isEditable: true,
          message: "hello"
        }
      },
      methods : {
        enterPressed(){
          alert('Enter Pressed');
        }
      }
    }

Props
`````

``tag``
  ``String``
  Html element type (``p``, ``div``...)

``v-model``
  ``v-model`` as usually used with ``<input/>`` and ``<textarea/>``

``:contenteditable``
  (Default : ``true``)
  Forwarded to DOM's `contenteditable <https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement/contentEditable>`_.

``noHTML``
  (Default : ``true``)
  Prevent insertion (either typed or pasted) of html text

``noNL``
  (Default : ``false``)
  Prevent insertion of new-lines. Also activate ``returned`` event emission

``v-on:...``
  All comon input DOM events are forwarded, so that you can use ``v-on`` as usual.

Events
``````

``returned``
  When the user press :kbd:Return and ``noNL`` is set, then it emits the ``returned`` event with the current value (as ``String``) as argument.

License
-------

This code is provided as-is, under the terms of the MIT license (see License file for more details).

A link to the original sources and contribution / pull request are welcome if you enjoy / use / contribute to this module ! :)
npm package: @motiadev/cron-plugin
Description: A Motia workbench plugin for monitoring and managing cron jobs.
Author: Motia Team
Latest version: 0.17.13-beta.195

# @motiadev/cron-plugin

A Motia workbench plugin for monitoring and managing cron jobs (scheduled tasks).

## Overview

This plugin adds a "Cron Jobs" tab to the Motia workbench bottom panel, providing:

- Real-time cron job monitoring
- Human-readable cron expression descriptions
- Next/last execution time display
- Execution history with duration tracking
- Manual job triggering
- Enable/disable job controls
- Status filtering (idle, running, completed, failed, disabled)
- Search functionality

## Installation

```bash
npm install @motiadev/cron-plugin
# or
pnpm add @motiadev/cron-plugin
```

## Usage

Add the plugin to your `motia.config.ts`:

```typescript
import cronPlugin from '@motiadev/cron-plugin/plugin'

export default {
  plugins: [cronPlugin],
}
```

The plugin will automatically appear as a "Cron Jobs" tab in the bottom panel of your Motia workbench.

## Features

### Job Monitoring

- View all registered cron steps
- Real-time status updates via WebSocket
- Countdown timer to next execution

### Job Controls

- **Trigger**: Manually run a cron job
- **Enable/Disable**: Toggle job scheduling
- **View History**: See past executions with timing

### Execution Tracking

- Duration measurement for each run
- Error capturing and display
- Trace ID correlation

### Filtering

- Filter by status (idle, running, failed, etc.)
- Search by job name or description
- Filter by associated flow

## Exported APIs

```typescript
// Main component
export { CronJobsPage, CronJobCard } from '@motiadev/cron-plugin'

// Types
export type { CronJob, CronExecution, CronStats, CronFilter } from '@motiadev/cron-plugin'

// Zustand store
export { useCronStore } from '@motiadev/cron-plugin'

// Hooks
export { useCronMonitor, useCronJobs, useJobExecutions, useCronStats } from '@motiadev/cron-plugin'
```

## Development

```bash
pnpm install
pnpm run dev      # Watch mode
pnpm run build    # Production build
pnpm run clean    # Remove dist/
```

## Requirements

- Motia with `@motiadev/core` and `@motiadev/ui`
- React 19+

## License

MIT
npm package: @motiadev/plugin-cron
Description: A Motia workbench plugin for monitoring and managing cron jobs.
Author: Motia Team
Latest version: 0.17.14-beta.196

# @motiadev/plugin-cron

A Motia workbench plugin for monitoring and managing cron jobs (scheduled tasks).

## Overview

This plugin adds a "Cron Jobs" tab to the Motia workbench bottom panel, providing:

- Real-time cron job monitoring
- Human-readable cron expression descriptions
- Next/last execution time display
- Execution history with duration tracking
- Manual job triggering
- Enable/disable job controls
- Status filtering (idle, running, completed, failed, disabled)
- Search functionality

## Installation

```bash
npm install @motiadev/plugin-cron
# or
pnpm add @motiadev/plugin-cron
```

## Usage

Add the plugin to your `motia.config.ts`:

```typescript
import cronPlugin from '@motiadev/plugin-cron/plugin'

export default {
  plugins: [cronPlugin],
}
```

The plugin will automatically appear as a "Cron Jobs" tab in the bottom panel of your Motia workbench.

## Features

### Job Monitoring

- View all registered cron steps
- Real-time status updates via WebSocket
- Countdown timer to next execution

### Job Controls

- **Trigger**: Manually run a cron job
- **Enable/Disable**: Toggle job scheduling
- **View History**: See past executions with timing

### Execution Tracking

- Duration measurement for each run
- Error capturing and display
- Trace ID correlation

### Filtering

- Filter by status (idle, running, failed, etc.)
- Search by job name or description
- Filter by associated flow

## Exported APIs

```typescript
// Main component
export { CronJobsPage, CronJobCard } from '@motiadev/plugin-cron'

// Types
export type { CronJob, CronExecution, CronStats, CronFilter } from '@motiadev/plugin-cron'

// Zustand store
export { useCronStore } from '@motiadev/plugin-cron'

// Hooks
export { useCronMonitor, useCronJobs, useJobExecutions, useCronStats } from '@motiadev/plugin-cron'
```

## Development

```bash
pnpm install
pnpm run dev      # Watch mode
pnpm run build    # Production build
pnpm run clean    # Remove dist/
```

## Requirements

- Motia with `@motiadev/core` and `@motiadev/ui`
- React 19+

## License

MIT
npm package: @motiadev/plugin-ws
Description: A Motia workbench plugin for real-time WebSocket log monitoring and debugging. Originally created by @potatocoder (Rohith Gilla).
Author: Motia Team
Latest version: 0.17.14-beta.196

# @motiadev/plugin-ws

A Motia workbench plugin for real-time WebSocket log monitoring and debugging.

![WebSocket Plugin Screenshot](assets/screenshot.png)

> **Credits**: Originally created by [@potatocoder](https://github.com/Rohithgilla12) (Rohith Gilla) as [@potatocoder/ws-plugin](https://github.com/Rohithgilla12/motia-ws-plugin). Now maintained as an official Motia plugin.

## Overview

This plugin adds a "WebSockets" tab to the Motia workbench bottom panel, providing:

- Real-time WebSocket message monitoring
- Stream subscription management (logs, API endpoints, custom streams)
- JSON syntax highlighting with expand/collapse for large payloads
- Message filtering by stream
- Connection status indicators
- Copy-to-clipboard functionality

## Installation

```bash
npm install @motiadev/plugin-ws
# or
pnpm add @motiadev/plugin-ws
```

## Usage

Add the plugin to your `motia.config.ts`:

```typescript
import wsPlugin from '@motiadev/plugin-ws/plugin'

export default {
  plugins: [wsPlugin],
}
```

The plugin will automatically appear as a "WebSockets" tab in the bottom panel of your Motia workbench.

## Features

### Stream Subscriptions

The plugin auto-subscribes to default Motia streams on connection:
- `__motia.logs` - Application logs
- `__motia.api-endpoints` - API request/response events

Add custom streams via the "Add" button in the stream bar.

### Message Types

Messages are color-coded by type:
- **System** - Connection events (amber)
- **Error** - Error messages (red)
- **Sync/Create/Update/Delete** - CRUD operations (various colors)
- **Sent** - Outgoing messages (blue)

### Exported APIs

```typescript
// Main component
export { WebSocketsPage } from '@motiadev/plugin-ws'

// Types
export type { WebSocketConnection, WebSocketMessage, WebSocketStats } from '@motiadev/plugin-ws'

// Zustand store for external state access
export { useWebSocketStore } from '@motiadev/plugin-ws'

// Hooks
export { useWebSocketConnections, useWebSocketMessages } from '@motiadev/plugin-ws'
```

## Development

```bash
pnpm install
pnpm run dev      # Watch mode
pnpm run build    # Production build
pnpm run clean    # Remove dist/
```

## Requirements

- Motia with `@motiadev/core` and `@motiadev/ui`
- React 19+

## Contributors

Special thanks to:
- **Rohith Gilla** ([@Rohithgilla12](https://github.com/Rohithgilla12)) - Original plugin creator

## License

MIT
npm package: @motiadev/ws-plugin
Description: A Motia workbench plugin for real-time WebSocket log monitoring and debugging. Originally created by @potatocoder (Rohith Gilla).
Author: Motia Team
Latest version: 0.17.13-beta.195

# @motiadev/ws-plugin

A Motia workbench plugin for real-time WebSocket log monitoring and debugging.

![WebSocket Plugin Screenshot](assets/screenshot.png)

> **Credits**: Originally created by [@potatocoder](https://github.com/Rohithgilla12) (Rohith Gilla) as [@potatocoder/ws-plugin](https://github.com/Rohithgilla12/motia-ws-plugin). Now maintained as an official Motia plugin.

## Overview

This plugin adds a "WebSockets" tab to the Motia workbench bottom panel, providing:

- Real-time WebSocket message monitoring
- Stream subscription management (logs, API endpoints, custom streams)
- JSON syntax highlighting with expand/collapse for large payloads
- Message filtering by stream
- Connection status indicators
- Copy-to-clipboard functionality

## Installation

```bash
npm install @motiadev/ws-plugin
# or
pnpm add @motiadev/ws-plugin
```

## Usage

Add the plugin to your `motia.config.ts`:

```typescript
import wsPlugin from '@motiadev/ws-plugin/plugin'

export default {
  plugins: [wsPlugin],
}
```

The plugin will automatically appear as a "WebSockets" tab in the bottom panel of your Motia workbench.

## Features

### Stream Subscriptions

The plugin auto-subscribes to default Motia streams on connection:
- `__motia.logs` - Application logs
- `__motia.api-endpoints` - API request/response events

Add custom streams via the "Add" button in the stream bar.

### Message Types

Messages are color-coded by type:
- **System** - Connection events (amber)
- **Error** - Error messages (red)
- **Sync/Create/Update/Delete** - CRUD operations (various colors)
- **Sent** - Outgoing messages (blue)

### Exported APIs

```typescript
// Main component
export { WebSocketsPage } from '@motiadev/ws-plugin'

// Types
export type { WebSocketConnection, WebSocketMessage, WebSocketStats } from '@motiadev/ws-plugin'

// Zustand store for external state access
export { useWebSocketStore } from '@motiadev/ws-plugin'

// Hooks
export { useWebSocketConnections, useWebSocketMessages } from '@motiadev/ws-plugin'
```

## Development

```bash
pnpm install
pnpm run dev      # Watch mode
pnpm run build    # Production build
pnpm run clean    # Remove dist/
```

## Requirements

- Motia with `@motiadev/core` and `@motiadev/ui`
- React 19+

## Contributors

Special thanks to:
- **Rohith Gilla** ([@Rohithgilla12](https://github.com/Rohithgilla12)) - Original plugin creator

## License

MIT