open-index/open-npm huggingface dataset:
npm package: @kody-ade/kody-engine
Description: Kody CI/CD pipeline engine — multi-agent pipeline for GitHub repos
Latest version: 0.1.7
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# @kody-ade/kody-engine

Multi-agent CI/CD pipeline engine that converts GitHub issues into pull requests.

## Quick Start

```bash
# Initialize Kody in your repo
npx @kody-ade/kody-engine init
```

This sets up:

- `.github/workflows/kody.yml` — GitHub Actions workflow
- `.opencode/` — Agent prompt definitions
- `kody.config.json` — Pipeline configuration

## Setup

1. Run `npx @kody-ade/kody-engine init` in your repo
2. Edit `kody.config.json` with your repo details
3. Add LLM API keys as GitHub repo secrets (e.g., `MINIMAX_API_KEY`)
4. Commit and push the workflow file
5. Comment `@kody` on any issue to run the pipeline

## Commands

```bash
# Initialize in target repo
kody-engine init [--force] [--workflow-only]

# Run pipeline (used by CI workflow)
kody-engine run

# CI helper commands
kody-engine parse-safety
kody-engine parse-inputs
kody-engine checkout-branch
```

## Usage on GitHub Issues

```
@kody                     # Full pipeline (spec + implementation)
@kody spec                # Analyze and spec only
@kody impl                # Implementation only
@kody rerun --from build  # Resume from stage
@kody approve             # Approve paused gate
```

## Configuration

`kody.config.json`:

```json
{
  "quality": {
    "typecheck": "pnpm tsc --noEmit",
    "lint": "pnpm lint",
    "testUnit": "pnpm test:unit"
  },
  "git": { "defaultBranch": "dev" },
  "github": { "owner": "your-org", "repo": "your-repo" }
}
```

## Required Secrets

| Secret            | Purpose                                                                   |
| ----------------- | ------------------------------------------------------------------------- |
| `MINIMAX_API_KEY` | LLM provider (or `OPENAI_API_KEY`, `ANTHROPIC_API_KEY`, `GEMINI_API_KEY`) |
| `GH_PAT`          | Optional: cross-repo operations                                           |

## License

MIT
npm package: @kodyl/css-modules-typescript-loader
Description: Webpack loader to create TypeScript declarations for CSS Modules
Author: SEEK
Latest version: 4.1.2

[![Build Status](https://img.shields.io/travis/seek-oss/css-modules-typescript-loader/master.svg?style=flat-square)](http://travis-ci.org/seek-oss/css-modules-typescript-loader) [![npm](https://img.shields.io/npm/v/css-modules-typescript-loader.svg?style=flat-square)](https://www.npmjs.com/package/css-modules-typescript-loader) [![semantic-release](https://img.shields.io/badge/%20%20%F0%9F%93%A6%F0%9F%9A%80-semantic--release-e10079.svg?style=flat-square)](https://github.com/semantic-release/semantic-release) [![Commitizen friendly](https://img.shields.io/badge/commitizen-friendly-brightgreen.svg?style=flat-square)](http://commitizen.github.io/cz-cli/)

# css-modules-typescript-loader

[Webpack](https://webpack.js.org/) loader to create [TypeScript](https://www.typescriptlang.org/) declarations for [CSS Modules](https://github.com/css-modules/css-modules).

Emits TypeScript declaration files matching your CSS Modules in the same location as your source files, e.g. `src/Component.css` will generate `src/Component.css.d.ts`.

## Why?

There are currently a lot of [solutions to this problem](https://www.npmjs.com/search?q=css%20modules%20typescript%20loader). However, this package differs in the following ways:

- Encourages generated TypeScript declarations to be checked into source control, which allows `webpack` and `tsc` commands to be run in parallel in CI.

- Ensures committed TypeScript declarations are in sync with the code that generated them via the [`verify` mode](#verify-mode).

## Usage

Place `css-modules-typescript-loader` directly after `css-loader` in your webpack config.

```js
module.exports = {
  module: {
    rules: [
      {
        test: /\.css$/,
        use: [
          'css-modules-typescript-loader',
          {
            loader: 'css-loader',
            options: {
              modules: true
            }
          }
        ]
      }
    ]
  }
};
```

### Verify Mode

Since the TypeScript declarations are generated by `webpack`, they may potentially be out of date by the time you run `tsc`. To ensure your types are up to date, you can run the loader in `verify` mode, which is particularly useful in CI.

For example:

```js
{
  loader: 'css-modules-typescript-loader',
  options: {
    mode: process.env.CI ? 'verify' : 'emit'
  }
}
```

Instead of emitting new TypeScript declarations, this will throw an error if a generated declaration doesn't match the committed one. This allows `tsc` and `webpack` to run in parallel in CI, if desired.

This workflow is similar to using the [Prettier](https://github.com/prettier/prettier) [`--list-different` option](https://prettier.io/docs/en/cli.html#list-different).

## With Thanks

This package borrows heavily from [typings-for-css-modules-loader](https://github.com/Jimdo/typings-for-css-modules-loader).

## License

MIT.
npm package: @koemi.moe!/revolt.js
Description: **revolt.js** is a direct implementation of the entire Revolt API and provides a way to authenticate and start communicating with Revolt servers.
Author: Paul Makles
Latest version: 5.1.0-alpha.6

# This is a fork of revolt.js which is used on koemi.moe

**revolt.js** is a direct implementation of the entire Revolt API and provides a way to authenticate and start communicating with Revolt servers.

## Example Usage

```typescript
let client = new Client();

client.on('ready', async () =>
    console.info(`Logged in as ${client.user!.username}!`)
);

client.on('message', async message => {
    if (message.content === 'sus') {
        message.channel!.sendMessage('sus!');
    }
});

// To login as a bot:
client.loginBot('..');

// To login as a user,
// either create a new session:
client.login({ email: '..', password: '..' });

// Or use an existing session:
client.useExistingSession({ token: '..' });
```

## MobX

MobX is used behind the scenes so you can subscribe to any change as you normally would, e.g. with `mobx-react(-lite)` or mobx's utility functions.

```typescript
import { autorun } from 'mobx';

[..]

client.once('ready', () => {
    autorun(() => {
        console.log(`Current username is ${client.user!.username}!`);
    });
});
```