open-index/open-npm huggingface dataset:
npm package: @souvikme/commitgenie
Description: > Stop wasting time thinking of commit messages. CommitGenie reads your staged changes and generates meaningful, conventional commit messages instantly.
Author: souvikme
Latest version: 1.3.0
Deprecated: Moved to @ztv-main/commitgenie. Run: npm i -g @ztv-main/commitgenie

﻿# CommitGenie 🧠

> Stop wasting time thinking of commit messages. CommitGenie reads your staged changes and generates meaningful, conventional commit messages instantly.

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

---

## The Problem

We've all written commits like `"fixed stuff"`, `"update"`, or `"changes"`.  
They're useless for code history, PR reviews, and team collaboration.  
**CommitGenie fixes that — in one command.**

---

## Install
```bash
npm install -g @souvikme/commitgenie
```

---

## Setup

Get a **free** Groq API key at [console.groq.com](https://console.groq.com), then create a `.env` file in your project root:
```bash
GROQ_API_KEY=your_key_here
```

---

## Usage
```bash
# 1. Stage your changes
git add .

# 2. Run CommitGenie
commitgenie
```

That's it. No configuration needed. No extra steps.

---

## How It Works
```
git add .  →  commitgenie  →  AI reads your diff  →  generates commit message  →  you confirm
```

CommitGenie reads exactly what you staged with `git diff --cached`, sends it to Groq's AI, and returns a structured commit message following the **Conventional Commits** standard.

---

## Interactive Menu
```
🧠 CommitGenie

✔ Done!

📝 Suggested commit message:

  feat(auth): add JWT refresh token rotation

  Implements automatic token rotation on refresh to improve security.
  Tokens are now invalidated after single use.

? What do you want to do?
❯ ✅  Use this message & commit
  ✏️   Edit message
  🔄  Regenerate
  ❌  Cancel
```

---

## Commit Message Format

CommitGenie follows the [Conventional Commits](https://www.conventionalcommits.org/) specification:
```
<type>(<scope>): <short description>

[optional body]
```

| Type | When it's used |
|------|---------------|
| `feat` | New feature added |
| `fix` | Bug fix |
| `refactor` | Code restructured |
| `docs` | Documentation changes |
| `test` | Tests added or updated |
| `chore` | Build, config, dependencies |
| `perf` | Performance improvement |

---

## Real Examples
```bash
feat(auth): add JWT refresh token rotation
fix(api): handle null response from payment gateway
refactor(dashboard): extract chart into separate component
docs(readme): update installation instructions
chore(deps): upgrade typescript to v5
```

---

## Requirements

- Node.js 16+
- Git installed
- Free Groq API key ([get one here](https://console.groq.com))

---

## License

MIT

---

## Author

Built by [Souvik Ghosh](https://github.com/souvikree)

---

*If this saved you time, consider giving it a ⭐ on GitHub!*
npm package: @souyahia/eslint-config-base
Description: The base ESLint config that I use in my pure JS projects
Author: souyahia
Latest version: 1.0.1

# @souyahia/eslint-config-base

This package provides the base ESlint configuration that I use in my pure JS projects.

# Installation

To install this eslint configuration, simply run the following command :

```
yarn add -D @souyahia/eslint-config-base
```

Until ESlint flat config is implemented (_see the note below_), you will also need to install the required peer
dependencies.

# How to Use

To extend this config, simply place the following snipplet in your `.eslintrc.js` to include the config :

```javascript
module.exports = {
  extends: ['@souyahia/eslint-config-base'],
};
```

# A note reguarding ESlint Flat Configs

Due to the limitations of how ESlint works right now, shared ESlint configurations **need** to specify their
dependencies (such as other configs, plugins etc...) as peer dependencies. This forces developers that want to use my
config to manually download each one of my dependencies. This is obviously very cumbersome and kind of misses the whole
point of a shared config. This is even more true when it comes to monorepos.There are ways of bypassing thislimitation
([@rushstack/eslint-patch](https://www.npmjs.com/package/@rushstack/eslint-patch) etc...) but they come with their own
limitations and are considered as "patches" rather than actual features.

However, in August 2022, the ESlint team came up with
[a new config system called ESlint Flat Config](https://eslint.org/blog/2022/08/new-config-system-part-1/). This new
config system allows (among other things) for a shared config to declare its dependencies as dev (or regular)
dependencies, and include them in the config file (by importing them as a node package). This is obviously great news
for me, since it basically means all of the issues listed in the previous paragraph will be solved. However, I need to
give time to ESlint configs and plugins packages to adapt to this new config system. For instance, the
typescript-eslint package created [an issue](https://github.com/typescript-eslint/typescript-eslint/issues/5938) on the
08/11 to update their config system.

This means that for now, I need to stick with the old config and its peer dependencies, and keep an eye on the package
updates until the new ESlint config system is mature enough for us to migrate to it.

Some references to read more about this subject :

- https://github.com/eslint/eslint/issues/3458
- https://eslint.org/blog/2022/08/new-config-system-part-1/
- https://eslint.org/blog/2022/08/new-config-system-part-2/
- https://eslint.org/blog/2022/08/new-config-system-part-3/
- https://github.com/eslint/eslint/issues/13481
- https://eslint.org/docs/latest/user-guide/configuring/configuration-files-new
- https://github.com/typescript-eslint/typescript-eslint/issues/5938
npm package: @souyahia/eslint-config-react
Description: The base ESLint config that I use in my React TypeScript projects
Author: souyahia
Latest version: 1.0.1

# @souyahia/eslint-config-base

This package provides the base ESlint configuration that I use in my pure JS projects.

# Installation

To install this eslint configuration, simply run the following command :

```
yarn add -D @souyahia/eslint-config-base
```

Until ESlint flat config is implemented (_see the note below_), you will also need to install the required peer
dependencies.

# How to Use

To extend this config, simply place the following snipplet in your `.eslintrc.js` to include the config :

```javascript
module.exports = {
  extends: ['@souyahia/eslint-config-base'],
};
```

# A note reguarding ESlint Flat Configs

Due to the limitations of how ESlint works right now, shared ESlint configurations **need** to specify their
dependencies (such as other configs, plugins etc...) as peer dependencies. This forces developers that want to use my
config to manually download each one of my dependencies. This is obviously very cumbersome and kind of misses the whole
point of a shared config. This is even more true when it comes to monorepos.There are ways of bypassing thislimitation
([@rushstack/eslint-patch](https://www.npmjs.com/package/@rushstack/eslint-patch) etc...) but they come with their own
limitations and are considered as "patches" rather than actual features.

However, in August 2022, the ESlint team came up with
[a new config system called ESlint Flat Config](https://eslint.org/blog/2022/08/new-config-system-part-1/). This new
config system allows (among other things) for a shared config to declare its dependencies as dev (or regular)
dependencies, and include them in the config file (by importing them as a node package). This is obviously great news
for me, since it basically means all of the issues listed in the previous paragraph will be solved. However, I need to
give time to ESlint configs and plugins packages to adapt to this new config system. For instance, the
typescript-eslint package created [an issue](https://github.com/typescript-eslint/typescript-eslint/issues/5938) on the
08/11 to update their config system.

This means that for now, I need to stick with the old config and its peer dependencies, and keep an eye on the package
updates until the new ESlint config system is mature enough for us to migrate to it.

Some references to read more about this subject :

- https://github.com/eslint/eslint/issues/3458
- https://eslint.org/blog/2022/08/new-config-system-part-1/
- https://eslint.org/blog/2022/08/new-config-system-part-2/
- https://eslint.org/blog/2022/08/new-config-system-part-3/
- https://github.com/eslint/eslint/issues/13481
- https://eslint.org/docs/latest/user-guide/configuring/configuration-files-new
- https://github.com/typescript-eslint/typescript-eslint/issues/5938
npm package: @souyahia/eslint-config-typescript
Description: The base ESLint config that I use in my TypeScript projects
Author: souyahia
Latest version: 1.0.2

# @souyahia/eslint-config-typescript

This package provides the base ESlint configuration that I use in my TypeScript projects.

# Installation

To install this eslint configuration, simply run the following command :

```
yarn add -D @souyahia/eslint-config-typescript
```

Until ESlint flat config is implemented (_see the note below_), you will also need to install the required peer
dependencies.

# How to Use

To extend this config, simply place the following snipplet in your `.eslintrc.js` to include the config :

```javascript
module.exports = {
  extends: ['@souyahia/eslint-config-typescript'],
  parserOptions: {
    project: ['./tsconfig.json'],
  },
};
```

Note that you need to manually specify the path to your tsconfig.json or the parser won't be able to locate your
Typescript config.

# A note reguarding ESlint Flat Configs

Due to the limitations of how ESlint works right now, shared ESlint configurations **need** to specify their
dependencies (such as other configs, plugins etc...) as peer dependencies. This forces developers that want to use my
config to manually download each one of my dependencies. This is obviously very cumbersome and kind of misses the whole
point of a shared config. This is even more true when it comes to monorepos.There are ways of bypassing thislimitation
([@rushstack/eslint-patch](https://www.npmjs.com/package/@rushstack/eslint-patch) etc...) but they come with their own
limitations and are considered as "patches" rather than actual features.

However, in August 2022, the ESlint team came up with
[a new config system called ESlint Flat Config](https://eslint.org/blog/2022/08/new-config-system-part-1/). This new
config system allows (among other things) for a shared config to declare its dependencies as dev (or regular)
dependencies, and include them in the config file (by importing them as a node package). This is obviously great news
for me, since it basically means all of the issues listed in the previous paragraph will be solved. However, I need to
give time to ESlint configs and plugins packages to adapt to this new config system. For instance, the
typescript-eslint package created [an issue](https://github.com/typescript-eslint/typescript-eslint/issues/5938) on the
08/11 to update their config system.

This means that for now, I need to stick with the old config and its peer dependencies, and keep an eye on the package
updates until the new ESlint config system is mature enough for us to migrate to it.

Some references to read more about this subject :

- https://github.com/eslint/eslint/issues/3458
- https://eslint.org/blog/2022/08/new-config-system-part-1/
- https://eslint.org/blog/2022/08/new-config-system-part-2/
- https://eslint.org/blog/2022/08/new-config-system-part-3/
- https://github.com/eslint/eslint/issues/13481
- https://eslint.org/docs/latest/user-guide/configuring/configuration-files-new
- https://github.com/typescript-eslint/typescript-eslint/issues/5938
npm package: @souyahia/prettier-config
Description: The base Prettier config that I use in my Node.js projects
Author: souyahia
Latest version: 1.0.1

# @monkvision/prettier-config

This package provides the base Prettier that I use throughout my Node.js projects

# Install

To install the project simply run the following command :

```shell
yarn add prettier @souyahia/prettier-config
```

# How to use

To use the Prettier config exported by this package, simply add the following line in your `package.json` :

```json
{
  "prettier": "@souyahia/prettier-config"
}
```
npm package: @souyahia/typescript-config
Description: The TSConfigs that I use in my TypeScript projects
Author: souyahia
Latest version: 1.1.3

# @souyahia/typescript-config

This package provides the TSConfgis that I use in my Typescript projects.

# Install

To install the project simply run the following command :

```shell
yarn add -D typescript @souyahia/typescript-config
```

# How to use

To use one of the Typescript config exported by this package, place the following code in your `tsconfig.json` :

```json
{
  "extends": "@souyahia/typescript-config/tsconfig.json",
  "include": ["src", "test"]
}
```

You can replace `tsconfig.json` by the name of the config file you want to use.

I also recommend using a second tsconfig file used for building your sources using the command
`tsc -p tsconfig.build.json`. The build file will specify the outDir and exclude the test files like this :

```json
{
  "extends": "./tsconfig.json",
  "compilerOptions": {
    "outDir": "dist"
  },
  "exclude": ["test"]
}
```

# Available configs

Here is a list of available Typescript config files exported by this project :

| Name                    | Usage                                         |
|-------------------------|-----------------------------------------------|
| `tsconfig.json`         | Base configuration for any typescript project |
| `tsconfig.angular.json` | Base configuration for any Angular 15 project |

# Examples
## Angular
- `tsconfig.json` :
```json
{
  "extends": "@souyahia/typescript-config/tsconfig.angular.json",
  "compilerOptions": {
    "baseUrl": "./",
    "outDir": "./dist/out-tsc",
    "paths": {
      "app/*": [
        "src/app/*"
      ]
    }
  }
}
```

- `tsconfig.app.json` :
```json
{
  "extends": "./tsconfig.json",
  "compilerOptions": {
    "outDir": "./out-tsc/app",
    "types": []
  },
  "files": [
    "src/main.ts",
    "src/polyfills.ts"
  ],
  "include": [
    "src/**/*.d.ts"
  ]
}
```

- `tsconfig.spec.json` :
```json
{
  "extends": "./tsconfig.json",
  "compilerOptions": {
    "outDir": "./out-tsc/spec",
    "types": [
      "jasmine"
    ]
  },
  "files": [
    "src/test.ts",
    "src/polyfills.ts"
  ],
  "include": [
    "src/**/*.spec.ts",
    "src/**/*.d.ts"
  ]
}
```
npm package: @sov3rain/unity-serve
Description: A lightweight, zero-dependency Node.js web server for serving Unity WebGL builds locally and across networks
Author: Sov3rain
Latest version: 1.1.0

# Unity Serve

A lightweight, zero-dependency Node.js web server specifically designed for serving Unity WebGL builds locally and across networks.

## Features

- 🚀 **Zero dependencies** - Uses only Node.js built-in modules
- 🔍 **Auto port detection** - Finds the first available port automatically
- 🌐 **Network access** - Provides local IP address for testing on other devices
- 🎮 **Unity WebGL optimized** - Includes proper MIME types and CORS headers
- 🗜️ **Compression support** - Handles both Brotli (.br) and Gzip (.gz) files
- 🎯 **Simple to use** - Just run in your WebGL build folder

## Installation

### Global Installation (Recommended)

```bash
npm install -g @sov3rain/unity-server
```

Then use anywhere:
```bash
unity-serve
```

## Usage

### Method 1: Global Command (if installed globally)

Navigate to your Unity WebGL build folder and run:
```bash
unity-serve
```

### Method 2: NPX (without installation)

```bash
cd path/to/your/unity-webgl-build
npx @sov3rain/unity-server
```

## What You'll See

When you start the server, you'll see output like this:

```
UNITY-SERVE v1.0.1

→ Local:   http://localhost:3000
→ Network: http://192.168.24.150:3000

Press Ctrl+C to stop the server
```

## Testing on Other Devices

Use the **Network URL** to test your Unity WebGL build on:
- Mobile phones
- Tablets  
- Other computers on the same network
- VR headsets with browsers

Just open the Network URL in any web browser on devices connected to the same WiFi/network.

## Unity WebGL Build Requirements

Your Unity WebGL build folder should contain:
- `index.html` (required - the server checks for this)
- Build files (`.js`, `.wasm`, `.data` files)
- Any compressed files (`.gz`, `.br`)

Typical Unity WebGL build structure:
```
your-build-folder/
├── index.html
├── Build/
│   ├── your-game.loader.js
│   ├── your-game.framework.js(.br/.gz)
│   ├── your-game.data(.br/.gz)
│   ├── your-game.wasm(.br/.gz)
│   └── your-game.symbols.json(.br/.gz)
├── TemplateData/
│   ├── favicon.ico
│   ├── fullscreen-button.png
│   ├── progress-bar-empty-dark.png
│   ├── progress-bar-full-dark.png
│   ├── unity-logo-dark.png
│   └── webgl-logo.png
└── StreamingAssets/ (if any)
```

## Troubleshooting

### "No index.html found" Error
Make sure you're running the server in the correct folder:
```bash
cd path/to/your/unity-webgl-build
# Should contain index.html
unity-serve
```

### Can't Access from Other Devices
1. **Check firewall** - Ensure your firewall allows the port
2. **Same network** - Devices must be on the same WiFi/network
3. **Use Network URL** - Use the IP address shown, not localhost

## License

MIT License - Feel free to use in your projects!
npm package: @sova-labs/sdk
Description: Sova MEV Searcher SDK for TON
Author: Sova.network
Latest version: 0.1.13

# Sova SDK

Sova SDK is a JavaScript/TypeScript library for interacting with the Sova MEV Engine and Searcher services. It provides functionalities for authentication, streaming mempool transactions, subscribing to bundles, and sending bundles.

- **Authentication**: Authenticate using your private key to obtain access and refresh tokens.
- **Streaming Mempool Transactions**: Stream transactions from the client to the Sova MEV Engine.
- **Subscribe to Bundles**: Subscribe to receive a stream of simulated and profitable bundles.
- **Send Bundles**: Send bundles to the Sova MEV Engine for processing.

## Installation
Install the package via npm:

`npm install @sova-labs/sdk`

Or using yarn:

`yarn add @sova-labs/sdk`

## Usage Guide
https://sova-network.gitbook.io/sova-labs/mev-searcher-guide/javascript-sdk

## Contributing

Contributions are welcome! Please open an issue or submit a pull request with any changes or enhancements. Follow these steps to contribute:

1. Fork the repository.
2. Create a new branch for your feature or bugfix.
3. Make your changes and commit them with clear and descriptive messages.
4. Push your changes to your fork.
5. Open a pull request to the main repository.