open-index/open-npm huggingface dataset:
npm package: @inte-cloud/plugins
Description: 这个软件包为 `lit-element` 用户界面组件提供了通用插件，它是作为一个可以独立使用的软件包发布的。
Latest version: 1.0.0

# @inte-cloud/plugins

这个软件包为 `lit-element` 用户界面组件提供了通用插件，它是作为一个可以独立使用的软件包发布的。

## LitElementResolver

A resolver for `unplugin-vue-components` and `unplugin-auto-import`.

```ts
import { LitElementResolver } from '@inte-cloud/plugins'

export default defineConfig({
  // ...
  plugins: [
    // ...
    AutoImport({
      resolvers: [LitElementResolver()],
    }),
    Components({
      resolvers: [LitElementResolver()],
    }),
  ],
})
```
npm package: @inte/acl
Description: A simple role-based access control.
Author: cipchk
Latest version: 2.0.0-beta.3

# @inte/acl module [![Build Status](https://travis-ci.org/ng-alain/inte.svg?branch=master)](https://travis-ci.org/ng-alain/inte) [![NPM version](https://img.shields.io/npm/v/@inte/acl.svg)](https://www.npmjs.com/package/@inte/acl) [![NPM version](https://img.shields.io/npm/v/@inte/acl/next.svg)](https://www.npmjs.com/package/@inte/acl) [![Taobao version](https://npm.taobao.org/badge/v/@inte/acl.svg?style=flat-square)](https://npm.taobao.org/package/@inte/acl)

A simple role-based access control.

## Links

