open-index/open-npm huggingface dataset:
npm package: @plumemo/devtools
Description: Po blog 开发工具
Author: Hubert
Latest version: 0.0.9-alpha.58

# Po blog 开发工具
> 包含 `Typescript类型定义` 和 `模块调试工具`    

<br/>

## 安装：
``` bash
yarn add -D @plumemo/devtools
或者
npm i -D @plumemo/devtools
```

## 使用：
``` bash
// 调试模块
po dev [options] <entry>

// 编译模块
po build [options] <entry>
```
## 参数说明：
### \<entry\>  
入口文件或文件夹，详情查看 `vue-cli-service` [entry] 说明
<br>
<br>

### dev [options]
  `--name`  
  类型：string  
  lib 名，（默认值：pakcage.json name 字段 或 entry 文件名）  

  `--filename`  
  类型：string  
  输出文件名，（默认值：--name 的值）  

  `--dest`  
  类型：string
  输出文件路径，（默认值： dist）

  `--plugin`  
  类型：boolean
  调试模块是否是插件，否则以主题模块运行

  `--port`  
  类型：number
  调试服务器端口，（默认：5005）

  `--host`  
  类型：string
  调试服务器IP, (默认：0.0.0.0)




### build [options]
  `--name`  
  类型：string  
  lib 名，（默认值：pakcage.json name 字段 或 entry 文件名）  

  `--filename`  
  类型：string  
  输出文件名，（默认值：--name 的值）  

  `--dest`  
  类型：string
  输出文件路径，（默认值： dist）

  `--info`  
  类型：boolean
  是否显示编译详细信息，（默认值： false）
npm package: @plumeria/core
Description: A styling system that disappears.
Author: Refirst 11
Latest version: 10.2.0

