open-index/open-npm huggingface dataset:
npm package: @talkweb/dmax
Description: talkweb dmax
Author: yanpengxiang@talkweb.com.cn
Latest version: 0.8.1

# DMAX

## TODO
- 间距分布调整 在widget大小不一致时 可以设置的最小值有问题 两个元素重叠时也有问题
- 直接点击需要拖拽添加的widget有问题
npm package: @talkweb/editor-bpmn
Description: BPMN editor based on G6
Author: yanpengxiang
Latest version: 1.0.0-alpha.6

# EDITOR - BPMN

新的流程设计器是基于阿里Antv开源的G6前端图可视化库开发的，这个可视化库使用的是canvas，而不是以前老版本bpm基于svg的实现，新的流程设计器会使用vue进行封装成独立的组件，和老版本的编辑器相比，会提供更好的兼容性和扩展性，在提供基础的图形编辑功能上会添加很多辅助功能如自动对齐、辅助线、快捷键等方便图形绘制。

## Install

npm
```
npm i @talkweb/editor-bpmn -S
```

yarn
```
yarn add @talkweb/editor-bpmn
```

CDN
```
<!-- 引入样式 -->
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@talkweb/editor-bpmn/lib/index.css"/>
<!-- 引入组件 -->
<script src="https://cdn.jsdelivr.net/npm/@talkweb/editor-bpmn/lib/index.js"></script>
```

## Usage
```
import Vue from 'vue';
import Editor from '@talkweb/editor-bpmn';
import '@talkweb/editor-bpmn/lib/index.css';
import App from './App.vue';

Vue.use(Editor);

new Vue({
  el: '#app',
  render: h => h(App)
});
```

```
<template>
  <editor-bpmn />
</template>
```

## Features

### Shapes
- 👌Task
- 👌Gateway
- 👌Middle event
- 👌End event
- 👌Start event
- 👌Sub process
- 👌Rect
- 👌Circle
- 👌Diamond
- 👌Ellipse
- 👌Sub process
- 👌Cylinder
- 👌Internal storage
- 👌Parallelogram
- 👌Document

### Core functions
- 👌Drag shapes
- 👌Connection shapes
- 👌Shape attribute editing

### Auxiliary functions
- 👌Resize
- 👌Copy
- 👌Cut
- 👌Paste
- 👌To front
- 👌To back
- 👌Clear
- 👌Print
- 👌zoom in
- 👌zoom out
- 👌Mini map
- 👌Quick graphics adding
- 👌Align edge
- 👌Dblclick to edit shape and edge
- 👌Edge editing
- 👌Multiple select

### Animation
- 👌Edge out animation

## Todo
- ❗️add shape icon
- ❗️drag edge label
- ❗️label align
- ❗️add group
- ❗️add pool
- ❗️modify canvas size
npm package: @talkwed-mito/browser
Description: A SDK For Monitoring Browser Errors
Author: cjinhuo
Latest version: 3.1.5

# @talkwed-mito/browser


## Install

```bash
# using npm
npm i @talkwed-mito/browser
# using yarn
yarn add @talkwed-mito/browser
```

### usage

```typescript
// some.js
import { init } from '@talkwed-mito/browser'

// multiple instances
const MitoInstance = init({
  // set debug true to convenient debugger in dev,set false in prod
  debug:true,
  dsn: 'https://test.com/yourInterface',
  maxBreadcrumbs: 100
})
```

