open-index/open-npm huggingface dataset:
npm package: @gaiot/apis
Description: aiot apis
Author: glodoncv
Latest version: 2.4.5

[git 使用文档](./README.git.md) | 组件库使用文档

## 组件库使用文档

### 项目结构

```
sdk/
 |-.husky
 |-.storybook
 |-dist/
 |-example/
   |-App.tsx
   |-main.tsx
 |-node_modules/
 |-packages/
   |-api/
     |-common
       |-base.api.ts
       |-base.model.ts
     |-panorama
       |-index.ts
       |-model.ts
     |-index.ts
   |-react-biz-components/
     |-PanoramaMap
       |-index.ts
       |-style.less
   |-react-components/
     |-Button
       |-index.ts
       |-style.less
   |-index.tsx
 |-public/
 |-stories/
   |-Button/
     |-Button.stories.tsx
 |-package.json
 |-index.html
 |-vite.config
```

| 目录/文件  | 作用介绍                    |
| ---------- | --------------------------- |
| .storybook | 文档预览服务的配置文件      |
| dist       | 打包文件，上传到 npm 上的包 |
| example    | 开发组件挂在在 root         |
| packages   | 需要开发的组件              |
| stories    | 需要生成预览文档的组件      |

#### 组件开发

1、项目启动： `npm run dev`

2、预览：`http://localhost:3000`

3、App.tsx 中引入 packages 中开发的组件，example 中示例如下：

```
import React from 'react';
import { Button } from '../packages/index';
const Test = () => {
  return (
    <div>
      <Button label="按钮" primary></Button>
    </div>
  );
};

export default Test;
```

### 组件发布

1、执行`npm run build`打包文件

2、命令行使用`npm login`登录 npm

3、使用`npm publish`发布

package.json 上定义的基础入口信息和类型声明

```
  {
	  "name": "aiot-panorama-jssdk",
	  "private": false,
	  "version": "0.0.2",
	  "description": "React components",
	  "type": "module",
	  "keywords": [
		"react",
		"react-component"
	  ],
	  "files": [
		"dist"
	  ],
	  "main": "./dist/aiot-panorama-jssdk.umd.cjs",
	  "module": "./dist/aiot-panorama-jssdk.js",
	  "typings": "./dist/index.d.ts",
	  "exports": {
		".": {
		  "import": "./dist/aiot-panorama-jssdk.js",
		  "require": "./dist/aiot-panorama-jssdk.umd.cjs"
		},
		"./style.css": "./dist/style.css"
	  },
	  "repository": "",
	  "author": "gspace",
	  "license": "MIT"
  }
```

### 组件使用

#### 安装

```bash
yarn add aiot-panorama-jssdk
```

#### 使用

```
import { Button } from 'aiot-panorama-jssdk';
import "aiot-panorama-jssdk/style.css"

<Button label="按钮" primary></Button>

```

附：

