open-index/open-npm huggingface dataset:
npm package: @kitql/all-in
Description: [KitQL](https://github.com/jycouet/kitql#kitql), _A set of tools, helping **you** building efficient apps in a fast way._
Latest version: 0.9.6
Deprecated: Check out https://kitql.dev/ for more info!

# KitQL - all-in

[KitQL](https://github.com/jycouet/kitql#kitql), _A set of tools, helping **you** building efficient apps in a fast way._

<p align="center">
  <img src="../../logo.svg" width="100" />
</p>

## Check the [⚡Doc⚡](https://kitql.dev/docs/all-in)
npm package: @kitql/client
Description: ![](https://img.shields.io/badge/State-deprecated-red)
Latest version: 0.5.12
Deprecated: check @kitql/all-in

# KitQL - client

![](https://img.shields.io/badge/State-deprecated-red)

This _sub package_ of KitQL has been deprecated. It is no longer maintained and will be removed in the future.

Please

<p align="center">
  <img src="../../logo.svg" width="100" />
</p>
npm package: @kitql/comp
Description: [KitQL](https://github.com/jycouet/kitql#kitql), _A set of tools, helping **you** building efficient apps in a fast way._
Latest version: 0.1.2
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# KitQL - comp

[KitQL](https://github.com/jycouet/kitql#kitql), _A set of tools, helping **you** building efficient apps in a fast way._

<p align="center">
  <img src="../../logo.svg" width="100" />
</p>

## Check the [⚡Doc⚡](https://kitql.vercel.app/docs/setup/02_client)
npm package: @kitql/eslint-config
Description: opinionated linting and formatting for projects
Latest version: 0.8.1

# 👌 @kitql/eslint-config

[![](https://img.shields.io/npm/v/@kitql/eslint-config?color=&logo=npm)](https://www.npmjs.com/package/@kitql/eslint-config)
[![](https://img.shields.io/npm/dm/@kitql/eslint-config?&logo=npm)](https://www.npmjs.com/package/@kitql/eslint-config)

## 📖 Read the doc

[![](https://img.shields.io/badge/Documentation%20of-kitql%20lint%20format-FF3E00.svg?style=flat&logo=stackblitz&logoColor=FF3E00)](https://kitql.dev/docs/tools/08_eslint-config)

## Install

```bash
npm install @kitql/eslint-config --D
```

### eslint config

`.eslint.config.js`

```js
import { kitql } from '@kitql/eslint-config'

export default [...kitql()]
```

### prettier config

`.prettierrc.cjs`

```js
import { kitql } from './packages/eslint-config/.prettierrc.cjs'

export default {
  ...kitql(),
  // Some custom things?
}
```

### ignore things with

`.prettierignore`

```bash
.DS_Store
node_modules
/build
/.svelte-kit
/package
.env
.env.*
!.env.example

# Ignore files for PNPM, NPM and YARN
pnpm-lock.yaml
package-lock.json
yarn.lock

# Ignore files that are project specific
/db
```

### usage

```bash
# lint
npm exec kitql-lint

# format
npm exec kitql-lint --format
```

## ⭐️ Join us

[![GitHub Repo stars](https://img.shields.io/github/stars/jycouet/kitql?logo=github&label=KitQL&color=#4ACC31)](https://github.com/jycouet/kitql)

💡 _[KitQL](https://www.kitql.dev/docs) itself is not a library, it's "nothing" but a collection of
standalone libraries._
npm package: @kitql/graphql-codegen
Description: GraphQL Code Generator plugin to generate SvelteKit stores in kitql context
Latest version: 0.5.4
Deprecated: check @kitql/all-in

# KitQL - graphql-codegen

![](https://img.shields.io/badge/State-deprecated-red)

This _sub package_ of KitQL has been deprecated. It is no longer maintained and will be removed in the future.

Please

<p align="center">
  <img src="../../logo.svg" width="100" />
</p>
npm package: @kitql/handles
Description: Some useful handles for SvelteKit
Latest version: 0.3.1

# 🔀 KitQL - Handles

[![](https://img.shields.io/npm/v/@kitql/handles?color=&logo=npm)](https://www.npmjs.com/package/@kitql/handles)
[![](https://img.shields.io/npm/dm/@kitql/handles?&logo=npm)](https://www.npmjs.com/package/@kitql/handles)

## 📖 Read the doc

[![](https://img.shields.io/badge/Documentation%20of-@kitql%20handles-FF3E00.svg?style=flat&logo=stackblitz&logoColor=FF3E00)](https://kitql.dev/docs/tools/05_handles)

## ⭐️ Join us

[![GitHub Repo stars](https://img.shields.io/github/stars/jycouet/kitql?logo=github&label=KitQL&color=#4ACC31)](https://github.com/jycouet/kitql)

💡 _[KitQL](https://www.kitql.dev/docs) itself is not a library, it's "nothing" but a collection of
standalone libraries._
npm package: @kitql/helpers
Description: Some useful helpers (0 deps)
Latest version: 0.8.13

# ⚡ KitQL - Helpers

[![](https://img.shields.io/npm/v/@kitql/helpers?color=&logo=npm)](https://www.npmjs.com/package/@kitql/helpers)
[![](https://img.shields.io/npm/dm/@kitql/helpers?&logo=npm)](https://www.npmjs.com/package/@kitql/helpers)

## 📖 Read the doc

[![](https://img.shields.io/badge/Documentation%20of-vite%20plugin%20kit%20routes-FF3E00.svg?style=flat&logo=stackblitz&logoColor=FF3E00)](https://kitql.dev/docs/tools/04_helpers)

## ✅ Important notes

It's a
![](https://img.shields.io/badge/0-Dependencies-FF3E00.svg?style=flat&logo=stackblitz&logoColor=FF3E00)
package.

[![](https://img.shields.io/badge/4.7%20gzip-pkg%20size.dev-FF3E00.svg?style=flat&logo=stackblitz&logoColor=FF3E00)](https://pkg-size.dev/@kitql%2Fhelpers)
is the "full" size. But, code splitting is always in mind so that you ship as less as possible in
the browser! _(Check out by selecting what you use)_

## ⭐️ Join us

[![GitHub Repo stars](https://img.shields.io/github/stars/jycouet/kitql?logo=github&label=KitQL&color=#4ACC31)](https://github.com/jycouet/kitql)

💡 _[KitQL](https://www.kitql.dev/docs) itself is not a library, it's "nothing" but a collection of
standalone libraries._
npm package: @kitql/internals
Description: Some useful internals
Latest version: 0.11.0

# ⚡ KitQL - Internals

[![](https://img.shields.io/npm/v/@kitql/internals?color=&logo=npm)](https://www.npmjs.com/package/@kitql/internals)
[![](https://img.shields.io/npm/dm/@kitql/internals?&logo=npm)](https://www.npmjs.com/package/@kitql/internals)

## 📖 Read the doc

[![](https://img.shields.io/badge/Documentation%20of-@kitql%20internals-FF3E00.svg?style=flat&logo=stackblitz&logoColor=FF3E00)](https://kitql.dev)

## ⭐️ Join us

[![GitHub Repo stars](https://img.shields.io/github/stars/jycouet/kitql?logo=github&label=KitQL&color=#4ACC31)](https://github.com/jycouet/kitql)

💡 _[KitQL](https://www.kitql.dev/docs) itself is not a library, it's "nothing" but a collection of
standalone libraries._
npm package: @kitql/sv
Description: sv add-on for KitQL
Latest version: 0.1.2

# [sv](https://svelte.dev/docs/cli/overview) community add-on: [@kitql/sv](https://github.com/@kitql/sv)

> [!IMPORTANT]
> Svelte maintainers have not reviewed community add-ons for malicious code. Use at your discretion

## Usage

To install the add-on, run:

```shell
npx sv add @kitql
```

## What you get

One of these:

- Scaffolding for remote functions
- Add `@KitQL/helpers`
- Add `vite-plugin-kit-routes`

## Cool one liners

```sh
npx sv create --template minimal --types ts --add @kitql="topics:demo-remote-functions+rfTopic:stuff"
```
npm package: @kitql/sveltekit
Description: kitql sveltekit helpers
Latest version: 0.0.5

# ⚡ KitQL - Svelte

[![](https://img.shields.io/npm/v/@kitql/sveltekit?color=&logo=npm)](https://www.npmjs.com/package/@kitql/sveltekit)
[![](https://img.shields.io/npm/dm/@kitql/sveltekit?&logo=npm)](https://www.npmjs.com/package/@kitql/sveltekit)

## 📖 Read the doc

[![](https://img.shields.io/badge/Documentation%20of-@kitql/sveltekit-FF3E00.svg?style=flat&logo=stackblitz&logoColor=FF3E00)](https://kitql.dev/docs/tools/10_sveltekit)

## ⭐️ Join us

[![GitHub Repo stars](https://img.shields.io/github/stars/jycouet/kitql?logo=github&label=KitQL&color=#4ACC31)](https://github.com/jycouet/kitql)

💡 _[KitQL](https://www.kitql.dev/docs) itself is not a library, it's "nothing" but a collection of
standalone libraries._
npm package: @kitql/template
Description: KitQL template
Latest version: 0.4.3
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# KitQL - graphql-codegen

[KitQL](https://github.com/jycouet/kitql#kitql), _A set of tools, helping **you** building efficient apps in a fast way._

<p align="center">
  <img src="../../logo.svg" width="100" />
</p>

# ⚡How to - graphql-codegen

```bash
pnpm add -D @kitql/graphql-codegen
```

Typical CodeGen file (`.graphqlrc.yaml`)

```yaml
# ...
codegen:
  generates:
    ./graphql/$kitql/graphqlTypes.ts:
      plugins:
        - typescript
        - typescript-resolvers
        - typescript-operations
        - typed-document-node

    ./graphql/$kitql/graphqlStores.ts:
      plugins:
        - '@kitql/graphql-codegen'
      config:
        importBaseTypesFrom: $graphql/$kitql/graphqlTypes # if you don't add this, you have to generate all types in the same file.
# ...
```
npm package: @kitql/vite-plugin-watch-and-run
Description: vite-plugin that will watch some files and run a package.json script on change
Latest version: 0.4.2
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# KitQL - vite-plugin-watch-and-run

[KitQL](https://github.com/jycouet/kitql#kitql), _A set of tools, helping **you** building efficient apps in a fast way._

<p align="center">
  <img src="../../logo.svg" width="100" />
</p>

## Check the [⚡Doc⚡](https://kitql.dev/docs/setup/03_vite-plugin-watch-and-run)
npm package: @kitrak_rev/axios-fetch-adapter
Description: Fetch adapter for axios
Author: nta.toan@gmail.com
Latest version: 0.3.3

# Why

I'm going to adopt PWA to my web applications and those web apps are heavily using Axios with the default XMLHTTPRequest adapter. Hence, I have to switch to Fetch adapter; However, Axios doesn't have an adapter for fetch API for now. So I write one to use while waiting for an offical one from Axios.

# Installation and Usage

You can install the adapter directly from this repository URL or feel free to copy its source code to your project.

``` sh
npm install axios
npm install @vespaiach/axios-fetch-adapter
```

There are two ways to use it:

1.  Create a new instance of Axios and pass this adapter in configuration

``` js
const instance = axios.create({
  baseURL: 'https://some-domain.com/api/',
  timeout: 1000,
  adapter: fetchAdapter
  ....
});
```

2.  Pass this adapter in each of request

``` js
axios.request({
  url: '/user',
  method: 'get',
  adapter: fetchAdapter
  ...
})
```

3.  Use with FormData 

``` js
axios.request({
  url: '/user',
  method: 'post',
  adapter: fetchAdapter
  data: new FormData(formId)
  ...
})
```

# Note

- Since, this adapter relies on fetch API so it won't work in Node environment
npm package: @kitschpatrol/tokei-linux-arm-gnueabihf
Description: Node bindings for Tokei, a fast code counting tool.
Author: Eric Mika
Latest version: 2.0.1

# `@kitschpatrol/tokei-linux-arm-gnueabihf`

This is the **armv7-unknown-linux-gnueabihf** binary for `@kitschpatrol/tokei`
npm package: @kitschpatrol/tokei-linux-arm64-musl
Description: Node bindings for Tokei, a fast code counting tool.
Author: Eric Mika
Latest version: 2.0.1

# `@kitschpatrol/tokei-linux-arm64-musl`

This is the **aarch64-unknown-linux-musl** binary for `@kitschpatrol/tokei`
npm package: @kitschpatrol/tokei-linux-x64-musl
Description: Node bindings for Tokei, a fast code counting tool.
Author: Eric Mika
Latest version: 2.0.1

# `@kitschpatrol/tokei-linux-x64-musl`

This is the **x86_64-unknown-linux-musl** binary for `@kitschpatrol/tokei`
npm package: @kitschpatrol/tokei-win32-arm64-msvc
Description: Node bindings for Tokei, a fast code counting tool.
Author: Eric Mika
Latest version: 2.0.1

# `@kitschpatrol/tokei-win32-arm64-msvc`

This is the **aarch64-pc-windows-msvc** binary for `@kitschpatrol/tokei`
npm package: @kitschpatrol/tokei-win32-ia32-msvc
Description: Node bindings for Tokei, a fast code counting tool.
Author: Eric Mika
Latest version: 2.0.1

# `@kitschpatrol/tokei-win32-ia32-msvc`

This is the **i686-pc-windows-msvc** binary for `@kitschpatrol/tokei`
npm package: @kitschpatrol/tokei-win32-x64-msvc
Description: Node bindings for Tokei, a fast code counting tool.
Author: Eric Mika
Latest version: 2.0.1

# `@kitschpatrol/tokei-win32-x64-msvc`

This is the **x86_64-pc-windows-msvc** binary for `@kitschpatrol/tokei`
npm package: @kitschpatrol/tweakpane-image-plugin
Description: Renamed to @kitschpatrol/tweakpane-plugin-image
Author: Florian Morel, Matheus Dias
Latest version: 2.0.1
Deprecated: Renamed to @kitschpatrol/tweakpane-plugin-image. If you're using svelte-tweakpane-ui and seeing this warning, please upgrade svelte-tweakpane-ui to a version >=1.2.6.

# `@kitschpatrol/tweakpane-image-plugin`

_**Deprecated. Renamed to [@kitschpatrol/tweakpane-plugin-image](https://github.com/kitschpatrol/tweakpane-plugin-image).**_
npm package: @kitschpatrol/tweakpane-plugin-camerakit
Description: A fork of @tweakpane/plugin-camerakit with build optimizations.
Author: cocopon
Latest version: 0.3.1-beta.3

# @kitschpatrol/tweakpane-plugin-camerakit

[![NPM Package @kitschpatrol/tweakpane-plugin-camerakit](https://img.shields.io/npm/v/@kitschpatrol/tweakpane-plugin-camerakit.svg)](https://npmjs.com/package/@kitschpatrol/tweakpane-plugin-camerakit)

## Overview

**This is a fork of [Hiroki Kokubun](https://cocopon.me/)'s [@tweakpane/plugin-camerakit
](https://github.com/tweakpane/plugin-camerakit) with externalized dependencies.**

This allows for smaller bundled file sizes in projects using multiple Tweakpane plugins.

It is published to NPM primarily for the [_Svelte Tweakpane UI_](https://kitschpatrol.com/svelte-tweakpane-ui) project, and will be kept in sync with the upstream version of the plugin, with minimal changes other than dependency externalization.

For most use cases, you probably don't want this fork!

## Background

The [Rollup](https://rollupjs.org) configuration provided in the [Tweakpane plugin template](https://github.com/tweakpane/plugin-template) does not externalize [`@tweakpane/core`](https://github.com/cocopon/tweakpane/tree/main/packages/core) as a production dependency.

Instead, it gets built into the single-file plugin artifact, which is what's published to NPM and imported by plugin consumers. This makes it easy to import as an ES module from a URL, but means that larger projects importing multiple Tweakpane plugins end up with duplicate copies of the `@tweakpane/core` code, adding about ~100 Kb to the final minified build for each plugin after the first.

Externalizing this dependency allows build tools like [vite](https://vitejs.dev) to share a single instance of the `@tweakpane/core` code across multiple plugins.

If you're not using a bundler, direct ESM imports from URLs can still work by defining the `@tweakpane/core` dependency in an [importmap](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script/type/importmap).

## Implementation notes

Note the package name change from `@tweakpane/plugin-camerakit` to `@kitschpatrol/tweakpane-plugin-camerakit`.

PNPM is used as the package manager.

## Versioning

In addition to the dependency externalization change, this fork also includes assorted dependency updates. In an effort to stay in sync with future upstream versions, intra-minor-version releases of the fork are tagged as "betas" of what would / will be the next patch release upstream.
npm package: @kitschpatrol/tweakpane-plugin-essentials
Description: A fork of @tweakpane/plugin-essentials with build optimizations.
Author: cocopon
Latest version: 0.2.2-beta.3

# @kitschpatrol/tweakpane-plugin-essentials

[![NPM Package @kitschpatrol/tweakpane-plugin-essentials](https://img.shields.io/npm/v/@kitschpatrol/tweakpane-plugin-essentials.svg)](https://npmjs.com/package/@kitschpatrol/tweakpane-plugin-essentials)

## Overview

**This is a fork of [Hiroki Kokubun](https://cocopon.me/)'s [@tweakpane/plugin-essentials
](https://github.com/tweakpane/plugin-essentials) with externalized dependencies.**

This allows for smaller bundled file sizes in projects using multiple Tweakpane plugins.

It is published to NPM primarily for the [_Svelte Tweakpane UI_](https://kitschpatrol.com/svelte-tweakpane-ui) project, and will be kept in sync with the upstream version of the plugin, with minimal changes other than dependency externalization.

It also incorporates a [fix for a CubicBezier performance issue](https://github.com/tweakpane/plugin-essentials/pull/21).

For most use cases, you probably don't want this fork!

## Background

The [Rollup](https://rollupjs.org) configuration provided in the [Tweakpane plugin template](https://github.com/tweakpane/plugin-template) does not externalize [`@tweakpane/core`](https://github.com/cocopon/tweakpane/tree/main/packages/core) as a production dependency.

Instead, it gets built into the single-file plugin artifact, which is what's published to NPM and imported by plugin consumers. This makes it easy to import as an ES module from a URL, but means that larger projects importing multiple Tweakpane plugins end up with duplicate copies of the `@tweakpane/core` code, adding about ~100 Kb to the final minified build for each plugin after the first.

Externalizing this dependency allows build tools like [vite](https://vitejs.dev) to share a single instance of the `@tweakpane/core` code across multiple plugins.

If you're not using a bundler, direct ESM imports from URLs can still work by defining the `@tweakpane/core` dependency in an [importmap](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script/type/importmap).

## Implementation notes

Note the package's name change from `@tweakpane/plugin-essentials` to `@kitschpatrol/tweakpane-plugin-essentials`.

PNPM is used as the package manager.

## Versioning

In addition to the dependency externalization change, this fork also includes assorted dependency updates. In an effort to stay in sync with future upstream versions, intra-minor-version releases of the fork are tagged as "betas" of what would / will be the next patch release upstream.
npm package: @kitschpatrol/tweakpane-plugin-file-import
Description: A fork of tweakpane-plugin-file-import with build optimizations.
Author: LuchoTurtle
Latest version: 1.1.2-beta.2

# @kitschpatrol/tweakpane-plugin-file-import

[![NPM Package @kitschpatrol/tweakpane-plugin-file-import](https://img.shields.io/npm/v/@kitschpatrol/tweakpane-plugin-file-import.svg)](https://npmjs.com/package/@kitschpatrol/tweakpane-plugin-file-import)

## Overview

**This is a fork of [LuchoTurtle](https://github.com/LuchoTurtle)'s [tweakpane-plugin-file-import](https://github.com/LuchoTurtle/tweakpane-plugin-file-import) with externalized dependencies.**

This allows for smaller bundled file sizes in projects using multiple Tweakpane plugins.

It is published to NPM primarily for the [_Svelte Tweakpane UI_](https://kitschpatrol.com/svelte-tweakpane-ui) project, and will be kept in sync with the upstream version of the plugin, with minimal changes other than dependency externalization.

For most use cases, you probably don't want this fork!

## Background

The [Rollup](https://rollupjs.org) configuration provided in the [Tweakpane plugin template](https://github.com/tweakpane/plugin-template) does not externalize [`@tweakpane/core`](https://github.com/cocopon/tweakpane/tree/main/packages/core) as a production dependency.

Instead, it gets built into the single-file plugin artifact, which is what's published to NPM and imported by plugin consumers. This makes it easy to import as an ES module from a URL, but means that larger projects importing multiple Tweakpane plugins end up with duplicate copies of the `@tweakpane/core` code, adding about ~100 Kb to the final minified build for each plugin after the first.

Externalizing this dependency allows build tools like [vite](https://vitejs.dev) to share a single instance of the `@tweakpane/core` code across multiple plugins.

If you're not using a bundler, direct ESM imports from URLs can still work by defining the `@tweakpane/core` dependency in an [importmap](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script/type/importmap).

## Implementation notes

PNPM is used as the package manager.

## Versioning

In addition to the dependency externalization change, this fork also includes assorted dependency updates. In an effort to stay in sync with future upstream versions, intra-minor-version releases of the fork are tagged as "betas" of what would / will be the next patch release upstream.
npm package: @kitschpatrol/tweakpane-plugin-inputs
Description: A fork of tweakpane-plugin-inputs with build optimizations.
Author: tallneil
Latest version: 1.0.4-beta.5

# @kitschpatrol/tweakpane-plugin-inputs

[![NPM Package @kitschpatrol/tweakpane-plugin-inputs](https://img.shields.io/npm/v/@kitschpatrol/tweakpane-plugin-inputs.svg)](https://npmjs.com/package/@kitschpatrol/tweakpane-plugin-inputs)

## Overview

**This is a fork of [Neil Shankar](https://tallneil.io/)'s [tweakpane-plugin-inputs](https://github.com/tallneil/tweakpane-plugin-inputs) with externalized dependencies.**

This allows for smaller bundled file sizes in projects using multiple Tweakpane plugins.

It is published to NPM primarily for the [_Svelte Tweakpane UI_](https://kitschpatrol.com/svelte-tweakpane-ui) project, and will be kept in sync with the upstream version of the plugin, with minimal changes other than dependency externalization.

For most use cases, you probably don't want this fork!

## Background

The [Rollup](https://rollupjs.org) configuration provided in the [Tweakpane plugin template](https://github.com/tweakpane/plugin-template) does not externalize [`@tweakpane/core`](https://github.com/cocopon/tweakpane/tree/main/packages/core) as a production dependency.

Instead, it gets built into the single-file plugin artifact, which is what's published to NPM and imported by plugin consumers. This makes it easy to import as an ES module from a URL, but means that larger projects importing multiple Tweakpane plugins end up with duplicate copies of the `@tweakpane/core` code, adding about ~100 Kb to the final minified build for each plugin after the first.

Externalizing this dependency allows build tools like [vite](https://vitejs.dev) to share a single instance of the `@tweakpane/core` code across multiple plugins.

If you're not using a bundler, direct ESM imports from URLs can still work by defining the `@tweakpane/core` dependency in an [importmap](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script/type/importmap).

## Implementation notes

PNPM is used as the package manager.

## Versioning

In addition to the dependency externalization change, this fork also includes assorted dependency updates. In an effort to stay in sync with future upstream versions, intra-minor-version releases of the fork are tagged as "betas" of what would / will be the next patch release upstream.
npm package: @kitschpatrol/tweakpane-plugin-profiler
Description: A fork of tweakpane-plugin-profiler with build optimizations.
Author: 0b5vr
Latest version: 0.4.2-beta.3

# @kitschpatrol/tweakpane-plugin-profiler

[![NPM Package @kitschpatrol/tweakpane-plugin-profiler](https://img.shields.io/npm/v/@kitschpatrol/tweakpane-plugin-profiler.svg)](https://npmjs.com/package/@kitschpatrol/tweakpane-plugin-profiler)

## Overview

**This is a fork of [@0b5vr](https://github.com/0b5vr)'s [tweakpane-plugin-profiler](https://github.com/0b5vr/tweakpane-plugin-profiler) with externalized dependencies.**

This allows for smaller bundled file sizes in projects using multiple Tweakpane plugins.

It is published to NPM primarily for the [_Svelte Tweakpane UI_](https://kitschpatrol.com/svelte-tweakpane-ui) project, and will be kept in sync with the upstream version of the plugin, with minimal changes other than dependency externalization.

For most use cases, you probably don't want this fork!

## Background

The [Rollup](https://rollupjs.org) configuration provided in the [Tweakpane plugin template](https://github.com/tweakpane/plugin-template) does not externalize [`@tweakpane/core`](https://github.com/cocopon/tweakpane/tree/main/packages/core) as a production dependency.

Instead, it gets built into the single-file plugin artifact, which is what's published to NPM and imported by plugin consumers. This makes it easy to import as an ES module from a URL, but means that larger projects importing multiple Tweakpane plugins end up with duplicate copies of the `@tweakpane/core` code, adding about ~100 Kb to the final minified build for each plugin after the first.

Externalizing this dependency allows build tools like [vite](https://vitejs.dev) to share a single instance of the `@tweakpane/core` code across multiple plugins.

If you're not using a bundler, direct ESM imports from URLs can still work by defining the `@tweakpane/core` dependency in an [importmap](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script/type/importmap).

## Implementation notes

This fork uses the main branch for the releases instead of dev.

Note the package's name change from `@0b5vr/tweakpane-plugin-profiler` to `@kitschpatrol/tweakpane-plugin-profiler`.

PNPM is used as the package manager.

## Versioning

In addition to the dependency externalization change, this fork also includes assorted dependency updates. In an effort to stay in sync with future upstream versions, intra-minor-version releases of the fork are tagged as "betas" of what would / will be the next patch release upstream.
npm package: @kitschpatrol/tweakpane-plugin-rotation
Description: A fork of tweakpane-plugin-rotation with build optimizations.
Author: 0b5vr
Latest version: 0.2.1-beta.2

# @kitschpatrol/tweakpane-plugin-rotation

[![NPM Package @kitschpatrol/tweakpane-plugin-rotation](https://img.shields.io/npm/v/@kitschpatrol/tweakpane-plugin-rotation.svg)](https://npmjs.com/package/@kitschpatrol/tweakpane-plugin-rotation)

## Overview

**This is a fork of [0b5vr](https://github.com/0b5vr)'s [tweakpane-plugin-rotation](https://github.com/0b5vr/tweakpane-plugin-rotation) with externalized dependencies.**

This allows for smaller bundled file sizes in projects using multiple Tweakpane plugins.

It is published to NPM primarily for the [_Svelte Tweakpane UI_](https://kitschpatrol.com/svelte-tweakpane-ui) project, and will be kept in sync with the upstream version of the plugin, with minimal changes other than dependency externalization.

For most use cases, you probably don't want this fork!

## Background

The [Rollup](https://rollupjs.org) configuration provided in the [Tweakpane plugin template](https://github.com/tweakpane/plugin-template) does not externalize [`@tweakpane/core`](https://github.com/cocopon/tweakpane/tree/main/packages/core) as a production dependency.

Instead, it gets built into the single-file plugin artifact, which is what's published to NPM and imported by plugin consumers. This makes it easy to import as an ES module from a URL, but means that larger projects importing multiple Tweakpane plugins end up with duplicate copies of the `@tweakpane/core` code, adding about ~100 Kb to the final minified build for each plugin after the first.

Externalizing this dependency allows build tools like [vite](https://vitejs.dev) to share a single instance of the `@tweakpane/core` code across multiple plugins.

If you're not using a bundler, direct ESM imports from URLs can still work by defining the `@tweakpane/core` dependency in an [importmap](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script/type/importmap).

## Implementation notes

This fork uses the main branch for the releases instead of dev.

Note the package's name change from `@0b5vr/tweakpane-plugin-rotation` to `@kitschpatrol/tweakpane-plugin-rotation`.

PNPM is used as the package manager.

## Versioning

In addition to the dependency externalization change, this fork also includes assorted dependency updates. In an effort to stay in sync with future upstream versions, intra-minor-version releases of the fork are tagged as "betas" of what would / will be the next patch release upstream.
npm package: @kitschpatrol/tweakpane-plugin-textarea
Description: A fork of @pangenerator/tweakpane-textarea-plugin with build optimizations.
Author: panGenerator
Latest version: 2.0.1-beta.2

# @kitschpatrol/tweakpane-plugin-textarea

[![NPM Package @kitschpatrol/tweakpane-plugin-textarea](https://img.shields.io/npm/v/@kitschpatrol/tweakpane-plugin-textarea.svg)](https://npmjs.com/package/@kitschpatrol/tweakpane-plugin-textarea)

## Overview

**This is a fork of [Krzysztof Goliński](http://www.golinski.org) and [Jakub Koźniewski](https://pangenerator.com)'s [tweakpane-textarea-plugin](https://github.com/pangenerator/tweakpane-textarea-plugin) with externalized dependencies.**

This allows for smaller bundled file sizes in projects using multiple Tweakpane plugins.

It is published to NPM primarily for the [_Svelte Tweakpane UI_](https://kitschpatrol.com/svelte-tweakpane-ui) project, and will be kept in sync with the upstream version of the plugin, with minimal changes other than dependency externalization.

For most use cases, you probably don't want this fork!

## Background

The [Rollup](https://rollupjs.org) configuration provided in the [Tweakpane plugin template](https://github.com/tweakpane/plugin-template) does not externalize [`@tweakpane/core`](https://github.com/cocopon/tweakpane/tree/main/packages/core) as a production dependency.

Instead, it gets built into the single-file plugin artifact, which is what's published to NPM and imported by plugin consumers. This makes it easy to import as an ES module from a URL, but means that larger projects importing multiple Tweakpane plugins end up with duplicate copies of the `@tweakpane/core` code, adding about ~100 Kb to the final minified build for each plugin after the first.

Externalizing this dependency allows build tools like [vite](https://vitejs.dev) to share a single instance of the `@tweakpane/core` code across multiple plugins.

If you're not using a bundler, direct ESM imports from URLs can still work by defining the `@tweakpane/core` dependency in an [importmap](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script/type/importmap).

## Implementation notes

Note the package's name change from `@pangenerator/tweakpane-textarea-plugin` to `@kitschpatrol/tweakpane-plugin-textarea` in the sanity-preserving spirit of [hierarchical naming](https://en.wikipedia.org/wiki/Reverse_domain_name_notation).

PNPM is used as the package manager.

## Versioning

In addition to the dependency externalization change, this fork also includes assorted dependency updates. In an effort to stay in sync with future upstream versions, intra-minor-version releases of the fork are tagged as "betas" of what would / will be the next patch release upstream.
npm package: @kitschpatrol/tweakpane-plugin-thumbnail-list
Description: A fork of tweakpane-plugin-thumbnail-list with Tweakpane 4 compatibility and externalized dependencies.
Author: Don McCurdy
Latest version: 1.0.4

# @kitschpatrol/tweakpane-plugin-thumbnail-list

[![NPM Package @kitschpatrol/tweakpane-plugin-thumbnail-list](https://img.shields.io/npm/v/@kitschpatrol/tweakpane-plugin-thumbnail-list.svg)](https://npmjs.com/package/@kitschpatrol/tweakpane-plugin-thumbnail-list)

## Overview

**This is a fork of [tweakpane-plugin-thumbnail-list](https://github.com/donmccurdy/tweakpane-plugin-thumbnail-list) with Tweakpane 4.0 compatibility and externalized dependencies.**

It's under consideration for inclusion in the [svelte-tweakpane-ui](https://kitschpatrol.com/svelte-tweakpane-ui) project, but may be useful to others who wish to use the plugin with Tweakpane 4.0.

Please refer to the [upstream project](https://github.com/donmccurdy/tweakpane-plugin-thumbnail-list) for documentation and other details.

## Background

The [Rollup](https://rollupjs.org) configuration provided in the [Tweakpane plugin template](https://github.com/tweakpane/plugin-template) does not externalize [`@tweakpane/core`](https://github.com/cocopon/tweakpane/tree/main/packages/core) as a production dependency.

Instead, it gets built into the single-file plugin artifact, which is what's published to NPM and imported by plugin consumers. This makes it easy to import as an ES module from a URL, but means that larger projects importing multiple Tweakpane plugins end up with duplicate copies of the `@tweakpane/core` code, adding about ~100 Kb to the final minified build for each plugin after the first.

Externalizing this dependency allows build tools like [vite](https://vitejs.dev) to share a single instance of the `@tweakpane/core` code across multiple plugins.

If you're not using a bundler, direct ESM imports from URLs can still work by defining the `@tweakpane/core` dependency in an [importmap](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script/type/importmap).

## Implementation notes

A [PR on the upstream project](https://github.com/donmccurdy/tweakpane-plugin-thumbnail-list/pull/6) with Tweakpane 4.0 support is pending.

Note the package's name change from `tweakpane-plugin-thumbnail-list` to `@kitschpatrol/tweakpane-plugin-thumbnail-list`.

PNPM is used as the package manager.

## Versioning

The [upstream project](https://github.com/donmccurdy/tweakpane-plugin-thumbnail-list) is currently zero-versioned. I've proposed version 1.0.0 in the pull-request with Tweakpane 4.0 support. Since a merge doesn't seem imminent, updates to the fork will follow normal [semver](https://semver.org/) practices instead of remaining in sync with hypothetical future updates to the upstream project. I might revisit this if the upstream repo springs back to life.
npm package: @kitschpatrol/tweakpane-plugin-waveform
Description: A fork of tweakpane-plugin-waveform with build optimizations.
Author: shoelder
Latest version: 1.0.4-beta.3

# @kitschpatrol/tweakpane-plugin-waveform

[![NPM Package @kitschpatrol/tweakpane-plugin-waveform](https://img.shields.io/npm/v/@kitschpatrol/tweakpane-plugin-waveform.svg)](https://npmjs.com/package/@kitschpatrol/tweakpane-plugin-waveform)

## Overview

**This is a fork of [Simon Schödler](https://github.com/shoedler)'s [tweakpane-plugin-waveform](https://github.com/shoedler/tweakpane-plugin-waveform) with externalized dependencies.**

This allows for smaller bundled file sizes in projects using multiple Tweakpane plugins.

It is published to NPM primarily for the [_Svelte Tweakpane UI_](https://kitschpatrol.com/svelte-tweakpane-ui) project, and will be kept in sync with the upstream version of the plugin, with minimal changes other than dependency externalization.

For most use cases, you probably don't want this fork!

## Background

The [Rollup](https://rollupjs.org) configuration provided in the [Tweakpane plugin template](https://github.com/tweakpane/plugin-template) does not externalize [`@tweakpane/core`](https://github.com/cocopon/tweakpane/tree/main/packages/core) as a production dependency.

Instead, it gets built into the single-file plugin artifact, which is what's published to NPM and imported by plugin consumers. This makes it easy to import as an ES module from a URL, but means that larger projects importing multiple Tweakpane plugins end up with duplicate copies of the `@tweakpane/core` code, adding about ~100 Kb to the final minified build for each plugin after the first.

Externalizing this dependency allows build tools like [vite](https://vitejs.dev) to share a single instance of the `@tweakpane/core` code across multiple plugins.

If you're not using a bundler, direct ESM imports from URLs can still work by defining the `@tweakpane/core` dependency in an [importmap](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script/type/importmap).

## Implementation Notes

Note the package's name change from `tweakpane-plugin-waveform` to `@kitschpatrol/tweakpane-plugin-waveform`.

PNPM is used as the package manager.

## Versioning

In addition to the dependency externalization change, this fork also includes assorted dependency updates. In an effort to stay in sync with future upstream versions, intra-minor-version releases of the fork are tagged as "betas" of what would / will be the next patch release upstream.
npm package: @kitsi/cli
Description: Kitsi: local-first CI engine with a TypeScript DSL
Latest version: 0.1.15

# Kitsi

Local-first CI engine with a TypeScript DSL.

## CLI Runner

Kitsi includes a lightweight CLI to run pipeline files that export a `ci` registry.

### Run from source (recommended for .mts pipelines)

```bash
bun ./src/bin/cli.ts list --file .kitsi/pipeline.mts
bun ./src/bin/cli.ts run pr --file .kitsi/pipeline.mts
```

Options:
- `--file`, `-f`: Path to the pipeline file (default: `.kitsi/pipeline.mts`)
- `--workspace`, `-w`: Workspace directory (default: current working directory)
- `--quiet`, `-q`: Suppress command logging

### Run from build output

If your pipeline is compiled to JavaScript, you can run the built CLI:

```bash
bun run build
node ./dist/bin/cli.js list --file ./dist/kitsi.pipeline.js
node ./dist/bin/cli.js run pr --file ./dist/kitsi.pipeline.js
```

### Example pipeline

See `.kitsi/pipeline.mts` for an example that runs lint, unit tests, and build using Kitsi itself.
npm package: @kitspark/fullmodalfx
Description: Lightweight, dependency-free fullscreen modal library with animated transitions.
Author: Kitspark
Latest version: 1.2.0

# fullmodalfx

fullmodalfx is a lightweight, dependency-free fullscreen modal library. It provides animated transitions, scroll locking, and lifecycle hooks using native DOM APIs.

## Features

- Dependency-free, modern TypeScript implementation
- Stack-aware modal handling (open a new modal while closing the previous seamlessly)
- Scroll locking with scrollbar compensation
- Built-in CSS for quick integration
- Lifecycle hooks for open/close events

## Installation

```bash
pnpm add @kitspark/fullmodalfx
```

## Usage

### HTML

```html
<a href="#demo-modal" data-modal-trigger>Open modal</a>

<div id="demo-modal">
  <div class="fmfx-modal__content">
    <button data-modal-close>Close</button>
    <p>Modal content goes here.</p>
  </div>
</div>
```

### JavaScript

```ts
import { initFullModalFX, createFullModalFX } from "@kitspark/fullmodalfx";
import "@kitspark/fullmodalfx/styles.css";

// Auto-bind all triggers with data-modal-trigger
initFullModalFX();

// Or configure a single modal instance
createFullModalFX({
  trigger: "#custom-trigger",
  modal: "#custom-modal",
  beforeOpen: (instance) => {
    console.log("opening", instance);
  }
});
```

### Styling

The library ships with a base stylesheet. Add `fmfx-modal__content` to your modal container and customize it as desired.

## API

### `createFullModalFX(options)`

Creates an instance of `FullModalFX`.

**Options:**

- `modal`: Selector or element for the modal.
- `trigger`: Selector or element to open the modal. If it is an anchor with a hash, the modal is inferred.
- `closeSelector`: Selector for close buttons inside the modal (default: `[data-modal-close]`).
- `closePreviousOnOpen`: Close the previous modal immediately when another opens (default: `true`).
- `animatedInClass`: CSS class for opening animation (default: `fmfx-fade-in`).
- `animatedOutClass`: CSS class for closing animation (default: `fmfx-fade-out`).
- `animationDurationMs`: Duration for animations (default: `200`).
- `beforeOpen`, `afterOpen`, `beforeClose`, `afterClose`: Lifecycle callbacks.

### `initFullModalFX(selector)`

Auto-binds all triggers matching the selector (default: `[data-modal-trigger]`).

### Instance methods

- `open()`
- `close()`
- `destroy()`

## Development

```bash
pnpm install
pnpm test
pnpm build
```

## Releasing

First time only (required to create the package on npm):

```bash
npm login
npm publish --access public
```

After trusted publishing is configured on npm for `@kitspark/fullmodalfx`:

1. Commit and push your changes to `main`.
2. GitHub → Actions → “Release” → Run workflow → choose `patch`/`minor`/`major`.
3. The tag push triggers the publish workflow and uploads the new version to npm.

## License

MIT
npm package: @kitspark/kitget
Description: kitget is a one-shot source slicer for the Kitspark ecosystem.
Author: Kitspark
Latest version: 0.3.2

# kitget

kitget is a one-shot source slicer for the Kitspark ecosystem.

It clones or reads a local copy of `kitspark/core`, copies a strict subset
of directories, and materializes them into a variant repository as owned source.

## What kitget is

- A one-time code injector
- A filesystem slicer
- A development convenience

## What kitget is not

- A dependency manager
- A runtime library
- An updater or sync tool

## Usage

```bash
kitget
npm package: @kitstack/rate-limitter
Description: A flexible, production-ready rate-limiting package for NestJS with multiple algorithms and Redis support.
Author: Ali Raza Khan
Latest version: 1.0.0

# NestJS Rate Limiter

A flexible, production-ready rate-limiting package for NestJS with multiple algorithms and Redis support.

## Packages

- `packages/nestjs-rate-limit` - The main NestJS rate limiting package
- `docs` - React documentation application
- `mock-server` - Mock API server for testing and demonstrating rate limiting

## Getting Started

### Package Development

```bash
cd packages/nestjs-rate-limit
npm install
npm run build
```

### Documentation Development

```bash
cd docs
npm install
npm run dev
```

### Mock Server

```bash
cd mock-server
npm install
npm run dev
```

The mock server runs on `http://localhost:3001` and provides example endpoints demonstrating different rate limiting strategies.

## Features

- 🎯 Multiple rate limiting algorithms (Sliding Window, Leaky Bucket, Token Bucket)
- 🔧 Flexible configuration (Global, Controller, Route level)
- 🚀 Priority system (Route > Controller > Global)
- 💾 Storage options (In-memory, Redis)
- 📝 Fully typed with TypeScript
- 🎨 Simple decorator-based API

## License

MIT