open-index/open-npm huggingface dataset:
npm package: @proteria/graphql-upload
Description: Middleware and an Upload scalar to add support for GraphQL multipart requests (file uploads via queries and mutations) to various Node.js GraphQL servers.
Author: alex-kinokon
Latest version: 16.0.3

# graphql-upload-cjs

![Latest upstream version](https://img.shields.io/npm/v/graphql-upload?label=latest%20upstream)
![Current upstream version](https://img.shields.io/badge/current%20upstream-v16.0.2-brightgreen)

```sh
npm install @proteria/graphql-upload
```

See [original README](https://github.com/jaydenseric/graphql-upload/blob/13fde6064e5613cfa283d07b88e1e0f2e6fe884d/readme.md) for `graphql-upload`.

## Why

[36 closed issues for "ESM"](https://github.com/jaydenseric/graphql-upload/issues?q=is%3Aissue+sort%3Aupdated-desc+esm+is%3Aclosed) in `graphql-upload` repo as of May 19, 2023.

## How

This repo just runs a script to repackage every `mjs` file in `graphql-upload` into CJS and bundle the TypeScript definitions.

## Differences

1. CommonJS.
2. No need to [configure your TypeScript](https://github.com/jaydenseric/graphql-upload/blob/e01b5d5541760d529b06c900883c5fa7febcff00/readme.md#requirements) to make it pick up the types.

## Build

```sh
pnpm install
pnpm run build
```
npm package: @protiven/react-components-lib
Description: Библиотека React компонентов
Author: Protiven
Latest version: 1.0.1

# React Components Library

Современная библиотека React компонентов, построенная с использованием TypeScript, Storybook и современных инструментов разработки.

## 🚀 Возможности

- ⚡ **TypeScript** - Полная типизация для лучшего DX
- 📚 **Storybook** - Интерактивная документация компонентов
- 🧪 **Jest + Testing Library** - Комплексное тестирование
- 📦 **Rollup** - Оптимизированная сборка
- 🎨 **CSS Modules** - Изолированные стили
- 🔧 **ESLint** - Линтинг кода
- 📖 **Автодокументация** - Автоматическая генерация документации

## 📦 Установка

```bash
npm install @protiven/react-components-lib
```

## 🎯 Использование

```tsx
import { Button, Input, Card } from '@protiven/react-components-lib';

function App() {
  return (
    <div>
      <Button variant="primary" size="large">
        Нажми меня
      </Button>
      
      <Input 
        label="Имя пользователя"
        placeholder="Введите имя..."
        error="Поле обязательно для заполнения"
      />
      
      <Card 
        header="Заголовок карточки"
        footer="Подвал карточки"
      >
        Содержимое карточки
      </Card>
    </div>
  );
}
```

## 🧩 Компоненты

### Button

Универсальная кнопка с различными вариантами стилизации.

**Пропсы:**
- `variant`: 'primary' | 'secondary' | 'outline' | 'ghost'
- `size`: 'small' | 'medium' | 'large'
- `fullWidth`: boolean
- `loading`: boolean

### Input

Поле ввода с поддержкой лейблов, ошибок и иконок.

**Пропсы:**
- `label`: string
- `error`: string
- `helperText`: string
- `variant`: 'outlined' | 'filled'
- `size`: 'small' | 'medium' | 'large'
- `fullWidth`: boolean
- `startIcon`: ReactNode
- `endIcon`: ReactNode

### Card

Контейнер для группировки связанного контента.

**Пропсы:**
- `variant`: 'elevated' | 'outlined' | 'filled'
- `padding`: 'none' | 'small' | 'medium' | 'large'
- `header`: ReactNode
- `footer`: ReactNode
- `image`: string
- `imageAlt`: string

## 🛠 Разработка

### Установка зависимостей

```bash
npm install
```

### Запуск Storybook

```bash
npm run dev
```

### Сборка библиотеки

```bash
npm run build
```

### Запуск тестов

```bash
npm test
```

### Линтинг

```bash
npm run lint
```

## 📁 Структура проекта

```
src/
├── components/
│   ├── Button/
│   │   ├── Button.tsx
│   │   ├── Button.css
│   │   ├── Button.test.tsx
│   │   ├── Button.stories.tsx
│   │   └── index.ts
│   ├── Input/
│   └── Card/
├── index.ts
└── setupTests.ts
```

## 🤝 Вклад в проект

1. Форкните репозиторий
2. Создайте ветку для новой функции (`git checkout -b feature/amazing-feature`)
3. Зафиксируйте изменения (`git commit -m 'Add amazing feature'`)
4. Отправьте в ветку (`git push origin feature/amazing-feature`)
5. Откройте Pull Request

## 📄 Лицензия

Этот проект лицензирован под MIT License - см. файл [LICENSE](LICENSE) для деталей.

## 🔗 Ссылки

- [Storybook](https://storybook.js.org/)
- [React](https://reactjs.org/)
- [TypeScript](https://www.typescriptlang.org/)
- [Rollup](https://rollupjs.org/)
- [Jest](https://jestjs.io/)
npm package: @proto-kit/deployment
Description: This package provides a suite of Dockerfiles and compose files to start protokit in a variety of settings and modes.
Latest version: 0.1.1-develop.2137

### General

This package provides a suite of Dockerfiles and compose files to start protokit
in a variety of settings and modes.

Everything is controlled via `Environments`. 
These are basically bundles of Appchains that are configured for different roles.
Every environment has a name and consists of multiple `Configurations`.

The base image built from `base/Dockerfile` executes any js file and passes in the environment and configuration name as arguments.

Configuration happens via a `.env` file that specifies a few things:
Among those are the profiles that should executed, the DB connection string, and the entrypoints for the different images


##### Currently available services:

- Persistance with 
  - Postgres (profile: `db`)
  - Redis (profiles: `db, worker`)
- Sequencer: `SEQUENCER_CONFIG` (profile: `simple-sequencer`)
- Worker: `WORKER_CONFIG` (profile: `worker`)


- Development-base: Usage for locally built starter-kit, see starter-kit documentation

### Usage

A example of how to use it with a local framework repo can be found under the package `stack`
The configuration of that setup can be found under .env

Executing it works via `docker-compose up --build` run in the `stack` package.

### Extentending deployment compose files

Option 1: Using include and specifying a exported `Environments` configuration

Option 2: Using extend and override the `cmd`

Be aware that including docker-compose files preserves their relationship in terms of relational paths, while extend does not (it behaves like copying the text into the parent file)