open-index/open-npm huggingface dataset:
npm package: @kgadzinowski/vanilla-toast
Description: Vanilla Toast is a JavaScript notification element that doesn't require any dependencies.
Author: Konrad Gadzinowski
Latest version: 1.1.0

# Vanilla Toast (vanilla-toast)
Vanilla Toast is a tiny, yet powerful JavaScript notification element that doesn't require any dependencies.  

## Demo
[Live Demo](https://konradg.com/vanilla-toast/demo/index.html)  
Demo application can be found in `/demo` folder.  

It shows all use cases.

## Suggested Dependencies For Additional Support
This element is using pointer events. As of today not all browser support this feature.  
[Browser support](http://caniuse.com/#search=pointer%20events)  
  
It might be necessary for you to use [Pointer Events Polyfill](https://github.com/jquery/PEP)  

## To Install With Bower
To use this element with Bower dependency manager, run:  
`bower install vanilla-toast --save`  

## How To Develop
In order to develop this element, you need to have Node.js installed.  

1. Install all development dependencies using command `npm install`.
2. Start watching TypeScript and SCSS changes with `gulp watch-all`.
3. Edit!  

On Linux systems, if you get error: `Error: watch ... ENOSPC` when executing `gulp watch-all`, then run `echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p` to fix it.

## How To Create Production Release
1. Execute `gulp prod`.
2. Production files can be found in `/dist` folder.
npm package: @kgan/create-kgan-react-router-app
Description: A React Router Starter from scratch using TypeScript, Webpack, Jest, React Testing Library, Storybook, Prettier, ESLint, and GitHub Actions.
Author: KGAN
Latest version: 0.0.3

# Welcome to React Router!

A modern, production-ready template for building full-stack React applications using React Router.

[![Open in StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](https://stackblitz.com/github/remix-run/react-router-templates/tree/main/default)

## Features

- 🚀 Server-side rendering
- ⚡️ Hot Module Replacement (HMR)
- 📦 Asset bundling and optimization
- 🔄 Data loading and mutations
- 🔒 TypeScript by default
- 🎉 TailwindCSS for styling
- 📖 [React Router docs](https://reactrouter.com/)

## Getting Started

### Installation

Install the dependencies:

```bash
npm install
```

### Development

Start the development server with HMR:

```bash
npm run dev
```

Your application will be available at `http://localhost:5173`.

## Building for Production

Create a production build:

```bash
npm run build
```

## Deployment

### Docker Deployment

To build and run using Docker:

```bash
docker build -t my-app .

# Run the container
docker run -p 3000:3000 my-app
```

The containerized application can be deployed to any platform that supports Docker, including:

- AWS ECS
- Google Cloud Run
- Azure Container Apps
- Digital Ocean App Platform
- Fly.io
- Railway

### DIY Deployment

If you're familiar with deploying Node applications, the built-in app server is production-ready.

Make sure to deploy the output of `npm run build`

```
├── package.json
├── package-lock.json (or pnpm-lock.yaml, or bun.lockb)
├── build/
│   ├── client/    # Static assets
│   └── server/    # Server-side code
```

## Styling

This template comes with [Tailwind CSS](https://tailwindcss.com/) already configured for a simple default starting experience. You can use whatever CSS framework you prefer.

---

Built with ❤️ using React Router.
npm package: @kgan/ui
Description: A React component library for building modern web applications using Tailwind CSS.
Author: KGAN
Latest version: 1.0.17

# @kgan/ui

A modern, flexible React UI component library based on the **Atomic Design** methodology, styled with **Tailwind CSS**.

> Build scalable and maintainable UI systems with a clear separation between atoms, molecules, and organisms.

---

## 📦 Installation

```bash
npm install @kgan/ui
# or
pnpm add @kgan/ui
# or
yarn add @kgan/ui
```
npm package: @kgateway/kbeacon
Description: This plugin lets you connect to kbeacon devices
Author: biTid
Latest version: 0.0.2

# @kgateway/kbeacon

This plugin lets you connect to kbeacon devices

## Install

```bash
npm install @kgateway/kbeacon
npx cap sync
```

## API

<docgen-index>

* [`echo(...)`](#echo)

</docgen-index>

<docgen-api>
<!--Update the source file JSDoc comments and rerun docgen to update the docs below-->

### echo(...)

```typescript
echo(options: { value: string; }) => any
```

| Param         | Type                            |
| ------------- | ------------------------------- |
| **`options`** | <code>{ value: string; }</code> |

**Returns:** <code>any</code>

--------------------

</docgen-api>
npm package: @kgcdream2019/v1-core
Description: 🎛 Core contracts for the JulSwap protocol
Latest version: 1.0.1

# SwapLiquidity 

https://swapliquidity.org. Feel free to read the code. More details coming soon.

## Deployed Contracts / Hash


- (Uni|SwapLiquidity)BSCswapFactory - https://bscscan.com/address/0x553990F2CBA90272390f62C5BDb1681fFc899675
- (Uni|SwapLiquidity)BSCswapRouter  - https://bscscan.com/address/0xbd67d157502A23309Db761c41965600c2Ec788b2
- (Uni|SwapLiquidity)BSCswapPair init code hash - `b1e98e21a5335633815a8cfb3b580071c2e4561c50afd57a8746def9ed890b18`


## License
 GPL
npm package: @kgierke/formkit-inputs
Description: Collection of FormKit inputs.
Author: Kurt Gierke
Latest version: 0.3.5

# FormKit Inputs

A collection of some additional input types to use with [FormKit](https://formkit.com). Most of these additional input types are based on my personal needs, but feel free to submit PRs to add more.

## How to use

### Install the package

In order to use this package you have to install it first, use your preferred package manager to install it.

```bash
npm install @kgierke/formkit-inputs
```

### Setup the package

After you've installed the package it's time to set it up. The minimal setup requires you only to import the `createFormKitInputsPlugin` function and use the resulting output as plugin in your FormKit configuration. Below is an example of the minimal setup.

```ts
import createApp from "vue";
import App from "./App.vue";
import { defaultConfig, plugin } from "@formkit/vue";
import { createFormKitInputsPlugin } from "@kgierke/formkit-inputs";

const formKitInputPlugin = createFormKitInputsPlugin();

const app = createApp(App);
app
  .use(
    plugin,
    defaultConfig({
      plugins: [formKitInputPlugin],
    })
  )
  .mount("#app");
```

### Passing options

The `createFormKitInputsPlugin` function accepts an optional `options` argument. The following options are available:

```ts
{
    /**
     * To use the image input type with an automatic upload function
     * you have to pass an uploadHandler function.
     * This can also be passed as a property to the `image` input type.
     *
     * The uploadHandler receives the HTML5 `File` object
     * as first argument and expects an src string as return value.
     */
    uploadHandler: (file: File) => Promise<string> | string,
}
```

## Included Inputs

### Image

The `image` input type is an alternative to the `file` input type. It allows you to upload images and have a preview directly in the form. It also allows you to individually add and remove images (Possible with the `multiple` property). It is also possible to directly upload images to your server once they are selected and block the form from submitting until the upload is finished. To do so you have to pass an uploadHandler function as property or through the global configuration. The uploadHandler receives the HTML5 `File` object as first argument and expects an src string as return value.

```vue
<template>
  <FormKit type="form">
    <FormKit
      type="image"
      name="image"
      label="Image"
      multiple
      uploadHandler="uploadHandler"
    />
  </FormKit>
</template>

<script setup lang="ts">
import { FormKit } from "@formkit/vue";

const uploadHandler = async (file: File) => {
  const formData = new FormData();
  formData.append("file", file);

  const response = await fetch("/upload", {
    method: "POST",
    body: formData,
  });

  return response.url;
};
</script>
```
npm package: @kgilden/fullcalendar-vue
Description: Kristen Gilden's fork of the official FullCalendar component for Vue
Latest version: 5.3.1-1
Deprecated: Changes merged to upstream, this is obsolete.


# FullCalendar Vue Component [![Build Status](https://travis-ci.com/fullcalendar/fullcalendar-vue.svg?branch=master)](https://travis-ci.com/fullcalendar/fullcalendar-vue)

This project provides an official Vue component for FullCalendar, with all the same setting.

- [FullCalendar Vue Component Docs](https://fullcalendar.io/docs/vue)
- [Example Project](https://github.com/fullcalendar/fullcalendar-example-projects/tree/master/vue)
- [Contributor Guide](CONTRIBUTORS.md)
npm package: @kgn-dkau2mation/node-red-contrib-azure-iot-device
Description: Node-RED node to connect to the Azure IoT platform as a device.
Latest version: 0.3.8

# Azure IoT Device Node-RED node
The Azure IoT Device Node-RED node is a node that can be used to connect Node-RED to the Azure IoT platform. It can connect to Azure IoT Hub, Azure IoT Central, and use Azure IoT Edge as a transparant gateway. The node has been created to support the different attestation methods (SAS, X.509) as well as use Azure Device Provisioning Service. The node has been developed using the [Azure IoT Node.js SDK](https://github.com/Azure/azure-iot-sdk-node/).

The Azure IoT Device node represents a **single device** on the Azure IoT platform. 

> NB: It is our assumption that you have a basic understanding of [Node-RED](https://nodered.org/) and the [Azure IoT platform](https://azure.microsoft.com/en-us/product-categories/iot/).

## Deploy the Azure Device node
In the [deploy](https://github.com/iotblackbelt/node-red-contrib-azure-iot-device/blob/master/DEPLOY.md) document we describe how to deploy the node to Node-RED.

## Configure an Azure IoT Device node
In the [configure](https://github.com/iotblackbelt/node-red-contrib-azure-iot-device/blob/master/CONFIGURE.md) document we describe how to setup an individual Azure IoT Device node.

## Use an Azure IoT Device node
In the [use](https://github.com/iotblackbelt/node-red-contrib-azure-iot-device/blob/master/USE.md) document we describe how to use the Azure IoT Device node to interact with the Azure IoT platform.
- sending telemetry
- receiving and responding to commands
- receiving desired properties
- updating reported properties
- receiving C2D messages

## Resilience
The node is developed to resist network loss. If there is no connectivity, the node will try to re-establish a device connection based on the set retry interval. The node doesn't store and forward. All message and properties sent during a loss of connectivity, will be lost.
npm package: @kgnfth/renovate-config-kgnfth
Description: kgnfth presets for Renovate
Latest version: 0.0.5

# Renovate Pixelphoto Configs

Pixelphoto presets for [Renovate](https://github.com/singapore/renovate) tool.

## Usage

Add this into `renovate.json`:

```json
{
  "extends": ["@pixelphoto"]
}
```

## Useful Links

- [Configuration Options](https://renovatebot.com/docs/configuration-options)
- [Renovatebot Presets](https://github.com/renovatebot/presets/tree/master/packages)