more info of [@talkwed-mito/browser](https://mitojs.github.io/mito-doc/#/sdk/guide/browser)
npm package: @talkwed-mito/core
Description: @talkwed-mito/core
Author: cjinhuo
Latest version: 3.1.6

# @talkwed-mito/core
provider some core class、base abstract class and base options for [@talkwed-mito](https://github.com/mitojs/mitojs)

read the [mito-doc](https://mitojs.github.io/mito-doc/#/sdk/guide/introduction) to konw more info
npm package: @talkwed-mito/shared
Description: @talkwed-mito/shared
Author: cjinhuo
Latest version: 3.1.6

# @talkwed-mito/shared

provider some common configuration,such as constants、enum for [@talkwed-mito](https://github.com/mitojs/mitojs)


read the [mito-doc](https://mitojs.github.io/mito-doc/#/sdk/guide/introduction) to konw more info
npm package: @talkwed-mito/types
Description: @talkwed-mito/types
Author: cjinhuo
Latest version: 3.1.6

# @talkwed-mito/types

provider some common types for [@talkwed-mito](https://github.com/mitojs/mitojs)


read the [mito-doc](https://mitojs.github.io/mito-doc/#/sdk/guide/introduction) to konw more info
npm package: @talkyjs/schematics
Description: A blank schematics
Author: Hidetaka Okamoto
Latest version: 2.1.0

# Getting Started With Schematics

This repository is a basic Schematic implementation that serves as a starting point to create and publish Schematics to NPM.

### Testing

To test locally, install `@angular-devkit/schematics-cli` globally and use the `schematics` command line tool. That tool acts the same as the `generate` command of the Angular CLI, but also has a debug mode.

Check the documentation with
```bash
schematics --help
```

### Unit Testing

`npm run test` will run the unit tests, using Jasmine as a runner and test framework.

### Commands


```bash
# Setup Skill handler
% yarn schematics .:init --path=./tmp --dry-run=false --ssml=tsx --database=none

# Add a ask-sdk request handler
% yarn schematics .:handler --path=./tmp --dry-run=false --ssml=tsx

# Add ask-utils router (Dry run)
% yarn schematics .:router --path=./tmp/src

# Add service class
% yarn schematics .:service --path=./tmp/src --name=test --dry-run=false --test=true
```

### Publishing

To publish, simply do:

```bash
npm run build
npm publish
```

That's it!

 ## TODO
 - [ ] Test Code
 - [ ] Auto import generated files
 - [ ] decorator support
 - [ ] Serverless Framework yaml generation
 - [ ] Update ASK CLI build hook (v1)
 - [ ] Update ASK CLI build hook (v2)
 - [ ] Create IAM policy example
 - [ ] Update CloudFormation template for ASK CLI (v2 cfn-deployer)
npm package: @talla-ui/util
Description: Tälla UI framework: utility library
Author: Jelmer Cormont
Latest version: 4.0.2

# Tälla UI framework: Utility library

This NPM package is part of the Tälla project. For more information, refer to the repository on GitHub.

## License

This code is free and open source. Copyright and [MIT](https://opensource.org/licenses/MIT) license terms still apply.

Copyright &copy; 2026 Jelmer Cormont
npm package: @tallang/shared-design-demo
Description: A demo repository to illustrate how to share palette and typography through NPM
Latest version: 1.1.2

# Shared design demo
[![npm version](https://badge.fury.io/js/%40tallang%2Fshared-design-demo.svg)](https://badge.fury.io/js/%40tallang%2Fshared-design-demo)

This package works as a demo to illustrate how to share typography and colors through SASS mixins:

# Colors
The colors and their SASS-names are provided below.
## Colors
- ![#2196F3](https://placehold.it/15/2196F3/000000?text=+) #2196F3: `$calm-blue`
- ![#009688](https://placehold.it/15/009688/000000?text=+) #009688: `$teal`
- ![#FFC107](https://placehold.it/15/FFC107/000000?text=+) #FFC107: `$amber`
- ![#D32F2F](https://placehold.it/15/D32F2F/000000?text=+) #D32F2F: `$red`

## Greys
- ![#282828](https://placehold.it/15/282828/000000?text=+) #282828: `$dark-grey`
- ![#dedede](https://placehold.it/15/dedede/000000?text=+) #dedede: `$light-grey`

 All of the provided colors are available in three shades. They can be used by postfixing the SASS-name with `-75` or `-50`. This will give the color an opacity of 75% or 50%, depending on your choice. An example is given below:
 ```
 background: $calm-blue;
 color: $calm-blue-75;
 border-color: $calm-blue-50;
 ```

# Material Design Colors
If you're using `@angular/material`, this package provides prebuilt primary, accent and warn colors. These variables are named
- `$demo-primary`
- `$demo-accent`
- `$demo-warn`

They can be used when configuring the `@angular/material` palette:
```
@import '~@angular/material/theming';
@import '~@tallang/shared-design-demo/theme';

@include mat-core();
$primary-color:  mat-palette($demo-primary);
$accent-color:   mat-palette($demo-accent);
$warn-color:     mat-palette($demo-warn);
$theme:          mat-light-theme($primary-color, $accent-color, $warn-color);

@include angular-material-theme($theme);
```

# Fortum typography
The typography configuration is implemented as a SASS mixin, and can be used by including it in your styles:
```
@import '~@tallang/shared-design-demo/theme';

@include demo-typography();
```
The `demo-typography` mixin includes `color`, `font-size`, `font-weight`, `line-height`, `margin` and alignment for all common HTML text elements (h1, h2, p, b, strong, i, em, mark, del, ins). It also sets the global font family to `Montserrat` with a fallback to sans-serif if `Montserrat` is not available.
npm package: @talltotal/vuepress-plugin-ppt
Description: ppt plugin for vuepress
Author: talltotal
Latest version: 0.0.6

# [@talltotal/vuepress-plugin-ppt](https://talltotal.github.io/vuepress-plugin-ppt/)

## install
```bash
yarn add -D @talltotal/vuepress-plugin-ppt
# OR npm install -D @talltotal/vuepress-plugin-ppt
```

## Usage
### 在 `config.js` 中引入
```js
module.exports = {
    plugins: ['@talltotal/vuepress-plugin-ppt'] 
}
```


### 在 md 文档中使用
1. 在 `frontmatter` 增加 ppt 组件的配置，以及一些隐藏其他页面元素的设置
    - `showPage` Boolean 是否显示分页下标
    - `listStyle` Object 页面自定义样式，以页码为key
2. 正文部分用 `::: ppt` + `:::` 包裹，中间以 `----` 为分页标识

> 另外，最好在组件外加个容器或自定义布局
> 
> Additionally, you can add a container or custom layout outside the component

```md
---
navbar: false
# ppt options
ppt:
    title: '@talltotal/vuepress-plugin-ppt'
    # whether to display pagination
    showPage: true
    # custom style apply on each page
    baseStyle: 'text-shadow: 0 0 2px rgba(0,0,0,0.2);'
    # custom page-style with page number as 'key'
    listStyle:
        1: 'background-image: url(/imgs/bg.jpg)'
---

::: ppt
# page one
xxxx

----

# page two
xxxx

----

# page three
xxxx
:::
```

### 操作
- 键盘
    - ⬆️⬅️：上一张
    - ⬇️➡️：下一张
- 手势
    - 向左划：上一张
    - 向右划：下一张
npm package: @talltotal/webpack-dependencie
Description: Count the number of times the file is dependent.
Author: talltotal
Latest version: 0.0.2

# Webpack Dependencie
> webpack插件 + vscode插件组合，显示文件被依赖关系

> Count & Show the number of times the file is dependent.

==> WIP <==

## use


### webpack plugin

```js
import WebpackDependenciePlugin from '@talltotal/webpack-dependencie'
import webpack from 'webpack'

webpack({
    plugins: [
        new WebpackDependenciePlugin()
    ]
})
```

### vscode extension

在 `EXPLORER` 面板
- 文件右键 => `File References` 列出此文件被哪些文件依赖
- 文件夹右键 => `No References` 列出此文件夹下哪些文件没有被依赖

在 `EDITOR` 面板
- 右键 => `File References` 列出当前文件被哪些文件依赖

#### Settings

* `WebpackDependencie.open`: true 
    > Whether to turn on Definition Resolve.<br/>
    > 是否开启
npm package: @talltotal/wxapp-minify
Description: minify for wxapp
Author: talltotal
Latest version: 0.0.1-alpha.2

# wxapp-minify

为微信小程序原生语法设计的压缩脚本。

支持压缩的文件类型：`.wxss` `.json` `.wxml` `.svg`。

支持对`.wxss` `.wxml`和`.svg`文件的压缩结果缓存。



## 安装
```bash
npm i @talltotal/wxapp-minify -D
# or
yarn add @talltotal/wxapp-minify -D
```



## 使用
> 配置优先级：指令 > 配置文件 > 内置默认配置

配置文件`.minify.js`：
```js
// 这里展示的为默认配置
module.exports = {
    // 源码文件所放的位置
    srcPath: 'app',

    // 压缩文件所放的位置
    distPath: 'dist',

    // 是否开启缓存
    cache: true,
    
    // 存储缓存的路径
    cachePath: 'node_modules/.cache/wxapp-minify',
}
```


指令运行：
```bash
$ npx wxapp-minify
# or
$ ./node_modules/.bin/wxapp-minify --help

Usage: wxapp-minify [options] [targetDir]

压缩微信小程序原生语法文件

Options:
    -V, --version              output the version number
    -d, --dest <distPath>      压缩文件所放的位置（默认为'dist'）
    -c, --config <configPath>  配置文件的路径（默认为'.minify.js'）
    --cache <cache>            是否开启缓存（默认为'true'）
    --cachePath <cachePath>    存储缓存的路径（默认为'node_modules/.cache/wxapp-minify'）
    -h, --help                 display help for command
```


脚本中使用：
```js
const wxappMinify = require('@talltotal/wxapp-minify')

wxappMinify()
```



## 对比

### `miniprogram-ci@1.1.6`
- `minifyJS`
    - 使用`terser`或`uglify-js`压缩JS
- `minifyWXML`
    - 未使用`html-minifier`，只做了`code.replace(/\r\n/g, "\n")`
- `minifyWXSS`
    - 使用`cssnano`压缩WXSS
    - `{preset:["default",{ reduceTransforms:false,calc:false,minifySelectors:false,normalizeUrl:false }]}`
- `minify`


### `miniprogram-slim@1.0.0-beta.1`
- 使用`imagemin`对glob匹配的文件做压缩图片
- 使用`spritesmith`对glob匹配的文件做雪碧图（生成一个png和一个css）
- 使用`jscpd`对js做相似度对比分析
- 从`project.config.json`目录到各页面引入的组件以及各模块，找到所有使用的文件
npm package: @tallty/tallty-cli
Description: 前端脚手架工具
Latest version: 0.1.9

# A scaffold tool build for restful resources.

## Usage:

```shell
tallty generate scaffold user id:number name:string sex:female#male --shallow --only index#show
```

## Doc

```shell
tallty --help
```

## Develop

```shell
yarn link
```

## Publish to npm

```shell
npm login

npm publish --access public
```
npm package: @talltydev/tallty-cli
Description: 前端脚手架工具
Latest version: 0.2.35

# A scaffold tool build for restful resources.

## Usage:

```shell
tallty generate scaffold user id:number name:string sex:female#male --shallow --only index#show
```

## Doc

```shell
tallty --help
```

## Develop

```shell
yarn link
```

## Publish to npm

```shell
npm login

npm publish --access public
```
npm package: @tally/fordconnect-node-red
Description: Using official FordConnect API to get vehicle details
Latest version: 1.1.2

The FordConnect API allows developers to integrate FordConnect features into their applications. With the API, you can access vehicle data, control vehicle functions. This instructions will guide you through the process of using the FordConnect API in your node-red flows. Let's get started!

## Prerequisites

- Ford developer account. Generate clientId/clientSecret pair. More on: https://developer.ford.com/
- FordPass account. Be sure to complete your account setup before attempting to account link.

### Account Link

- Go to https://fordconnect.cv.ford.com/common/login/?make=F&application_id=AFDC085B-377A-4351-B23E-5E1D35FB3700&client_id=30990062-9618-40e1-a27b-7c6bcb23658a&response_type=code&state=123&redirect_uri=https%3A%2F%2Flocalhost%3A3000&scope=access
  Make sure that the Client ID in this URL matches the Client ID you received from developer.ford.com
- Using your account credentials, sign in to FordPass or Lincoln Way
- On the following screen, select the authorized vehicle in the vehicle list that you want to account link. This account linking process will enable you to retrieve vehicle data and execute remote vehicle commands.
- After you authorize the data sharing, you will be redirected to the _redirect_uri_ from the above url with the authorization code
- You will need the value after _code=_ for the _generate-tokens_ node

### Obtaining tokens

Generate tokens using auth code and clientId, clientSecret
![generate tokens flow](https://vsubbotskyy.github.io/fordConnect-node-red/images/generate-tokens.jpg)

### Using the API

After tokens are generated and saved to context you can start making requests to the API
![get vehicles list](https://vsubbotskyy.github.io/fordConnect-node-red/images/get-vehicles.jpg)

Access token is valid for 20 minutes, so if the request is failed with 401 status the token is probably expired. Failed requests with 401 status code will trigger output on the second output (to which get new tokens node can be hooked up). Other errors will be forwarded to the third output
![get vehicle details](https://vsubbotskyy.github.io/fordConnect-node-red/images/get-vehicle-details.jpg)

By default the car should send update on ignition status change. Sometimes vehicle info can be outdated, because server will return cached last values. To fetch the relevant data vehicle status request can be made. The request is non-blocking, so to delay output until refresh is completed "Wait for result check box" can be enabled in node config. There's also poll interval and max retry settings.
![refresh vehicle status](https://vsubbotskyy.github.io/fordConnect-node-red/images/refresh-vehicle-status.jpg)

To get relevant data from the car the flow might look like this
![get updated vehicle data](https://vsubbotskyy.github.io/fordConnect-node-red/images/get-updated-vehicle-status.jpg)

> [!CAUTION]
> Ford advises to be mindful of how often the vehicle is polled, because it has impact on battery life.
npm package: @tallypay/core
Description: Core types, trace IDs, and event emitter for TallyPay x402 instrumentation
Latest version: 0.0.3

# @tallypay/core

Framework-agnostic primitives for [x402](https://www.x402.org/) payment flows and [TallyPay](https://tallypay.dev) lifecycle tracing. Zero runtime dependencies beyond the Web/Node globals used (`fetch`, `crypto`).

## Install

```bash
npm install @tallypay/core
```

## What’s included

| Export | Description |
|--------|-------------|
| **`generateTraceId()`** | Time-sortable trace ID (ULID-style) for correlating events across client and server. |
| **`createEventEmitter(config)`** | Batched, non-blocking emitter that POSTs lifecycle events to the TallyPay collector. Drops events if the collector is unreachable—observability never blocks payments. |
| **`wrapFetch(fetch, config)`** | Wraps `fetch` to handle HTTP 402: parse `payment-required`, call your signer, retry with `payment-signature`. |
| **Types** | `PaymentRequired`, `PaymentRequirements`, `PaymentPayload`, `PaymentResponse` (aligned with the x402 shape you use in headers/body). |
| **Lifecycle types** | `PaymentLifecycleEvent`, `PaymentLifecycleEventType` (`402_ISSUED`, `402_RECEIVED`, `PAYMENT_SIGNED`, …). |

## Trace IDs

```ts
import { generateTraceId } from "@tallypay/core";

const traceId = generateTraceId();
```

## Event emitter (server or Node)

```ts
import { createEventEmitter } from "@tallypay/core";

const emitter = createEventEmitter({
  apiKey: "tp_live_...", // from TallyPay dashboard
  collectorUrl: "https://collector.tallypay.dev", // optional override
});

emitter.emit({
  traceId,
  eventType: "VERIFY_REQUESTED",
  source: "server",
  metadata: { endpoint: "/api/premium" },
});

await emitter.flush();
```

## Wrapped fetch (browser or Node 18+)

```ts
import { wrapFetch } from "@tallypay/core";

const paymentFetch = wrapFetch(fetch, {
  onPaymentRequired: async (paymentRequired, url) => {
    // Return the value for the `payment-signature` header (base64 payload per your stack).
    return signAndEncodePayment(paymentRequired, url);
  },
  onLifecycleEvent: (eventType, metadata) => {
    console.debug(eventType, metadata);
  },
});

const res = await paymentFetch("https://api.example.com/premium");
```

## Testing

From the monorepo root:

```bash
pnpm --filter @tallypay/core test
```

Or from this package: `pnpm test` (Vitest).

## License

MIT. Source code will be published on GitHub at launch; until then see [tallypay.dev](https://tallypay.dev).

## Links

- [TallyPay](https://tallypay.dev)
- [Documentation](https://tallypay.dev/docs) (when live)