open-index/open-npm huggingface dataset:
npm package: @ondc-ui/dictionary
Description: Dictionary token for ONDC design system 
Author: Pratik Sharma
Latest version: 1.1.0

# ONDC Token

A dictionary token package for the ONDC design system. This package contains various JSON files representing structured data for use within the ONDC design ecosystem.

## Features
- Provides JSON files for various aspects of the ONDC design system.
- Easy to integrate into projects.
- Well-structured and standardized data representation.

## Included Files
The package includes the following JSON files:

- **payment.json**: Payment-related configurations.
- **privacy.json**: Privacy-related data.
- **security.json**: Security-related configurations.
- **shop.json**: Shop-related data.
- **time.json**: Time-related information.
- **token.json**: Token definitions.
- **ui.json**: UI-specific configurations.

## Installation

To install the package, use npm:

```bash
npm install @ondc-ui/dictionary
```

## Usage

Import and use the JSON files in your project:

```javascript
// Import a specific JSON file
const tokenData = require('@ondc-ui/dictionary');

console.log(tokenData);
```

You can also access other JSON files similarly by specifying the file name.

## Development

This package is part of the ONDC design system workspace (`ondc-ui`). Contributions and improvements are welcome.

### Testing Locally
To test the package before publishing:

1. Run the following command to pack the module:
   ```bash
   npm pack
   ```
2. Verify the contents of the `.tgz` file.