- [Api Document](https://ng-alain.com/acl)
- [Demo](//ng-alain.github.io/ng-alain/)

## Architecture

![Architecture](https://raw.githubusercontent.com/ng-alain/inte/master/_screenshot/architecture.png)

## Troubleshooting

Please follow this guidelines when reporting bugs and feature requests:

1. Use [GitHub Issues](https://github.com/ng-alain/inte/issues) board to report bugs and feature requests (not our email address)
2. Please **always** write steps to reproduce the error. That way we can focus on fixing the bug, not scratching our heads trying to reproduce it.

Thanks for understanding!

### License

The MIT License (see the [LICENSE](https://github.com/ng-alain/inte/blob/master/LICENSE) file for the full text)
npm package: @inte/theme
Description: ng-alain theme system library.
Author: cipchk
Latest version: 2.0.0-beta.3

# @inte/theme module [![Build Status](https://travis-ci.org/ng-alain/inte.svg?branch=master)](https://travis-ci.org/ng-alain/inte) [![NPM version](https://img.shields.io/npm/v/@inte/theme.svg)](https://www.npmjs.com/package/@inte/theme) [![NPM version](https://img.shields.io/npm/v/@inte/theme/next.svg)](https://www.npmjs.com/package/@inte/theme) [![Taobao version](https://npm.taobao.org/badge/v/@inte/theme.svg?style=flat-square)](https://npm.taobao.org/package/@inte/theme)

ng-alain theme system library.

## Links


## Architecture

![Architecture](https://coding.net/u/dooo/p/inte/git/raw/master/_screenshot/architecture.png)


### License

No License
npm package: @inte/util
Description: Universal toolset of ng-alain.
Author: cipchk
Latest version: 2.0.0-beta.4

# @inte/util module [![Build Status](https://travis-ci.org/ng-alain/inte.svg?branch=master)](https://travis-ci.org/ng-alain/inte) [![NPM version](https://img.shields.io/npm/v/@inte/util.svg)](https://www.npmjs.com/package/@inte/util) [![NPM version](https://img.shields.io/npm/v/@inte/util/next.svg)](https://www.npmjs.com/package/@inte/util) [![Taobao version](https://npm.taobao.org/badge/v/@inte/util.svg?style=flat-square)](https://npm.taobao.org/package/@inte/util)

Universal toolset of ng-alain.

## Links


## Architecture

![Architecture](https://coding.net/u/dooo/p/inte/git/raw/master/_screenshot/architecture.png)


### License

No License
npm package: @intear/inevents-websocket-client
Description: Event streaming client for Intear events API
Author: INTEAR
Latest version: 1.1.0

# inevents-websocket-client

Event streaming client for Intear events API. This client allows you to subscribe to and process events from the Intear WebSocket API with automatic reconnection and error handling.

## Installation

```bash
npm install inevents-websocket-client
```

## Usage

```typescript
import { EventStreamClient } from 'inevents-websocket-client';

// Create a client
const client = EventStreamClient.default();

// Start streaming events
await client.streamEvents<YourEventType>(
    'event_name',
    async (event) => {
        // Handle each event
        console.log('Received event:', event);
    }
);

// To stop streaming
client.abort();
```

### Custom Server URL

```typescript
const client = new EventStreamClient('wss://your-server.com');
```

### Type-Safe Events

The client is fully type-safe. Define your event types for better TypeScript integration:

```typescript
interface MyEvent {
    event_type: string;
    data: Record<string, unknown>;
}

await client.streamEvents<MyEvent>(
    'my_event',
    async (event) => {
        // event is typed as MyEvent
        console.log(event.event_type);
    }
);
```

## Features

- Type-safe event streaming
- Automatic reconnection on connection loss
- Proper error handling
- Clean shutdown support
- WebSocket ping/pong handling
- Configurable server URL

## License

MIT
npm package: @intech.lu/eslint-config
Description: ESLint rules for InTech projects
Author: InTech S.A.
Latest version: 2.0.2

# InTech ESLint Rules

Welcome to the "InTech ESLint Rules" repository, a centralized solution for managing and applying consistent code quality standards accross all projects at InTech. This repository hosts a custom ESLint configuration designed to enforce a unified coding style and coding best practices helping to ensure maintainability and reducing code quality discrepancies in collaborative projects.

## 🗂️ Table of Contents

1. [Installation](#⚙️-installation)
    1. [Requirements](#📋-requirements)
    2. [Step 1: install the ESLint extension for VSCode](#1️⃣-step-1-install-the-eslint-extension-for-vscode)
    3. [Step 2: install ESLint and the InTech rules](#2️⃣-step-2-install-eslint-and-the-intech-rules)
    4. [Step 3: create the ESLint configuration](#3️⃣-step-3-create-the-eslint-configuration)
    5. [Step 4: enjoy 🎉](#4️⃣-step-4-enjoy-🎉)

## ⚙️ Installation

Add the InTech ESLint Rules on your existing project.

### 📋 Requirements

- NPM version >= 9
- Node.js version >= `v18.18.0`

### 1️⃣ Step 1: install the ESLint extension for VSCode

- <https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint>

Create a `.vscode/settings.json` file with the following configuration at the root of your project:

```json
{
  "editor.codeActionsOnSave": {
    "source.fixAll.eslint": true
  },
  "eslint.validate": ["javascript", "typescript", "html"]
}
```

### 2️⃣ Step 2: install ESLint and the InTech rules

Go to the folder of your project and execute the following command:

```bash
npm install -D eslint '@intech.lu/eslint-config'
```

Note: *You'll have to install ESLint at least version 9 as it includes breaking changes and reworks the way ESLint is executed.*

### 3️⃣ Step 3: create the ESLint configuration

At the root of your project, create an `eslint.config.mjs` file with the following content:

```js
import eslintConfig from '@intech.lu/eslint-config';

export default [ 
  ...eslintConfig,
];
```

If you need to override the InTech rules for some reason, simply do it by adding rules in your `eslint.config.mjs`, it will override the InTech related ones:

```js
import eslintConfig from '@intech.lu/eslint-config';

export default [ 
  ...eslintConfig,
  {
    rules: {
      'no-console': 'error', // will switch InTech 'no-console' rule value from 'warn' to 'error'
    }
  },
];
```

⚠️ *NB: You should always override InTech rules after destructuring `eslintConfig`, otherwise `eslintConfig` will take precedence and override the rules you've just added.*

### 4️⃣ Step 4: enjoy 🎉

You now have the InTech ESLint rules applied automatically to your project.
npm package: @intech.lu/eslint-config-angular
Description: ESLint rules for InTech Angular projects
Author: InTech S.A.
Latest version: 2.0.1

# InTech Angular ESLint rules

Welcome to the "InTech Angular ESLint rules" repository, a centralized solution for managing and applying consistent code quality standards accross all projects at InTech using Angular. This repository hosts a custom ESLint configuration designed to enforce a unified coding style and coding best practices helping to ensure maintainability and reducing code quality discrepancies in collaborative projects.

## 🗂️ Table of Contents

1. [Installation](#⚙️-installation)
    1. [Requirements](#📋-requirements)
    2. [Step 1: install the ESLint extension for VSCode](#1️⃣-step-1-install-the-eslint-extension-for-vscode)
    3. [Step 2: install ESLint and the InTech rules](#2️⃣-step-2-install-eslint-and-the-intech-rules)
    4. [Step 3: create the ESLint configuration](#3️⃣-step-3-create-the-eslint-configuration)
    5. [Step 4: enjoy 🎉](#4️⃣-step-4-enjoy-🎉)
2. [Contribute](#🤝-contribute)
    1. [Development](#💻-development)
    2. [Deployment](#🚀-deployment)

## ⚙️ Installation

Add the InTech Angular ESLint rules on your existing project.

### 📋 Requirements

- NPM version >= 9
- Node.js version >= `18.18.0`
- Angular version >= `18.0.0`

#### Supported versions

| Angular            | InTech Angular ESLint |
| ------------------ | --------------------- |
| >= 18.0.0          | >= 2.0.0              |
| < 18.0.0           | >=1.0.0 <2.0.0        |

### 1️⃣ Step 1: install the ESLint extension for VSCode

- <https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint>

Create a `.vscode/settings.json` file with the following configuration at the root of your project:

```json
{
  "editor.codeActionsOnSave": {
    "source.fixAll.eslint": true
  },
  "eslint.validate": ["javascript", "typescript", "html"]
}
```

### 2️⃣ Step 2: install ESLint and the InTech rules

Go to the folder of your project and execute the following command:

```bash
npm install -D eslint '@intech.lu/eslint-config-angular'
```

Note: *You'll have to install ESLint at least version 9 as it includes breaking changes and reworks the way ESLint is executed.*

### 3️⃣ Step 3: create the ESLint configuration

At the root of your project, create an `eslint.config.mjs` file with the following content:

```js
import eslintConfig from '@intech.lu/eslint-config-angular';

export default [ 
  ...eslintConfig,
];
```

If you need to override the InTech rules for some reason, simply do it by adding rules in your `eslint.config.mjs`, it will override the InTech related ones:

```js
import eslintConfig from '@intech.lu/eslint-config-angular';

export default [ 
  ...eslintConfig,
  {
    rules: {
      'no-console': 'error', // will switch InTech 'no-console' rule value from 'warn' to 'error'
    }
  },
];
```

⚠️ *NB: You should always override InTech rules after destructuring `eslintConfig`, otherwise `eslintConfig` will take precedence and override the rules you've just added.*

### 4️⃣ Step 4: enjoy 🎉

You now have the InTech Angular ESLint rules applied automatically to your project.
npm package: @intech.lu/eslint-config-react
Description: ESLint rules for InTech React projects
Author: InTech S.A.
Latest version: 1.1.0

# InTech React ESLint Rules

Welcome to the "InTech React ESLint rules" repository, a centralized solution for managing and applying consistent code quality standards accross all projects at InTech using React. This repository hosts a custom ESLint configuration designed to enforce a unified coding style and coding best practices helping to ensure maintainability and reducing code quality discrepancies in collaborative projects.

## 🗂️ Table of Contents

1. [Installation](#⚙️-installation)
    1. [Requirements](#📋-requirements)
    2. [Step 1: install the ESLint extension for VSCode](#1️⃣-step-1-install-the-eslint-extension-for-vscode)
    3. [Step 2: install ESLint and the InTech rules](#2️⃣-step-2-install-eslint-and-the-intech-rules)
    4. [Step 3: create the ESLint configuration](#3️⃣-step-3-create-the-eslint-configuration)
    5. [Step 4: enjoy 🎉](#4️⃣-step-4-enjoy-🎉)

## ⚙️ Installation

Add the InTech ESLint Rules on your existing project.

### 📋 Requirements

- NPM version >= 9
- Node.js version >= `v18.18.0`

### 1️⃣ Step 1: install the ESLint extension for VSCode

- <https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint>

Create a `.vscode/settings.json` file with the following configuration at the root of your project:

```json
{
  "editor.codeActionsOnSave": {
    "source.fixAll.eslint": true
  },
  "eslint.validate": ["javascript", "typescript", "html"]
}
```

### 2️⃣ Step 2: install ESLint and the InTech rules

Go to the folder of your project and execute the following command:

```bash
npm install -D eslint '@intech.lu/eslint-config'
```

Note: *You'll have to install ESLint at least version 9 as it includes breaking changes and reworks the way ESLint is executed.*

### 3️⃣ Step 3: create the ESLint configuration

At the root of your project, create an `eslint.config.mjs` file with the following content:

```js
import eslintConfig from '@intech.lu/eslint-config';

export default [ 
  ...eslintConfig,
];
```

If you need to override the InTech rules for some reason, simply do it by adding rules in your `eslint.config.mjs`, it will override the InTech related ones:

```js
import eslintConfig from '@intech.lu/eslint-config';

export default [ 
  ...eslintConfig,
  {
    rules: {
      'no-console': 'error', // will switch InTech 'no-console' rule value from 'warn' to 'error'
    }
  },
];
```

⚠️ *NB: You should always override InTech rules after destructuring `eslintConfig`, otherwise `eslintConfig` will take precedence and override the rules you've just added.*

### 4️⃣ Step 4: enjoy 🎉

You now have the InTech ESLint rules applied automatically to your project.
npm package: @intech.lu/eslint-config-vue
Description: ESLint rules for InTech Vue projects
Author: InTech S.A.
Latest version: 2.0.2

# InTech Vue ESLint Rules

Welcome to the "InTech Vue ESLint Rules" repository, a centralized solution for managing and applying consistent code quality standards accross all projects at InTech. This repository hosts a custom ESLint configuration designed to enforce a unified coding style and coding best practices helping to ensure maintainability and reducing code quality discrepancies in collaborative projects.

## 🗂️ Table of Contents

1. [Installation](#⚙️-installation)
    1. [Requirements](#📋-requirements)
    2. [Step 1: install the ESLint extension for VSCode](#1️⃣-step-1-install-the-eslint-extension-for-vscode)
    3. [Step 2: install ESLint and the InTech rules](#2️⃣-step-2-install-eslint-and-the-intech-rules)
    4. [Step 3: create the ESLint configuration](#3️⃣-step-3-create-the-eslint-configuration)
    5. [Step 4: enjoy 🎉](#4️⃣-step-4-enjoy-🎉)

## ⚙️ Installation

Add the InTech ESLint Rules on your existing project.

### 📋 Requirements

- NPM version >= 9
- Node.js version >= `v18.18.0`

### 1️⃣ Step 1: install the ESLint extension for VSCode

- <https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint>

Create a `.vscode/settings.json` file with the following configuration at the root of your project:

```json
{
  "editor.codeActionsOnSave": {
    "source.fixAll.eslint": true
  },
  "eslint.validate": ["javascript", "typescript", "html"]
}
```

### 2️⃣ Step 2: install ESLint and the InTech rules

Go to the folder of your project and execute the following command:

```bash
npm install -D eslint '@intech.lu/eslint-vue'
```

Note: *You'll have to install ESLint at least version 9 as it includes breaking changes and reworks the way ESLint is executed.*

### 3️⃣ Step 3: create the ESLint configuration

At the root of your project, create an `eslint.config.mjs` file with the following content:

```js
import eslintConfig from '@intech.lu/eslint-config-vue';

export default [ 
  ...eslintConfig,
];
```

If you need to override the InTech rules for some reason, simply do it by adding rules in your `eslint.config.mjs`, it will override the InTech related ones:

```js
import eslintConfig from '@intech.lu/eslint-config-vue';

export default [ 
  ...eslintConfig,
  {
    rules: {}
  },
];
```

⚠️ *NB: You should always override InTech rules after destructuring `eslintConfig`, otherwise `eslintConfig` will take precedence and override the rules you've just added.*

### 4️⃣ Step 4: enjoy 🎉

You now have the InTech ESLint rules applied automatically to your project.
npm package: @intechstudio/grid-luafmt
Description: Format Lua code
Author: Expo
Latest version: 1.20241030.1555
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

[![Build Status](https://travis-ci.org/trixnz/lua-fmt.svg?branch=master)](https://travis-ci.org/trixnz/lua-fmt) [![NPM Package](https://img.shields.io/npm/v/lua-fmt.svg)](https://www.npmjs.com/package/lua-fmt)

# Code Formatter for Lua
`lua-fmt` is pretty-printer for [Lua](https://www.lua.org/) code, written in [TypeScript](https://www.typescriptlang.org/) and deeply inspired by [prettier](https://github.com/prettier/prettier). `lua-fmt` provides an interface to format Lua code that conforms to a single and consistent standard.

While not implemented yet, the interface will be customizable to tailor the output to the user's preferences: linebreaks, string style, etc.

## Installing
* `npm install lua-fmt`

## Usage
### API
```TypeScript
import {formatText} from 'lua-fmt';
console.log(formatText('local hello = "Hello"; print(hello .. " world!")'))
```

### Command Line
Format a single file:
* `luafmt test/lua-5.3.4-tests/calls.lua`

Format a stream from `stdin`:
* `cat test/lua-5.3.4-tests/calls.lua | luafmt --stdin`

## TODO
- [ ] Add support for a `.luafmt` preferences file

## Testing
`lua-fmt` uses [jest](https://facebook.github.io/jest/) for automated testing.

Among the user-created tests in the `test/` folder, a copy of the `lua-5.3.4` tests are executed after formatting to ensure the code remains syntactically correct after formatting. For this reason, please do not modify the `lua-5.3.4-tests` folder unless updating with new tests from the official Lua tests. To run these tests, `lua53` is expected to be available on the `PATH`.

When contributing changes, please consider writing tests to ensure they do not regress.

## License

This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.

## Acknowledgments
* [Oskar Schöldström](https://github.com/oxyc) - [luaparse](https://github.com/oxyc/luaparse): A Lua parser written in JavaScript
* [Christopher Chedeau](https://github.com/vjeux) - [prettier](https://github.com/prettier/prettier): Prettier is an opinionated JavaScript formatter.
* [Ben Newman](https://github.com/benjamn) - [recast](https://github.com/benjamn/recast): JavaScript syntax tree transformer, nondestructive pretty-printer, and automatic source map generator.