open-index/open-npm huggingface dataset:
npm package: @kudobuzz/kbclient
Description: Wrapper for the Kudobuzz API
Author: banphlet
Latest version: 0.0.5

# Kbjs Clients
Collection of Kudobuzz Public Client packages

[![lerna](https://img.shields.io/badge/maintained%20with-lerna-cc00ff.svg)](https://lernajs.io/)

# Setup

Kbjs uses [lerna](https://lernajs.io/) to manage packages.

- `npm install --global lerna` to install lerna globally.
- `lerna bootstrap` to resolve packages from npm registry.

## [Documentation](https://docs.kudobuzz.com)
npm package: @kudobuzz/kbjs-core
Description: Core wrapper for kudobuzz client packages
Author: Theophilus Annor
Latest version: 0.0.5

# KBJS Core
A wrapper for core Kudobuzz client utils.

## Installation

`npm i --save @kudobuzz/kbjs-core`


# Usage 

``` javascript

const kbjscore = require('@kudobuzz/kbjs-core')

const customers = kbjscore.client.get("/customers")
```

## Api 

**#client**
Basic wrapper around axios library [See](https://www.npmjs.com/package/axios)

### Usage
``` javascript

const kbjscore = require('@kudobuzz/kbjs-core')

const customers = kbjscore.client.get("/customers")
```
npm package: @kudohamu/storybook-akashic
Description: Storybook for Akashic Engine.
Author: kudohamu
Latest version: 6.3.13

# @kudohamu/storybook-akashic

[![CI](https://github.com/kudohamu/storybook-akashic/actions/workflows/ci.yml/badge.svg)](https://github.com/kudohamu/storybook-akashic/actions/workflows/ci.yml)

@kudohamu/storybook-akashic は [Storybook](https://storybook.js.org/) を使った [Akashic Engine](https://akashic-games.github.io/) のエンティティ用のUI開発環境を提供します。  
`g.E` や `g.Label` などのエンティティをエンティティ単位で視覚化し、さまざまな状態を確認しながらインタラクティブに開発できます。

![Screen Shot](https://github.com/kudohamu/storybook-akashic/blob/main/assets/screenshot.gif)  

## How to Install

```
$ npm i -D @kudohamu/storybook-akashic
```

また、利用したいAkashic Engineのバージョンが入った [akashic-engine-standalone](https://github.com/akashic-games/akashic-engine-standalone) をインストールしてください。

```
$ npm i -D @akashic/akashic-engine-standalone
```

## How to Use

### Basic Use

ミニマルな利用であれば@storybook/reactなどと全く同じ様に、「タイトルなどのメタデータ」と「エンティティの生成に必要なパラメータを受け取ってエンティティを生成して返す関数」をstoryからエクスポートするだけでStorybookに表示することができます。

```typescript
// FilledRect.stories.ts

import { Story } from '@kudohamu/storybook-akashic';

export default {
  title: 'Demo/FilledRect'
};

const Template: Story<g.FilledRectParameterObject> = (params) => {
  return new g.FilledRect({
    ...params,
    width: 200,
    height: 56,
    cssColor: 'red'
  });
};

export const Default = Template.bind({});
```

### With Assets

表示したいエンティティが画像などのアセットを使用する場合、対象のアセットIDがどのパスから取得できるかを@kudohamu/storybook-akashicに教えてあげる必要があります。  
`.storybook/preview.ts` または各storyファイルからエクスポートするparametersに、必要な[GameConfiguration](https://akashic-games.github.io/reference/akashic-engine-v3/interfaces/gameconfiguration.html)と使用するassetId(またはassetPaths)を含めることで@kudohamu/storybook-akashicがアセット情報を読み取ることができるようになります。  

```typescript
// .storybook/preview.ts

import { GameConfiguration } from '@akashic/akashic-engine-standalone';
import { StorybookAkashicParameters } from '@kudohamu/storybook-akashic';
const gameJson: GameConfiguration = require('../game.json');

export const parameters: StorybookAkashicParameters = {
  akashic: {
    assetIds: ['player', 'background'],
    configuration: gameJson
  }
};
```

また上記の情報から得られたアセットのパスにStorybookがアクセスできるようにしてください。  
これは `start-storybook` で立ち上げる際に関連するアセットをstatic filesとして指定しなければならないことを意味します。  

```json
"scripts": {
  "storybook": "start-storybook -p 6006 -s ./game"
}
```
*※ 上で指定している `game` ディレクトリはAkashic Engineで使用する `audio`, `image`, `text` などのディレクトリをまとめたディレクトリです*
  
  
Storybookをビルドするときも同様です。

```json
"scripts": {
  "build-storybook": "build-storybook -p 6006 -s ./game"
}
```

## Demo Project

利用者の理解を助けるために@kudohamu/storybook-akashicを使ったデモプロジェクトを公開しています。  
より実践的で詳細な使用方法は下記プロジェクトを参考にしてください。  

[https://github.com/kudohamu/storybook-akashic-demo](https://github.com/kudohamu/storybook-akashic-demo)

## License

本リポジトリは MIT License の元で公開されています。 詳しくは [LICENSE](https://github.com/kudohamu/storybook-akashic/blob/main/LICENSE) をご覧ください。
npm package: @kudojs/toolbox
Description: A lightweight React utility components library inspired by Solid.js. Includes components like Switch, Match, Show, Dynamic, and For — enabling expressive and declarative UI patterns in React.
Author: Ismail Salah
Latest version: 1.1.3

# @kudo/toolbox

A lightweight React utility components library inspired by Solid.js.  
Includes components like **Switch**, **Match**, **Show**, **Dynamic**, and **For** — enabling expressive and declarative UI patterns in React.

---

## ✨ Features

- 🧩 Simple `Switch` / `Match` control flow components
- 👁️ `Show` component for conditional rendering
- 🔄 `Dynamic` component for dynamic component instantiation
- 🔁 `For` component for declarative iteration
- 🪶 Small bundle size, no dependencies
- 🦄 TypeScript support

---

## 📦 Installation

```bash
npm install @kudo/toolbox
````

or

```bash
yarn add @kudo/toolbox
```

---

## 🚀 Usage

### Switch / Match

```tsx
import { Switch, Match } from '@kudo/toolbox';

function Example({ value }: { value: number }) {
  return (
    <Switch>
      <Match when={value === 1}>One</Match>
      <Match when={value === 2}>Two</Match>
      <Match when={value === 3}>Three</Match>
    </Switch>
  );
}
```

### Show

```tsx
import { Show } from '@kudo/toolbox';

function Example({ loggedIn }: { loggedIn: boolean }) {
  return (
    <Show when={loggedIn}>
      <p>Welcome back!</p>
    </Show>
  );
}
```

### Dynamic

```tsx
import { Dynamic } from '@kudo/toolbox';

const components = {
  one: () => <div>Component One</div>,
  two: () => <div>Component Two</div>,
};

function Example({ type }: { type: 'one' | 'two' }) {
  const Component = components[type];
  return <Dynamic component={Component} />;
}
```

### For

```tsx
import { For } from '@kudo/toolbox';

function Example() {
  const items = ['Apple', 'Banana', 'Cherry'];

  return (
    <For each={items}>
      {(item, index) => (
        <div key={index}>
          {index + 1}. {item}
        </div>
      )}
    </For>
  );
}
```

---

## 💻 Components API

### `<Switch>`

Renders the first `<Match>` whose `when` prop evaluates to `true`.

### `<Match>`

* **when** (boolean | ReactElement | undefined): The condition to match.

### `<Show>`

* **when** (boolean | ReactElement | undefined): The condition to show the children.

### `<Dynamic>`

* **component** (React component): The component to dynamically render.

### `<For>`

* **each** (array): The array to iterate over.
* **children** (function): A render function of the form `(item, index) => ReactNode`.

---

## 📚 License

MIT

---

## 🙏 Acknowledgements

Inspired by [Solid.js control flow components](https://www.solidjs.com/docs/latest/api#control-flow).
npm package: @kudoo/components
Description: Shared React components across Kudoo
Author: Kudoo Cloud Pty Ltd
Latest version: 2.4.2

# Overview

The `React` components are separated by our classification
* bosons
* nuclei
* atoms
* screens

Bosons are the smallest UI components we have and make up the base components of everything we do. Bosons are the lowest common denominator

Nuclei consist of a bunch of commonly used components that together form a piece of common functionality

Atoms are the building blocks of the application. They can be thought of as the Lego blocks that make up the application. The Atoms are:
* Drawer
* Footer
* HeaderBar
* NotFound
* Tabs
* Screens

# Creating a basic screen

The webapp will always consist of at least the following components
* drawer
* headerBar
* screen

```javascript
import React from 'react';
import Drawer, HeaderBar from './index';
import { BrowserRouter as Router, Route } from 'react-router-dom';

<Router>
    <Route
    render={() => (
        <Drawer
            companies={[{ id: 1, name: 'Kudoo' }, { id: 2, name: 'Facebook' }]}
            selectedCompany={{ id: 1, name: 'Kudoo', owner: true }}
        />
        <HeaderBar
            headerLabel={'Dashboard'}
            profile={{ firstName: 'John', lastName: 'Doe' }}
        />
    )}
    />
</Router>

```
npm package: @kudoo/email
Description: The Kudoo library for dealing with email. Allows adding PDF attachments and i18n of emails
Author: Kudoo Cloud Pty Ltd
Latest version: 2.1.0

# kudoo-email
The Kudoo library for dealing with email. Allows adding PDF attachments and i18n of emails

## Getting started
We use `Babel` to you'll need to have it installed globally
`npm install -g babel-cli`
We'll also need `ncp`
`npm install -g ncp`
npm package: @kudoo/graphql
Description: Graphql services and typedefs for Kudoo
Author: Kudoo Cloud Pty Ltd
Latest version: 3.0.9

# kudoo-graphql
Kudoo's shared library of GraphQL related queries and mutations

Need react and react-dom lib as we are using ract-apollo in this package.

# Development

3 things to consider
`typedefs`: These are definitions of query and mutation
`hoc` : These are mainly useful in react codebase
`services`: using which we can use skelm api in node projects

When we want to use skelm api in any node project, you need to create service for that if it doesn't exist
when we are developing mode, this changes will not be in npm package before publishing so we need to use `npm link` feature

for that
1. you need to go to `kudoo-graphql` folder and run `npm link`
2. go to hermes folder and run `npm link @kudoo/graphql` , which will create linkage to your local folder
3. now whenever you make changes in `kudoo-graphql` , you need to run `npm run build` in `kudoo-graphql` folder , which transpile latest code
npm package: @kudoo/kudoo-email
Description: The Kudoo library for dealing with email. Allows adding PDF attachments and i18n of emails
Author: Kudoo Cloud Pty Ltd
Latest version: 1.0.0

# kudoo-email
The Kudoo library for dealing with email. Allows adding PDF attachments and i18n of emails

## Getting started
We use `Babel` to you'll need to have it installed globally
`npm install -g babel-cli`
We'll also need `ncp`
`npm install -g ncp`
npm package: @kudoo/tsconfig
Description: > Shared [TypeScript config](https://www.typescriptlang.org/docs/handbook/tsconfig-json.html) for my projects
Author: Kudoo Cloud Pty Ltd
Latest version: 1.0.6

# tsconfig

> Shared [TypeScript config](https://www.typescriptlang.org/docs/handbook/tsconfig-json.html) for my projects


## Install

```
$ npm install --save-dev @kudoo/tsconfig
```


## Usage

`tsconfig.json`

```json
{
	"extends": "@kudoo/tsconfig",
}
```
## NPM scripts
It's also a good idea to include these scripts
```json
  "scripts": {
    "type-check": "tsc --noEmit",
    "type-check:watch": "npm run type-check -- --watch",
    "build": "npm run build:types && npm run build:js",
    "build:types": "tsc --emitDeclarationOnly",
    "build:js": "babel src --out-dir lib --extensions \".ts,.tsx\" --source-maps inline",
    "lint": "tslint -c tslint.json 'src/**/*.ts'",
    "start": "cd lib && node index.js"
```

## License

MIT
npm package: @kudos-protocol/keys
Description: key management for kudos
Author: @loremlabs
Latest version: 0.0.2

# Kudos Keys

Kudos Keys is a library that provides a set of functions to generate and manage keys for the Kudos ecosystem.

Generally you won't need to use this directly but it's used as part of other [@kudos-protocol](https://www.npmjs.com/search?q=%40kudos-protocol) libraries.

## Usage

```javascript

import { hexToBytes, signMessage, getKeys, normalizePrivateKey, validate } from '@kudos-protocol/keys';

// signature = '0x' + signature + recId // recId is last byte of signature
const isValid = await validate({ signature, message, { address } });

// loop through 'WALLET_SEED_' to read in keys for an address.
// WALLET_SEED_0 = walletAddress:publicKey:privateKey
const walletKeys = getKeys(address); // only use this on dev / trusted environments

```

## Logging

Set the `LOG_LEVEL=debug` environment variable to see debug logs.

Uses [@kudos-protocol/logger](https://www.npmjs.com/package/@kudos-protocol/logger).
npm package: @kudos-protocol/logging
Description: logging standardization used in the kudos protocol
Author: @loremlabs
Latest version: 0.0.4

# Logging

## Overview

This is a helper library for logging, a wrapper around [pino](https://github.com/pinojs/pino).

Likely you won't want to use this directly, but it's used as part of other [@kudos-protocol](https://www.npmjs.com/search?q=%40kudos-protocol) libraries.

## Usage

```javascript
import log from '@kudos-protocol/logging';

log.info('Hello World');
```

## Configuration

The logger can be configured by setting the following environment variables:

| Variable   | Description                       | Default |
| ---------- | --------------------------------- | ------- |
| LOG_LEVEL  | The log level.                    | info    |
| LOG_PRETTY | Whether to pretty print the logs. | false   |
npm package: @kudos-protocol/short-id
Description: base58 short id used in kudos
Author: @loremlabs
Latest version: 0.0.1

# Kudos Short ID

## Overview

This library provides a base58 encoded UUID V1 which is 22 characters long. It's used to create a unique identifier for a Kudos transaction. Under the hood it's the standard UUID V1 which is base58 encoded.

Likely you won't want to use this directly, but it's used as part of other [@kudos-protocol](https://www.npmjs.com/search?q=%40kudos-protocol) libraries.

## Usage

```javascript
import { shortID, shortIdFromUuid, uuidV1 } from '@kudos-protocol/short-id';

console.log(shortID()); // Jr9jnoTosc332G9gjcStZv
```
npm package: @kuehnelbs/node-red-contrib-nextcloud
Description: Collection of node-red nodes to download Calendars (CalDAV) and Contacts (CardDAV) and up- / download / list files (WebDAV) from / to nextcloud
Author: Torsten Kühnel
Latest version: 0.1.3

# node-red-contrib-nextcloud
Collection of node-red nodes to download Calendars (CalDAV) and Contacts
(CardDAV) and up- / download / list files (WebDAV) from / to [nextcloud](https://nextcloud.com/)

Detailed information can be found in the build in info of each node

## Installation
npm install node-red-contrib-nextcloud

### CalDAV
- based on [dav](https://github.com/lambdabaa/dav) package using CalDAV protocol
- reads all calendars and sends a message for each calendar
- reads a specified calandar if set in node properties or incoming message

### CardDAV
- based on [dav](https://github.com/lambdabaa/dav) package using CalDAV protocol
- reads all addressbooks and sends a message for each adressbook
- reads a specified addressbook if set in node properties or incoming message

### WebDAV
- based on [webdav](https://github.com/perry-mitchell/webdav-client) package using WebDAV protocol

##### Read content of a server directory
- reads content of the users root directory if no folder is specified
- reads content of a given directory specified in node properties or incoming message

##### Upload a file to a server directory
- uploads a file to nextcloud server
- absolute path of upload file can be set in node properties or incoming message
- server directory can be set in node properties or incoming message

##### Download a file from a server directory
- downloads a file from nextcloud server
- file on server can be set in node properties or incoming message
- sends file as binary buffer to the output. File can be stored using file node
npm package: @kuei/react-scripts
Description: Configuration and scripts for Create React Lib.
Latest version: 3.0.2-alpha.2

# react-scripts

This package includes scripts and configuration used by [Create React App](https://github.com/facebook/create-react-app).<br>
Please refer to its documentation:

- [Getting Started](https://facebook.github.io/create-react-app/docs/getting-started) – How to create a new app.
- [User Guide](https://facebook.github.io/create-react-app/) – How to develop apps bootstrapped with Create React App.