## Author
Pratik Sharma  
[Email](mailto:sharma.pratik2016@gmail.com)  
[GitHub - @biomathcode](https://github.com/biomathcode)

## License

This package is licensed under the MIT License. See the LICENSE file for details.
npm package: @ondc/automation-logger
Description: logger for protocol workbench ondc
Author: extedcouD
Latest version: 1.1.0

# Automation Logger Package

A robust, structured logging utility for Node.js applications, designed for the ONDC ecosystem and beyond. The Automation Logger Package provides a consistent API for logging across environments, with native support for Grafana Loki in production and developer-friendly, colorized logs in development.

## Features

- **Singleton Logger Instance:** Ensures a single logger instance throughout your application.
- **Multiple Log Levels:** Supports `info`, `error`, `debug`, and `warning` with structured arguments.
- **Axios Error Handling:** Special support for logging detailed Axios errors (request, response, code, stack).
- **Environment-Aware:** Adapts output and transports based on `NODE_ENV`—pretty console output in development, Loki JSON in production.
- **Correlation Middleware:** Express middleware to attach/request a correlation ID for traceability.
- **Profiler:** Timer/profiler utility for measuring durations of code execution.
- **Extensible:** Built on top of [winston](https://github.com/winstonjs/winston) with support for custom transports and formats.

## Installation

```bash
npm i @ondc/automation-logger
```

## Usage

### Basic Logging

```typescript
import logger from "@ondc/automation-logger";

logger.info("Service started", { user: "alice" });
logger.error("Failed to process request", new Error("Something went wrong"));
logger.debug("Debug message", { debugInfo: "details" });
logger.warning("Potential issue detected", { details: "..." });
```

### Profiling Code

```typescript
const profiler = logger.startTimer();
// ... your code
profiler.done({ message: "Finished task", corrId: "abc123" });
```

### Express Correlation Middleware

To add a correlation ID to every incoming request:

```typescript
import logger from "@ondc/automation-logger";
app.use(logger.getCorrelationIdMiddleware());
```

## Environment Variables

- `SERVICE_NAME` (required): Sets the service label for logs.
- `NODE_ENV` (required): Should be `production` or `development`.
- `LOG_LEVEL`: Log level (`info`, `debug`, etc.). Defaults to `info`.
- `LOKI_HOST`: URL for Grafana Loki (required in production for remote logging).

## Example

```typescript
import logger from "@ondc/automation-logger-package";

logger.info("Application started", "extraContext");
logger.error("API call failed", new Error("Bad request"));
```

## Development & Testing

- Colorized, human-readable logs in development.
- Structured, JSON logs for Loki in production.

## License

See [LICENSE](LICENSE) for details.

---

> For more, see the [repository](https://github.com/ONDC-Official/automation-logger-package)
npm package: @ondeliverys/eslint-config
Description: ESLint config for OnDeliverys projects
Author: OnDeliverys, Matheus Santos Ferreira Ribeiro
Latest version: 1.0.8

# Ondeliverys ESLint Configuration

## What's included?

- Standard base configuration;
- React plugin;
- React Hooks plugin;
- JSX a11y plugin;
- Prettier;

## Setup

### React (with Next.js)

Install dependencies:

```bash
npm i -D eslint @ondeliverys/eslint-config
```

Inside `.eslintrc.json`:

```json
{
  "extends": [
    "@ondeliverys/eslint-config/next", 
    "next/core-web-vitals"
  ]
}
```

### Electron

Install dependencies:

```bash
npm i -D eslint @ondeliverys/eslint-config
```

Inside `.eslintrc.json`:

```json
{
  "extends": "@ondeliverys/eslint-config/electron"
}
```

### Nest.js

Install dependencies:

```bash
npm i -D eslint @ondeliverys/eslint-config
```

Inside `.eslintrc.json`:

```json
{
  "extends": "@ondeliverys/eslint-config/nest"
}
```

### Node.js

Install dependencies:

```bash
npm i -D eslint @ondeliverys/eslint-config
```

Inside `.eslintrc.json`:

```json
{
  "extends": "@ondeliverys/eslint-config/node"
}
```
### React Native

Install dependencies:

```bash
npm i -D eslint @ondeliverys/eslint-config
```

Inside `.eslintrc.json`:

```json
{
  "extends": "@ondeliverys/eslint-config/reactnative"
}
```

## Contribution

If you find issues or have suggestions for improvements, feel free to open an [issue](https://github.com/seu-usuario/eslint-config-ondeliverys/issues) in this repository.

## License

This package is licensed under the [MIT License](https://opensource.org/licenses/MIT).
npm package: @ondeoma/ts-generics-macro
Description: Macros with type generics for TypeScript
Author: hyranno
Latest version: 0.0.6

# ts-generics-macro

This is a Source Transformer that allows you to create function macros in TypeScript.
It is designed for use with [ts-patch](https://github.com/nonara/ts-patch).

This package is inspired by [ts-macros](https://github.com/GoogleFeud/ts-macros).
While `ts-macros` is a great tool,
  it appears to be currently unmaintained (no commits for over 2 years and inactive on issues/PRs),
  which has left some instability around generics unresolved.

This project aims to provide a **focused** alternative specifically for fundamental function macros,
  prioritizing stability around generics.

## Usage

### 1. Configuration

Add it to your `tsconfig.json`:
```json
{
  "compilerOptions": {
    "plugins": [
      {"transform": "@ondeoma/ts-generics-macro"}
    ]
  }
}
```

### 2. Writing Macros

**In your code:**
```typescript
// Define your macro function.
// By default, functions ending with "$macro$" are treated as macros.
function add$macro$(
  a: number,
  b: number,
): number {
  return a + b;
}

// Use the macro.
console.log(add$macro$(1, 2));
```

**Transformed result:**
```typescript
// Define your macro function.
// By default, functions ending with "$macro$" are treated as macros.
function add$macro$(
  a: number,
  b: number,
): number {
  throw "This is macro. Call of this function should have been expanded at compile time.";
}

// Use the macro.
console.log(
  (function (
    a: number,
    b: number,
  ): number {
    return a + b;
  })(1, 2)
);
```
The macro call is expanded inline, wrapping the body.

You can check `package/test-fixtures` for more examples of source codes and their expected transformed outputs.

## Options
- `macroSuffix`: The function name suffix used to identify macros. Default is `$macro$`.

## Notes
Standard Source Transformers do not automatically update the `TypeChecker` after modifying the AST.
Since this transformer relies on the `TypeChecker` (and modifies the AST itself),
  chaining it with other transformers may lead to stale type information.

To ensure the `TypeChecker` remains up-to-date throughout the transformation pipeline,
  consider using [ts-rebuild](https://github.com/Ondeoma/ts-rebuild) to rebuild the program where necessary.
npm package: @ondeoma/ts-print
Description: Print source files as a transformer.
Author: hyranno
Latest version: 0.0.3

# ts-print
This is a simple Source Transformer that prints the AST to files instead of transforming the code.
It is designed for use with [ts-patch](https://github.com/nonara/ts-patch).

This tool is primarily intended for debugging purposes, allowing you to inspect the AST structure.

## Usage
```json
{
  "compilerOptions": {
    "plugins": [
      {
        "transform": "ts-print",
        "inputDir": "src",
        "outputDir": "printed"
      }
    ]
  }
}
```
See `packages/example` for complete example.

## Notes
- `inputDir`: This option is used to determine the relative path structure for the output files. The transformer does not read files directly from this directory (it processes files handled by the compiler).

- `--noEmit`: This transformer does not work with the --noEmit option, as Source Transformers run during the emit phase. Related issue: [ts-patch#178](https://github.com/nonara/ts-patch/issues/178).
npm package: @ondeoma/ts-rebuild
Description: Transformer to update type-checker after other transformers.
Author: hyranno
Latest version: 0.1.3

# ts-rebuild

This is a Program Transformer that wraps other Source Transformers and rebuilds the `ts.Program` to update the `TypeChecker`.
It is designed for use with [ts-patch](https://github.com/nonara/ts-patch).


## Usage

Configure it in your `tsconfig.json` as follows:

```json
{
  "compilerOptions": {
    "plugins": [
      {
        "transform": "@ondeoma/ts-rebuild",
        "transformProgram": true,
        "children": [
          { "transform": "some-type-changing-transformer" }
        ]
      },
      { "transform": "transformer-needs-updated-typechecker" }
    ]
  }
}
```

See `packages/example` for a complete example.


## Background

Standard Source Transformers modify the AST (Abstract Syntax Tree),
  but TypeScript does not automatically update the TypeChecker to reflect these changes.
This causes issues when subsequent transformers depend on up-to-date type information (e.g., retrieving types of newly generated nodes).

`ts-rebuild` solves this by wrapping your Source Transformers and acting as a Program Transformer.
It ensures the `TypeChecker` is refreshed after the source transformations are applied,
  allowing downstream transformers to work correctly.
npm package: @ondeoma/ts-tiny-reflect
Description: Reflection for TypeScript
Author: hyranno
Latest version: 0.0.7

# ts-tiny-reflect
This is a Source Transformer that allows you to get type metadata in TypeScript.
It is designed for use with [ts-patch](https://github.com/nonara/ts-patch).

## Usage

### 1. Configuration

Add it to your `tsconfig.json`:
```json
{
  "compilerOptions": {
    "plugins": [
      {"transform": "@ondeoma/ts-tiny-reflect"}
    ]
  }
}
```

### 2. Writing code
**In your code:**
```typescript
import tiny_reflect from "@ondeoma/ts-tiny-reflect/macros";
tiny_reflect.typeMetadata<[number, string]>();
```

**Transformed result:**
```typescript
import tiny_reflect from "@ondeoma/ts-tiny-reflect/macros";
({
    "kind": "tuple",
    "elements": [
        {
            "kind": "primitive",
            "typeName": "number"
        },
        {
            "kind": "primitive",
            "typeName": "string"
        }
    ]
});
```

See `packages/tis-tiny-reflect/macros` for full list of macros.