[storybook 中文使用文档](https://storybook.js.org/tutorials/design-systems-for-developers/react/zh-CN/document/)

[storybook 英文使用文档](https://storybook.js.org/docs/react/get-started/introduction)
npm package: @gait-financial/react
Description: React wrappers for Gait Web Components
Latest version: 0.2.0

# @gait-financial/react

React wrapper for Gait Web Components. Use `<GaitButton>` with `data-id` and optional props for checkout/split payment.

## Install

```bash
npm install @gait-financial/react
```

## Setup

**1. Register once** (e.g. in your root or layout):

```tsx
import '@gait-financial/react/register';
```

**2. Use the component:**

```tsx
import { GaitButton } from '@gait-financial/react';

<GaitButton
  data-id="your-checkout-id"
  totalCost={99.99}
  onSplitFeedback={(d) => console.log(d.success ? 'OK' : d.error)}
/>
```

## Vite

Add to `vite.config.ts` so the web component script loads:

```ts
optimizeDeps: { exclude: ['@gait-financial/react'] },
```

## Builds (from repo root)

- **Production:** `npm run publish:react` — builds WC + React package, publishes to `latest`
- **Staging:** `npm run publish:react:staging` — builds with `.env.staging`, publishes with tag `staging`  
  From `packages/react`: `npm run publish:staging`

## Props

| Prop | Description |
|------|-------------|
| `data-id` | Checkout identity (required for payments) |
| `totalCost` | Total amount |
| `items` | Cart items for split payment |
| `customer` | `{ email, name? }` |
| `webhook` | `{ url, body? }` for split callbacks |
| `disabled`, `size`, `style` | Button options |
| `onClick`, `onLoaded`, `onDataProcessed`, `onSplitFeedback`, `onMerchantIdError`, `onConfirm` | Event callbacks |
npm package: @gait-tools/cypress-server-mock
Description: mocking library for cypress
Author: alex@gait.dev
Latest version: 2.0.1

# Cypress Server Mock

A tool for full stack mocking in cypress tests

## Installation

`npm i @gait-tools/cypress-server-mock`

## Usage

The package comes in 2 parts:
1. The cypress command
2. The api route called to implement mocking on the server

To use the cypress command add the following to your `support/commands.ts` file:

`import "@gait-tools/cypress-server-mock/commands";`

Currently only Next is supported.

Add a capture all api route under `/pages/api/mock/` e.g. `/pages/api/mock/[...mock].ts`.

Inside that file you can either export a pre-configured mock handler e.g.: 

```typescript
import { undiciHandler } from "@gait-tools/cypress-server-mock";
const opts = { 
   createApiPath: "string";
   restoreApiPath: "string";
   ...rest // opts specific to the custom handler - see typing for more details here
} 

export default undiciHandler(opts);
```

or build out your own handler: 

```typescript
import { createHandler } from "@gait-tools/cypress-server-mock";

export default createHandler({
   createHandler: async (mockConfig) => {
    // function to create your mocks
   },
    restoreHandler: async () => {
      // function to restore your mocks 
    },
    /** optional path your mocking create endpoint sits on.
     * defaults to `api/mock/create`
     */
    createApiPath: "string"; 
    /** optional path your mocking restore endpoint sits on.
     * defaults to `api/mock/restore`
     */
    restoreApiPath: "string";
});
```

You can then use the cypress server mock in your tests:
```typescript
it('should give me fake content', () => {
  cy.mockServerUrl({
    apiPath: "http://localhost:3000/api/mock", // the path to your mocking endpoints
    basePath: "http://external-service.company.com", // the path you want to mock
    path: "/content",
    method: "GET",
    response: {
      statusCode: 200,
      data: { content: "fake content" },
    }
  })
  
  cy.visit('http://localhost:3000');
})

afterEach(() => {
  cy.restoreServerMocks();
})
```

## Security
We are looking at implementing a default block such that these routes are not available in production builds, however we currently do not have that functionality.
 Ensure you only have these mocking routes for development/testing builds.

## Limitations
- Currently we only support NextJS routes
- We only allow you to mock api requests at the moment, but do not allow you to verify that a route was called
- These routes are currently available in production, we are looking to limit that
npm package: @gaius-bot/readdir
Description: Fast, dependency-less, stream-based recursive directory reads
Latest version: 1.0.0
Deprecated: Please use @chatsift/readdir instead

<div align="center">
  <img width="120" height="36" src="https://gaiusbot.me/wp-content/uploads/2020/08/GaiusBanner.png">
  <h4>
    Fast, dependency-less, stream-based recursive directory reads</a>
  </h3>

  <p align="center">
    <br />
    <h3>
      <strong>
        <a href="https://gaiusbot.me/">Learn about the bot</a>
      </strong>
    </h2>
  </p>  

  <p>
    <img src="https://github.com/GaiusCicereius/readdir/actions/workflows/quality.yml/badge.svg" alt="Quality Check">
    <a href="https://github.com/GaiusCicereius/readdir/blob/main/LICENSE"><img src="https://img.shields.io/badge/License-MIT-yellow.svg" alt="License: MIT"></a>
  </p>
</div>


# Contributing
We make use of [`PNPM`](https://pnpm.js.org/) to manage the project. It is expected that you have an up-to-date version of it. 

Please ensure you run `pnpm run lint`, `pnpm run build`, and `pnpm run test` in the root directory before pushing your commits.

If all checks out, [Submit a Pull Request](https://github.com/GaiusCicereius/readdir/compare)

Do keep in mind that this package has internal use, but I'd still be willing to add something to it if you find it useful.

# LICENSING

This project is a rewrite/fork of [readdirp](https://github.com/paulmillr/readdirp), licensed under the MIT license.

© 2012-2019 Thorsten Lorenz, Paul Miller (https://paulmillr.com)

© 2021, [didinele](https://github.com/didinele). Some rights reserved.
npm package: @gajduk/mendixmodelsdk
Description: Mendix Model SDK
Author: Mendix
Latest version: 4.56.1

# Mendix Model SDK

The Mendix Model SDK is a TypeScript- & JavaScript-based SDK that, through the Model SDK, provides access to the inner-workings of every Mendix app.

With the [Platform SDK](https://www.npmjs.com/package/mendixplatformsdk) and Model SDK, you can do the following:

- **Read** from your app model (for example, analyze the quality of your app model, or generate a high-level diagram to document your app)
- **Write** to your app model (for example, create a new entity in your domain model, add an activity to an existing microflow, even generate a whole new Mendix app based on a legacy code base)

Basically, the [Platform SDK](https://www.npmjs.com/package/mendixplatformsdk) and Model SDK allow you to automate any tedious or error-prone task. If you imagine it, there’s probably a way to do it via these SDKs.

## Documentation

See the [Mendix Platform SDK documentation](https://docs.mendix.com/apidocs-mxsdk/mxsdk/)
npm package: @gajduk/mendixplatformsdk
Description: Mendix Platform SDK
Author: Mendix
Latest version: 4.1.1

# Mendix Platform SDK

The Mendix Platform SDK defines TypeScript classes that provide access to the Project API
(https://docs.mendix.com/apidocs-mxsdk/apidocs/projects-api).
The Projects API allows you to programmatically create a project in your company space and move working copies between the Team Server and the Model Server.

## Installation

    npm install mendixplatformsdk

## Documentation

https://developers.mendix.com/model-sdk/