# @plumeria/core
![license](https://img.shields.io/badge/license-MIT-blue)
![npm](https://img.shields.io/npm/v/@plumeria/core)

![web (prod/dev)](https://img.shields.io/badge/web%20(prod/dev)-0B-brightgreen)
![runtime](https://img.shields.io/badge/runtime-0B-brightgreen)
![type safe](https://img.shields.io/badge/types-100%25-brightgreen)

**Plumeria** is a library for developing styled React components for the web. It is a compiler with typed syntax and linting support. The goal of Plumeria is to reduce the load on developers.

## Documentation

Read the [documentation](https://plumeria.dev/) for more details.

## Example
Styles can be passed to the `styleName` prop. That prop accepts static and dynamic styles as an array.

```tsx
import * as css from '@plumeria/core';

const styles = css.create({
  text: {
    fontSize: 12
  },
  cond: {
    background: 'navy'
  },
  scale: (value) => ({
    scale: value
  })
});

export default function App(props) {
  const scale = useScale();
  return (
    <div
      {...props}
      styleName={[
        styles.text, 
        cond && styles.cond,
        styles.scale(scale)
      ]}
    />
  );
}
```

## License

Plumeria is MIT licensed.
npm package: @plumeria/eslint-plugin
Description: Plumeria ESLint plugin
Author: Refirst 11
Latest version: 10.2.0

# @plumeria/eslint-plugin

ESLint plugin for Plumeria.  
Below are the available rules and the recommended configuration.

## Recommended configuration

The `plugin:@plumeria/recommended` config enables the following:

- `@plumeria/style-name-requires-import`: **error**
- `@plumeria/no-combinator`: **error**
- `@plumeria/no-destructure`: **error**
- `@plumeria/no-inner-call`: **error**
- `@plumeria/no-unused-keys`: **warn**
- `@plumeria/sort-properties`: **warn**
- `@plumeria/format-properties`: **warn**
- `@plumeria/validate-values`: **warn**

```js
import { plumeria } from '@plumeria/eslint-plugin';

export default [plumeria.flatConfigs.recommended];
```

## Rules

### style-name-requires-import

Disallow styleName prop in files without a @plumeria/core import.


### no-combinator

Disallow combinators `>`, `+`, `~` and descendant combinator (space) unless inside functional pseudo-classes.

### no-destructure

Disallow destructuring `css.create` and `css.props`, etc.

### no-inner-call

Disallow calling `css.create`, etc. inside functions.

### no-unused-keys

Warns when object keys are defined but not used, mainly in component files.

### sort-properties

Automatically sorts CSS properties in the recommended order for consistency and maintainability.

### format-properties
Automatically format for consistency and maintainability.
- Formats a line into a multi-line.  
- Formats by filling in blank lines.

### validate-values

Validates CSS property values for correctness. Only standard CSS properties are checked; properties with string literal keys (e.g., computed or dynamic property names) are not validated.

## CLI (plumerialint)

This package provides a CLI command, `plumerialint`, as a convenient way
to run Plumeria's custom ESLint rules.

It uses `oxlint` internally for fast linting with code snippets in output.

### Installation

```bash
npm install -D @plumeria/eslint-plugin oxlint
# or
pnpm add -D @plumeria/eslint-plugin oxlint
```

### Usage

```bash
plumerialint
```

The process exits with a non-zero status code if any errors or warnings are found,
making it suitable for use in CI and build pipelines.

Example usage in `package.json`:

```json
{
  "scripts": {
    "lint": "plumerialint"
  }
}
```

**Note:** `oxlint` is required as `plumerialint` uses it internally.
npm package: @plumier/core
Description: Delightful Node.js Rest Framework
Author: Ketut Sandiarsa
Latest version: 1.1.3

# Plumier
Delightful Node.js Rest Framework

[![Build Status](https://github.com/plumier/plumier/workflows/ubuntu/badge.svg)](https://github.com/plumier/plumier/actions?query=workflow%3Aubuntu)
[![Build status](https://github.com/plumier/plumier/workflows/windows/badge.svg)](https://github.com/plumier/plumier/actions?query=workflow%3Awindows)
[![Coverage Status](https://coveralls.io/repos/github/plumier/plumier/badge.svg?branch=master)](https://coveralls.io/github/plumier/plumier?branch=master)
[![lerna](https://img.shields.io/badge/maintained%20with-lerna-cc00ff.svg)](https://lernajs.io/)
[![npm](https://img.shields.io/npm/v/plumier/canary)](https://www.npmjs.com/package/plumier?activeTab=versions)
[![npm](https://img.shields.io/npm/v/plumier/latest)](https://www.npmjs.com/package/plumier?activeTab=versions)

## Documentation 
Read the project documentation on https://plumierjs.com

## Contributing
To run Plumier project on local machine, some setup/app required

### App requirements
* Visual Studio Code (Recommended)
* Yarn (required)

### Local Setup
* Fork and clone the project `git clone` 
* Install dependencies by `yarn install`
* Run test by `yarn test`

### Debugging
Plumier already provided vscode `task` and `launch` setting. To start debugging a test scenario:
* Locate the test file and narrow the test runs by using `.only`
* Put breakpoint on any location you need on `.ts` file 
* On start/debug configuration select `Jest Current File` and start debugging
npm package: @plumier/generic-controller
Description: Plumier generic controller implementation
Author: Ketut Sandiarsa
Latest version: 1.1.3

# Plumier
Delightful Node.js Rest Framework

[![Build Status](https://github.com/plumier/plumier/workflows/ubuntu/badge.svg)](https://github.com/plumier/plumier/actions?query=workflow%3Aubuntu)
[![Build status](https://github.com/plumier/plumier/workflows/windows/badge.svg)](https://github.com/plumier/plumier/actions?query=workflow%3Awindows)
[![Coverage Status](https://coveralls.io/repos/github/plumier/plumier/badge.svg?branch=master)](https://coveralls.io/github/plumier/plumier?branch=master)
[![lerna](https://img.shields.io/badge/maintained%20with-lerna-cc00ff.svg)](https://lernajs.io/)
[![npm](https://img.shields.io/npm/v/plumier/canary)](https://www.npmjs.com/package/plumier?activeTab=versions)
[![npm](https://img.shields.io/npm/v/plumier/latest)](https://www.npmjs.com/package/plumier?activeTab=versions)

## Documentation 
Read the project documentation on https://plumierjs.com

## Contributing
To run Plumier project on local machine, some setup/app required

### App requirements
* Visual Studio Code (Recommended)
* Yarn (required)

### Local Setup
* Fork and clone the project `git clone` 
* Install dependencies by `yarn install`
* Run test by `yarn test`

### Debugging
Plumier already provided vscode `task` and `launch` setting. To start debugging a test scenario:
* Locate the test file and narrow the test runs by using `.only`
* Put breakpoint on any location you need on `.ts` file 
* On start/debug configuration select `Jest Current File` and start debugging
npm package: @plumier/jwt
Description: Plumier authorization module using JWT
Author: Ketut Sandiarsa
Latest version: 1.1.3

# Plumier
Delightful Node.js Rest Framework

[![Build Status](https://github.com/plumier/plumier/workflows/ubuntu/badge.svg)](https://github.com/plumier/plumier/actions?query=workflow%3Aubuntu)
[![Build status](https://github.com/plumier/plumier/workflows/windows/badge.svg)](https://github.com/plumier/plumier/actions?query=workflow%3Awindows)
[![Coverage Status](https://coveralls.io/repos/github/plumier/plumier/badge.svg?branch=master)](https://coveralls.io/github/plumier/plumier?branch=master)
[![lerna](https://img.shields.io/badge/maintained%20with-lerna-cc00ff.svg)](https://lernajs.io/)
[![npm](https://img.shields.io/npm/v/plumier/canary)](https://www.npmjs.com/package/plumier?activeTab=versions)
[![npm](https://img.shields.io/npm/v/plumier/latest)](https://www.npmjs.com/package/plumier?activeTab=versions)

## Documentation 
Read the project documentation on https://plumierjs.com

## Contributing
To run Plumier project on local machine, some setup/app required

### App requirements
* Visual Studio Code (Recommended)
* Yarn (required)

### Local Setup
* Fork and clone the project `git clone` 
* Install dependencies by `yarn install`
* Run test by `yarn test`

### Debugging
Plumier already provided vscode `task` and `launch` setting. To start debugging a test scenario:
* Locate the test file and narrow the test runs by using `.only`
* Put breakpoint on any location you need on `.ts` file 
* On start/debug configuration select `Jest Current File` and start debugging
npm package: @plumier/mongoose
Description: Mongoose with decorator based configuration
Author: Ketut Sandiarsa
Latest version: 1.1.3

# Plumier
Delightful Node.js Rest Framework

[![Build Status](https://github.com/plumier/plumier/workflows/ubuntu/badge.svg)](https://github.com/plumier/plumier/actions?query=workflow%3Aubuntu)
[![Build status](https://github.com/plumier/plumier/workflows/windows/badge.svg)](https://github.com/plumier/plumier/actions?query=workflow%3Awindows)
[![Coverage Status](https://coveralls.io/repos/github/plumier/plumier/badge.svg?branch=master)](https://coveralls.io/github/plumier/plumier?branch=master)
[![lerna](https://img.shields.io/badge/maintained%20with-lerna-cc00ff.svg)](https://lernajs.io/)
[![npm](https://img.shields.io/npm/v/plumier/canary)](https://www.npmjs.com/package/plumier?activeTab=versions)
[![npm](https://img.shields.io/npm/v/plumier/latest)](https://www.npmjs.com/package/plumier?activeTab=versions)

## Documentation 
Read the project documentation on https://plumierjs.com

## Contributing
To run Plumier project on local machine, some setup/app required

### App requirements
* Visual Studio Code (Recommended)
* Yarn (required)

### Local Setup
* Fork and clone the project `git clone` 
* Install dependencies by `yarn install`
* Run test by `yarn test`

### Debugging
Plumier already provided vscode `task` and `launch` setting. To start debugging a test scenario:
* Locate the test file and narrow the test runs by using `.only`
* Put breakpoint on any location you need on `.ts` file 
* On start/debug configuration select `Jest Current File` and start debugging
npm package: @plumier/query-parser
Description: Plumier testing modules
Author: Ketut Sandiarsa
Latest version: 1.1.3

# Plumier
Delightful Node.js Rest Framework

[![Build Status](https://github.com/plumier/plumier/workflows/ubuntu/badge.svg)](https://github.com/plumier/plumier/actions?query=workflow%3Aubuntu)
[![Build status](https://github.com/plumier/plumier/workflows/windows/badge.svg)](https://github.com/plumier/plumier/actions?query=workflow%3Awindows)
[![Coverage Status](https://coveralls.io/repos/github/plumier/plumier/badge.svg?branch=master)](https://coveralls.io/github/plumier/plumier?branch=master)
[![lerna](https://img.shields.io/badge/maintained%20with-lerna-cc00ff.svg)](https://lernajs.io/)
[![npm](https://img.shields.io/npm/v/plumier/canary)](https://www.npmjs.com/package/plumier?activeTab=versions)
[![npm](https://img.shields.io/npm/v/plumier/latest)](https://www.npmjs.com/package/plumier?activeTab=versions)

## Documentation 
Read the project documentation on https://plumierjs.com

## Contributing
To run Plumier project on local machine, some setup/app required

### App requirements
* Visual Studio Code (Recommended)
* Yarn (required)

### Local Setup
* Fork and clone the project `git clone` 
* Install dependencies by `yarn install`
* Run test by `yarn test`

### Debugging
Plumier already provided vscode `task` and `launch` setting. To start debugging a test scenario:
* Locate the test file and narrow the test runs by using `.only`
* Put breakpoint on any location you need on `.ts` file 
* On start/debug configuration select `Jest Current File` and start debugging
npm package: @plumier/swagger
Description: Swagger and Open API 3 module for Plumier
Author: Ketut Sandiarsa
Latest version: 1.1.3

# Plumier
Delightful Node.js Rest Framework

[![Build Status](https://github.com/plumier/plumier/workflows/ubuntu/badge.svg)](https://github.com/plumier/plumier/actions?query=workflow%3Aubuntu)
[![Build status](https://github.com/plumier/plumier/workflows/windows/badge.svg)](https://github.com/plumier/plumier/actions?query=workflow%3Awindows)
[![Coverage Status](https://coveralls.io/repos/github/plumier/plumier/badge.svg?branch=master)](https://coveralls.io/github/plumier/plumier?branch=master)
[![lerna](https://img.shields.io/badge/maintained%20with-lerna-cc00ff.svg)](https://lernajs.io/)
[![npm](https://img.shields.io/npm/v/plumier/canary)](https://www.npmjs.com/package/plumier?activeTab=versions)
[![npm](https://img.shields.io/npm/v/plumier/latest)](https://www.npmjs.com/package/plumier?activeTab=versions)

## Documentation 
Read the project documentation on https://plumierjs.com

## Contributing
To run Plumier project on local machine, some setup/app required

### App requirements
* Visual Studio Code (Recommended)
* Yarn (required)

### Local Setup
* Fork and clone the project `git clone` 
* Install dependencies by `yarn install`
* Run test by `yarn test`

### Debugging
Plumier already provided vscode `task` and `launch` setting. To start debugging a test scenario:
* Locate the test file and narrow the test runs by using `.only`
* Put breakpoint on any location you need on `.ts` file 
* On start/debug configuration select `Jest Current File` and start debugging
npm package: @plumier/typeorm
Description: TypeOrm helper for Plumier
Author: Ketut Sandiarsa
Latest version: 1.1.3

# Plumier
Delightful Node.js Rest Framework

[![Build Status](https://github.com/plumier/plumier/workflows/ubuntu/badge.svg)](https://github.com/plumier/plumier/actions?query=workflow%3Aubuntu)
[![Build status](https://github.com/plumier/plumier/workflows/windows/badge.svg)](https://github.com/plumier/plumier/actions?query=workflow%3Awindows)
[![Coverage Status](https://coveralls.io/repos/github/plumier/plumier/badge.svg?branch=master)](https://coveralls.io/github/plumier/plumier?branch=master)
[![lerna](https://img.shields.io/badge/maintained%20with-lerna-cc00ff.svg)](https://lernajs.io/)
[![npm](https://img.shields.io/npm/v/plumier/canary)](https://www.npmjs.com/package/plumier?activeTab=versions)
[![npm](https://img.shields.io/npm/v/plumier/latest)](https://www.npmjs.com/package/plumier?activeTab=versions)

## Documentation 
Read the project documentation on https://plumierjs.com

## Contributing
To run Plumier project on local machine, some setup/app required

### App requirements
* Visual Studio Code (Recommended)
* Yarn (required)

### Local Setup
* Fork and clone the project `git clone` 
* Install dependencies by `yarn install`
* Run test by `yarn test`

### Debugging
Plumier already provided vscode `task` and `launch` setting. To start debugging a test scenario:
* Locate the test file and narrow the test runs by using `.only`
* Put breakpoint on any location you need on `.ts` file 
* On start/debug configuration select `Jest Current File` and start debugging
npm package: @plumile/eslint-config-typescript
Description: Shared ESLint flat config tuned for TypeScript-forward React projects
Author: Olivier Hardy
Latest version: 0.1.87

# @plumile/eslint-config-typescript

Shared ESLint flat config for TypeScript-forward React projects.

## Status

Recommended for external use. This is one of the clearest standalone packages in
the repository and is designed to work outside the Plumile monorepo.

## Purpose

The package provides:

- a reusable flat ESLint config array
- a `createConfig` helper for custom `tsconfig` locations
- a Relay-specific preset in `relay.js`

It is intended for projects that want Plumile's TypeScript, React, accessibility
and code-quality defaults without copying rule definitions manually.

## Installation

```bash
npm install --save-dev eslint @plumile/eslint-config-typescript
```

Typical peer dependencies:

```bash
npm install --save-dev \
  @stylistic/eslint-plugin \
  @typescript-eslint/eslint-plugin \
  eslint-plugin-jsdoc \
  eslint-plugin-jsx-a11y \
  eslint-plugin-n \
  eslint-plugin-react \
  eslint-plugin-react-hooks \
  eslint-plugin-sonarjs
```

If you use the Relay preset, also install:

```bash
npm install --save-dev eslint-plugin-relay
```

## Main Public Surface

### Default export

The package default export is an array of ESLint flat config fragments that you
spread into `eslint.config.js`.

### `createConfig`

Use `createConfig({ project })` when your ESLint TypeScript project file is not
at `./tsconfig.eslint.json`.

### Relay preset

Import `@plumile/eslint-config-typescript/relay.js` to add Relay-specific
syntax, naming, and colocated fragment checks.

## Quick Start

### Flat config

```ts
import plumileTs from '@plumile/eslint-config-typescript';

export default [
  ...plumileTs,
  {
    files: ['src/**/*.ts', 'src/**/*.tsx'],
    rules: {
      '@typescript-eslint/no-explicit-any': 'off',
    },
  },
];
```

### Custom TypeScript project

```ts
import { createConfig } from '@plumile/eslint-config-typescript';

export default [...createConfig({ project: './tsconfig.eslint.json' })];
```

### Relay preset

```ts
import plumileTs from '@plumile/eslint-config-typescript';
import relayPreset from '@plumile/eslint-config-typescript/relay.js';

export default [...plumileTs, ...relayPreset];
```

## What the Preset Covers

- TypeScript parsing and project-aware linting
- React hooks rules
- accessibility checks
- jsdoc and general code-quality rules
- stylistic rules aligned with the repository expectations

## Validation Notes

- public config shape should be covered by tests that load the default config and
  the Relay preset
- README examples should stay aligned with the exported entry points

## Limitations

- this package assumes ESLint flat config as the primary integration model
- legacy `.eslintrc` consumers may still adapt it, but flat config is the
  documented path
- consumers remain responsible for installing the required peer dependencies

## Related Docs

- [Repository Guidelines](../../AGENTS.md)
- [Documentation Index](../../docs/index.md)
npm package: @plumile/ui-devtools
Description: Shared DevTools UI primitives for Plumile extensions
Author: Plumile Maintainers
Latest version: 0.1.87

# @plumile/ui-devtools

Shared DevTools UI primitives for Plumile extensions and debugging panels.

## Status

Specialized public package. This package is intended for internal tooling or
specialized DevTools interfaces, not as a general-purpose component library.

## Purpose

`@plumile/ui-devtools` provides a small set of visual primitives used by
Plumile developer tooling, including:

- badges and pills
- status lights
- cards and sections
- tabs and toolbar components
- split-view layouts
- code blocks and empty states
- a dedicated DevTools theme wrapper

## Installation

```bash
npm install @plumile/ui-devtools
```

Peer dependencies:

```bash
npm install react react-dom
```

## Main Public Surface

- `DevtoolsTheme`
- `DevtoolsBadge`
- `DevtoolsPill`
- `DevtoolsStatusLight`
- `DevtoolsCard`
- `DevtoolsSection`
- `DevtoolsCodeBlock`
- `DevtoolsEmptyState`
- `DevtoolsTabs`
- `DevtoolsToolbar`
- `DevtoolsToolbarButton`
- `DevtoolsToolbarSeparator`
- `DevtoolsSplitView`

For the complete entry point, see [`src/index.ts`](./src/index.ts).

## Quick Start

```tsx
import {
  DevtoolsCard,
  DevtoolsSection,
  DevtoolsTabs,
  DevtoolsTheme,
} from '@plumile/ui-devtools';

const items = [
  { id: 'timeline', label: 'Timeline' },
  { id: 'state', label: 'State' },
] as const;

export function Panel(): JSX.Element {
  return (
    <DevtoolsTheme>
      <DevtoolsTabs
        items={items}
        selectedId="timeline"
        onSelect={() => {}}
        ariaLabel="Panel sections"
      />
      <DevtoolsCard title="Router">
        <DevtoolsSection title="Live state">Ready</DevtoolsSection>
      </DevtoolsCard>
    </DevtoolsTheme>
  );
}
```

## Validation Notes

- the package should keep targeted tests around stable interactive primitives
  such as tabs or toolbar interactions
- visual breadth is intentionally small, so concise README guidance is preferred
  over deeper docs

## Limitations

- the look and feel is intentionally tied to Plumile DevTools
- this package does not aim to be a generic dashboard or admin UI toolkit

## Related Docs

- [Router DevTools Extension README](../router-devtools-extension/README.md)
- [Documentation Index](../../docs/index.md)
npm package: @plumjs/plumier
Description: Delightful NodeJS Web Api Framework powered by KoaJs and TypeScript
Author: Ketut Sandiarsa
Latest version: 1.0.0-alpha.6

# Plumier
Delightful NodeJS Web Api Framework powered by KoaJs and TypeScript

[![Build Status](https://travis-ci.org/ktutnik/plumier.svg?branch=master)](https://travis-ci.org/ktutnik/plumier)
[![Coverage Status](https://coveralls.io/repos/github/ktutnik/plumier/badge.svg?branch=master)](https://coveralls.io/github/ktutnik/plumier?branch=master) 
[![Greenkeeper badge](https://badges.greenkeeper.io/ktutnik/plumier.svg)](https://greenkeeper.io/)
[![Codacy Badge](https://api.codacy.com/project/badge/Grade/6d61987244f1471abe915292cb3add1b)](https://www.codacy.com/app/ktutnik/plumier?utm_source=github.com&amp;utm_medium=referral&amp;utm_content=ktutnik/plumier&amp;utm_campaign=Badge_Grade)
npm package: @plumpboy/bootstrap-confirmation
Description: Bootstrap plugin for on-place confirm boxes using Popover
Author: plumpboy
Latest version: 1.0.0

# Bootstrap-Confirmation

[![npm version](https://img.shields.io/npm/v/bootstrap-confirmation2.svg?style=flat-square)](https://www.npmjs.com/package/bootstrap-confirmation2)
[![jsDelivr CDN](https://data.jsdelivr.com/v1/package/npm/bootstrap-confirmation2/badge)](https://www.jsdelivr.com/package/npm/bootstrap-confirmation2)
[![GZIP size](https://img.shields.io/bundlephobia/minzip/bootstrap-confirmation2?label=gzip%20size)](https://bundlephobia.com/result?p=bootstrap-confirmation2)
[![Build Status](https://github.com/mistic100/Bootstrap-Confirmation/workflows/CI/badge.svg)](https://github.com/mistic100/Bootstrap-Confirmation/actions)

Bootstrap plugin for on-place confirm boxes using Popover.

## Documentation

[bootstrap-confirmation.js.org](http://bootstrap-confirmation.js.org)

## Installation

#### Bootstrap 4

```
npm install bootstrap-confirmation2
```

#### Bootstrap 3

```
npm install bootstrap-confirmation2@2.x.x
```
npm package: @plumpnation/nunjucks-html-loader
Description: A webpack loader that takes nunjucks templates and returns raw html. It also works with webpack's watch command
Author: Ryan Hornberger
Latest version: 1.2.0

Nunjucks (Webpack) HTML Loader
==============================
The original 'nunjucks-loader' takes nunjucks templates and turns them into javascript. I wanted to take nunjucks templates and turn them into pre-compiled static html files.

[![NPM version][npm-image]][npm-url]
[![Github license][github-license-image]][github-url]
[![Github stars][github-image]][github-url]

Usage
-----

This is a very simple webpack loader for nunjucks files. It performs the following opteration:

    some-template.nunj -> html string

When you mix it with the file-loader you can take it one step further!

    some-template.nunj -> html string -> some-file.html

Add your personal variation to the below loader configuration to your webpack config and you should be good to go.

	{
        test: /\.nunj$/,
        loader: 'file?context=' + precompiledContext + '&name=[path][name].html!nunjucks-html?' +
        	JSON.stringify({
        		'searchPaths': [
					'/path/to/sources',
					'/path/to/more/sources'
				]
        	})
    }


[npm-url]: https://www.npmjs.com/package/nunjucks-html-loader
[npm-image]: https://img.shields.io/npm/v/nunjucks-html-loader.svg
[github-url]: https://github.com/ryanhornberger/nunjucks-html-loader
[github-image]: https://img.shields.io/github/stars/ryanhornberger/nunjucks-html-loader.svg?style=social&label=Star
[github-license-image]: https://img.shields.io/github/license/ryanhornberger/nunjucks-html-loader.svg
npm package: @plundell/npm-ts-boilerplate
Description: A CLI tool to generate a TypeScript npm module boilerplate
Author: plundell
Latest version: 1.0.4

# npm-ts-boilerplate

A simple CLI tool to generate a TypeScript npm module boilerplate.

## Installation

To install the tool globally, run:

```bash
npm install -g @plundell/npm-ts-boilerplate
```

## Usage
After installing it globally you can call it directly from the command line:
```bash
npm-ts-boilerplate -p /path/to/new/module -g my-github-user -n new-module-name
```
This command will create a new directory at /path/to/new/module/new-module-name with the boilerplate files, modify the configuration files with the new module name, install npm dependencies, initialize a Git repository, configure the remote repository, and create the first commit with the message "boilerplate created".


## License
MIT
npm package: @plung/sdk
Description: Official TypeScript SDK for the Plung API
Author: Plung
Latest version: 0.2.0

# Plung TypeScript SDK

Official TypeScript SDK for the Plung API.

## Installation

```bash
pnpm add @plung/sdk
```

## Quick start

```ts
import { PlungClient } from '@plung/sdk';

const client = new PlungClient(process.env.PLUNG_API_KEY!);

const { data, meta } = await client.links.create({
  url: 'https://example.com',
});

console.log(data.shortUrl);
console.log(meta.rateLimit.remaining);
```

Example response shape:

```ts
{
  data: {
    shortUrl: 'https://plu.ng/hello-world',
    shortCode: 'hello-world',
    url: 'https://example.com',
    createdAt: '2026-03-27T00:00:00.000Z'
  },
  meta: {
    apiKeyName: 'primary',
    rateLimit: {
      limit: 100,
      remaining: 99,
      reset: 1710000000
    },
    plan: 'PRO',
    usage: {
      apiCallsUsed: 1,
      apiCallsLimit: 1000,
      apiCallsRemaining: 999,
      reset: 1775001600
    }
  }
}
```

## Available methods

| Resource | Method | Signature |
| --- | --- | --- |
| Links | `links.create` | `(input: CreateLinkInput) => Promise<PlungResponse<Link>>` |
| Links | `links.batchCreate` | `(items: CreateLinkInput[]) => Promise<PlungResponse<BatchCreateResponse>>` |
| QR | `qr.get` | `(shortCode: string, options?: QrOptions) => Promise<QrResponse>` |
| Analytics | `analytics.get` | `(shortCode: string) => Promise<PlungResponse<LinkStats>>` |

## Error handling

```ts
import {
  PlungAuthError,
  PlungRateLimitError,
  PlungValidationError,
  PlungClient,
} from '@plung/sdk';

const client = new PlungClient(process.env.PLUNG_API_KEY!);

try {
  await client.links.create({ url: 'not-a-valid-url' });
} catch (error) {
  if (error instanceof PlungValidationError) {
    console.log('Validation failed:', error.message);
  } else if (error instanceof PlungAuthError) {
    console.log('Authentication failed:', error.message);
  } else if (error instanceof PlungRateLimitError) {
    console.log('Rate limited:', error.retryAfter);
  }
}
```

## Response metadata

Every successful SDK response includes a `meta` object.

- `meta.apiKeyName`: API key label returned by the backend, when available.
- `meta.rateLimit.limit`: Current rate-limit ceiling for the authenticated key.
- `meta.rateLimit.remaining`: Remaining requests in the current rate-limit window.
- `meta.rateLimit.reset`: Unix timestamp in seconds for the rate-limit reset time.
- `meta.plan`: Current Plung plan identifier returned by the backend.
- `meta.usage.apiCallsUsed`: API calls already used in the current billing period.
- `meta.usage.apiCallsLimit`: API call limit for the current billing period, when finite.
- `meta.usage.apiCallsRemaining`: Remaining API calls for the current billing period, when finite.
- `meta.usage.reset`: Unix timestamp in seconds for the next usage reset time.

## Requirements

- Node `>=24.14.1`
npm package: @plungerswap/sdk
Description: 🛠 An SDK for building applications on top of PlungerSwap.
Latest version: 0.0.3

# Uniswap SDK

[![code style: prettier](https://img.shields.io/badge/code_style-prettier-ff69b4.svg?style=flat-square)](https://github.com/prettier/prettier)
[![Actions Status](https://github.com/VenomProtocol/venomswap-sdk/workflows/CI/badge.svg)](https://github.com/VenomProtocol/venomswap-sdk)
[![npm version](https://img.shields.io/npm/v/@venomswap/sdk/latest.svg)](https://www.npmjs.com/package/@venomswap/sdk/v/latest)
[![npm bundle size (scoped version)](https://img.shields.io/bundlephobia/minzip/@venomswap/sdk/latest.svg)](https://bundlephobia.com/result?p=@venomswap/sdk@latest)

In-depth documentation on this SDK is available at [uniswap.org](https://uniswap.org/docs/v2/SDK/getting-started/).

## Running tests

To run the tests, follow these steps. You must have at least node v10 and [yarn](https://yarnpkg.com/) installed.

First clone the repository:

```sh
git clone https://github.com/VenomProtocol/venomswap-sdk.git
```

Move into the uniswap-sdk working directory

```sh
cd uniswap-sdk/
```

Install dependencies

```sh
yarn install
```

Run tests

```sh
yarn test
```

You should see output like the following:

```sh
yarn run v1.22.4
$ tsdx test
 PASS  test/constants.test.ts
 PASS  test/pair.test.ts
 PASS  test/fraction.test.ts
 PASS  test/miscellaneous.test.ts
 PASS  test/entities.test.ts
 PASS  test/trade.test.ts

Test Suites: 1 skipped, 6 passed, 6 of 7 total
Tests:       3 skipped, 82 passed, 85 total
Snapshots:   0 total
Time:        5.091s
Ran all test suites.
✨  Done in 6.61s.
```
npm package: @plungerswap/sdk-extra
Description: 🛠 A specific SDK/toolkit for building applications on top of PlungerSwap.
Latest version: 0.0.3

# Venomswap SDK Extra

[![code style: prettier](https://img.shields.io/badge/code_style-prettier-ff69b4.svg?style=flat-square)](https://github.com/prettier/prettier)
[![Actions Status](https://github.com/VenomProtocol/venomswap-sdk-extra/workflows/CI/badge.svg)](https://github.com/VenomProtocol/venomswap-sdk-extra)
[![npm version](https://img.shields.io/npm/v/@venomswap/sdk-extra/latest.svg)](https://www.npmjs.com/package/@venomswap/sdk-extra/v/latest)
[![npm bundle size (scoped version)](https://img.shields.io/bundlephobia/minzip/@venomswap/sdk-extra/latest.svg)](https://bundlephobia.com/result?p=@venomswap/sdk-extra@latest)

## Running tests

To run the tests, follow these steps. You must have at least node v10 and [yarn](https://yarnpkg.com/) installed.

First clone the repository:

```sh
git clone https://github.com/VenomProtocol/venomswap-sdk-extra.git
```

Move into the venomswap-sdk-extra working directory

```sh
cd venomswap-sdk-extra/
```

Install dependencies

```sh
yarn install
```

Run tests

```sh
yarn test
```
npm package: @plunk/node
Description: Official Node.js library for useplunk.com
Author: driaug
Latest version: 3.0.3

# Plunk Node.js
This project contains the helper library for interacting with the Plunk API using Node.js.

## Table of contents
- [Installation](#installation)
- [Getting started](#getting-started)
- [API](#api)
    - [Events](#events)
    - [Email](#emails)

![Card](https://www.useplunk.com/assets/card.png)

## Installation
Installing the latest version can be done through your package manager.

```shell
npm i @plunk/node

yarn add @plunk/node
```

## Getting started
Any interaction you want to make with the Plunk API needs to be done through the Plunk client. You can use a default import to get started.

```js
import Plunk from '@plunk/node';

// Using the default API URL
const plunk = new Plunk("Your secret key");

// Or specifying a custom API URL
const plunkCustom = new Plunk("Your secret key", { baseUrl: "https://selfhosted.example.com/api/v1/" });
```

## API
### Events
#### track()
Used to publish an event

##### Parameters
- `event`: The name of the event to publish
- `email`: The email address of the user to publish the event to
- `subscribed` [Optional]: Whether to the contact is subscribed to marketing emails, defaults to `true`
- `data` [Optional]: An object containing the data to attach to the user

```ts
const success = await plunk.events.track({
  event: "new-project",
  email: "hello@useplunk.com",
  data: {
    company: "Plunk"
  }
});
```

### Emails
#### send()
Used to send a transactional email
##### Parameters
- `to`: The email address of the recipient
- `subject`: The subject of the email
- `body`: The body of the email
- `type` [Optional]: The type of email to send (`html` or `markdown`)
- `from` [Optional]: The email address of the sender
- `name` [Optional]: The name of the sender
- `subscribed` [Optional]: Whether to the contact is subscribed to marketing emails, defaults to `false`

```ts
const success = await plunk.emails.send({
  to: "hello@useplunk.com",
  subject: "Welcome to Plunk",
  body: "Hello world!",
});
```