open-index/open-npm huggingface dataset:
npm package: @gecsevar.hu/gecsevar-formik-fields
Description: [![npm version](https://badge.fury.io/js/@gecsevar.hu%2Fgecsevar-formik-fields.svg)](https://badge.fury.io/js/@gecsevar.hu%2Fgecsevar-formik-fields)
Author: AstrA
Latest version: 0.1.4-alpha-8

[![npm version](https://badge.fury.io/js/@gecsevar.hu%2Fgecsevar-formik-fields.svg)](https://badge.fury.io/js/@gecsevar.hu%2Fgecsevar-formik-fields)

[![https://nodei.co/npm/@gecsevar.hu/gecsevar-formik-fields.png?downloads=true&downloadRank=true&stars=true](https://nodei.co/npm/@gecsevar.hu/gecsevar-formik-fields.png?downloads=true&downloadRank=true&stars=true)](https://www.npmjs.com/package/@gecsevar.hu/gecsevar-formik-fields)

# Getting Started with GecseVa'r Components

You may start your form with Formik. You may find MUI nice. You also look around and import Yup.

Well then, this is my answer! 
Text, Select, Select with items, Date, Time and so...

More code examples at
https://gecsevar.hu

(oh, the stuff is free, please give star and share if you like it)
npm package: @gecugamo/web-component-lit
Description: Webcomponent web-component-lit following open-wc recommendations
Author: web-component-lit
Latest version: 0.0.2

# \<web-component-lit>

This webcomponent follows the [open-wc](https://github.com/open-wc/open-wc) recommendation.

## Installation

```bash
npm i web-component-lit
```

## Usage

```html
<script type="module">
  import 'web-component-lit/web-component-lit.js';
</script>

<web-component-lit></web-component-lit>
```

## Linting and formatting

To scan the project for linting and formatting errors, run

```bash
npm run lint
```

To automatically fix linting and formatting errors, run

```bash
npm run format
```

## Testing with Web Test Runner

To execute a single test run:

```bash
npm run test
```

To run the tests in interactive watch mode run:

```bash
npm run test:watch
```

## Demoing with Storybook

To run a local instance of Storybook for your component, run

```bash
npm run storybook
```

To build a production version of Storybook, run

```bash
npm run storybook:build
```


## Tooling configs

For most of the tools, the configuration is in the `package.json` to reduce the amount of files in your project.

If you customize the configuration a lot, you can consider moving them to individual files.

## Local Demo with `web-dev-server`

```bash
npm start
```

To run a local development server that serves the basic demo located in `demo/index.html`
npm package: @gecut/lit-helper
Description: <!-- TODO: Write a Description -->
Author: S. MohammadMahdi Zamanian
Latest version: 2.4.7

# Gecut Data Manager

<!-- TODO: Write a Description -->

## Receiver Concept

receiver of data and cache on memory ram and update

## Sender Concept

sender of data and update dependencies data, for example when create new todo, should update todo list data

# How can i use ?

step by step to use `@gecut/data-manager`

## First Step

define type of receivers and senders

```ts
declare global {
  interface GecutReceiverServices {
    readonly 'todo-storage': TodoInterface[];
  }
  interface GecutSenderServices {
    readonly 'new-todo': TodoInterface;
  }
}
```

## Second Step

define dataManager from a new instance of `DataManager` class

```ts
const dataManager = new DataManager(
  {
    'todo-storage': {
      receiverFunction() {
        // receive todo-storage data and return
        return api.storage.query();
      },
    },
  },
  {
    'new-todo': {
      // when send data update todo-storage
      dependencies: ['todo-storage'],
      async senderFunction(newTodo) {
        // send new todo data to back-end
        await api.new.mutate(newTodo);
      },
    },
  },
);
```

## Third Step

```ts
// define this in Component Class and use
// receiver decorator has autoUpdate (automatic requestUpdate)
@receiver('todo-storage', dataManager)
todoStorage!: TodoInterface[];
```

## Fourth Step

```ts
// use this for send data
dataManager.senders['new-todo']?.send({
  status: true,
  message: textInputValue,
});
```
npm package: @gecut/mixins
Description: A tiny, TypeScript-powered package of hyper-fast LitElement mixins. Enhance your web components with swift, type-safe functionality that’s easy to integrate.
Author: S. MohammadMahdi Zamanian
Latest version: 2.2.4

# ui-mixins

This library was generated with [Nx](https://nx.dev).

## Building

Run `nx build ui-mixins` to build the library.

## Running unit tests

Run `nx test ui-mixins` to execute the unit tests via [Jest](https://jestjs.io).
npm package: @gedai/nestjs-core
Description: Core component for the gedai project
Author: gm50x
Latest version: 0.0.6

## Description

Seamless asynchronous local storage management using the NodeJS Async Local Storage. This package is designed as a core component for the `gedai` project, and offers plug-and-play functionality, empowering developers to effortlessly integrate asynchronous local storage into their applications.

## Getting Started

### Step 1: Installation

Install the necessary packages with your favorite Package Manager.

```bash
$ npm install @gedai/core
```

### Step 2: Configuration Setup

In your `app.module.ts` import `ContextModule` and set it up.

```typescript
// app.module.ts
import { ContextModule } from '@gedai/core';
import { Module } from '@nestjs/common';
import { randomUUID } from 'crypto';
import { AppController } from './app.controller';
import { AppService } from './app.service';

@Module({
  imports: [
    // Setup Context Module Here
    ContextModule.forRoot({}),
  ],
  controllers: [AppController],
  providers: [AppService],
})
export class AppModule {}
```

In `main.ts` import the apply the required configuration with `configureContextWrapper`.

```typescript
// main.ts
import { configureContextWrappers } from '@gedai/core';
import { NestFactory } from '@nestjs/core';
import { AppModule } from './app.module';

async function bootstrap() {
  const app = await NestFactory.create(AppModule)
    // Setup Context Wrappers Here
    .then(configureContextWrappers);

  await app.listen(3000);
}
bootstrap();
```

## Step 3: Usage

In your services, add `ContextService` as an injectable dependency.

```typescript
// app.service.ts
import { ContextService } from '@gedai/core';
import { Injectable } from '@nestjs/common';

@Injectable()
export class AppService {
  // Injected here
  constructor(private readonly context: ContextService) {}

  getHello(): string {
    // Recover any previously set property
    const contextId = this.context.getId();
    return `[${contextId}]: Hello World!`;
  }
}
```

## Important Consideration Regarding AsyncLocalStorage and Continuation Passing Style

Implementing continuation passing style introduces complexity to systems. While it's a viable method for data sharing across layers and components, exercising caution is paramount. It's remarkably easy to lose oversight of stored data within the context, potentially leading to bugs or leaks.

### Potential Use Cases:

- **Tracking Execution Context**: Utilize to share a traceId throughout the request lifecycle, facilitating seamless monitoring and debugging.
- **Automatically Managing Database Transactions**: Implement for streamlined transaction handling, ensuring data integrity and consistency. Ability to handle the transactions without touching the business layers.
- **Tracking Tenant Shard ID**: Employ for efficient tracking and management of tenant-specific data shards, enhancing multi-tenancy support and scalability without having to pass properties everywhere in your code.

## License

Gedai is [MIT licensed](LICENSE).
npm package: @gedai/nestjs-tactical-design
Description: Domain Driven Design and CQRS abstractions for gedai project
Author: gm50x
Latest version: 0.0.3

## Description

Utilities package for working with Domain Driven Design and CQRS in NestJS. This package offers abstractions and dedicated implementations need to be installed together.

## Installation

```bash
$ npm install @gedai/nestjs-tactical-design
```

## Getting Started:

TODO: WORK IN PROGRESS

## License

Gedai is [MIT licensed](LICENSE).
npm package: @gedai/nestjs-tactical-design-amqp
Description: Domain Driven Design and CQRS AMQP for gedai project
Author: gm50x
Latest version: 0.0.3

## Description

This package extends @gedai/nestjs-tactical-design by implementing concrete event publishing integration with RabbitMQ via AMQP. In order for this package to work you must import `@gedai/nestjs-amqp` package.

## Installation

```bash
$ npm install @gedai/nestjs-tactical-design @gedai/nestjs-amqp @gedai/nestjs-tactical-design-amqp
```

## License

Gedai is [MIT licensed](LICENSE).
npm package: @gedai/nestjs-tactical-design-mongoose
Description: Domain Driven Design and CQRS Mongoose for gedai project
Author: gm50x
Latest version: 0.0.3

## Description

This package extends @gedai/nestjs-tactical-design by implementing concrete data persistence with Mongoose. It exposes the base Repository class for mongoose implementations that should be extended in services for persistence. It also provides concrete implementation of Transactional decorator for usage with mongoose and the mongoose repository.

## Installation

```bash
$ npm install @gedai/nestjs-tactical-design @gedai/nestjs-tactical-design-mongoose @nestjs/mongoose mongoose
```

## License

Gedai is [MIT licensed](LICENSE).
npm package: @gedasx/rating-stars-component
Description: Interactive Angular component for displaying star ratings.  Component works for all Angular versions from 4 to 16.
Latest version: 0.0.11

## rating-stars-component

Interactive Angular component for displaying star ratings. 
Component works for all Angular versions from 4 to 16.

## Demo

[Demo rating-stars-component](https://stackblitz.com/~/github.com/neslibinas/demo-gedasx-rating-stars-component)

## Installation
- `npm i @gedasx/rating-stars-component`
- Edit your app.module file:

```
...
import { StarRatingLibraryModule } from '@gedasx/rating-stars-component';

@NgModule({
  ...
  imports: [
    ...
    StarRatingLibraryModule
  ],
  ...
})
```


## Usage

**Inputs**
- `size` [integer] - size of start in pixels (default size - 20px)
- `initFilledStars` [0 | 1 | 2 | 3 | 4 | 5] - initial number of prefilled stars (default 2)
- `disabled` [boolean] - determines whether component is read-only (default false)

**Events**
- `numberOfStartsEvent` [EventEmitter] - provides rating value when user clicks on star


## Examples
Default values:
```
<rating-stars-component></rating-stars-component>
```

Read-only mode:
```
<rating-stars-component [disabled]="true"></rating-stars-component>
```

Size of stars 30px, click on start action calls clickStar method and emits rating number:
```
<rating-stars-component [starSize]="30" (numberOfStartsEvent)="clickStar($event)"></rating-stars-component>
```


## License

[MIT](https://github.com/neslibinas/my-workspace/blob/master/projects/my-library/LICENSE)
npm package: @gedatou/ui
Description: A starter for creating a TypeScript package.
Author: ge Datou
Latest version: 0.0.14

# tsdown-starter

A starter for creating a TypeScript package.

## Development

- Install dependencies:

```bash
vp install
```

- Run the unit tests:

```bash
vp run --filter ./packages/ui test
```

- Build the library:

```bash
vp run --filter ./packages/ui build
```
npm package: @gedeagas/react-native-signin-with-apple
Description: React Native Sign In With Apple
Author: Agastya Darma Laksana
Latest version: 1.1.1


# react-native-sign-in-with-apple

## Getting started

`$ npm install react-native-sign-in-with-apple --save`

### Mostly automatic installation

`$ react-native link react-native-sign-in-with-apple`

### Manual installation


#### iOS

1. In XCode, in the project navigator, right click `Libraries` ➜ `Add Files to [your project's name]`
2. Go to `node_modules` ➜ `react-native-sign-in-with-apple` and add `RNSignInWithApple.xcodeproj`
3. In XCode, in the project navigator, select your project. Add `libRNSignInWithApple.a` to your project's `Build Phases` ➜ `Link Binary With Libraries`
4. Run your project (`Cmd+R`)<

#### Android

1. Open up `android/app/src/main/java/[...]/MainActivity.java`
  - Add `import com.reactlibrary.RNSignInWithApplePackage;` to the imports at the top of the file
  - Add `new RNSignInWithApplePackage()` to the list returned by the `getPackages()` method
2. Append the following lines to `android/settings.gradle`:
  	```
  	include ':react-native-sign-in-with-apple'
  	project(':react-native-sign-in-with-apple').projectDir = new File(rootProject.projectDir, 	'../node_modules/react-native-sign-in-with-apple/android')
  	```
3. Insert the following lines inside the dependencies block in `android/app/build.gradle`:
  	```
      compile project(':react-native-sign-in-with-apple')
  	```

#### Windows
[Read it! :D](https://github.com/ReactWindows/react-native)

1. In Visual Studio add the `RNSignInWithApple.sln` in `node_modules/react-native-sign-in-with-apple/windows/RNSignInWithApple.sln` folder to their solution, reference from their app.
2. Open up your `MainPage.cs` app
  - Add `using Sign.In.With.Apple.RNSignInWithApple;` to the usings at the top of the file
  - Add `new RNSignInWithApplePackage()` to the `List<IReactPackage>` returned by the `Packages` method


## Usage
```javascript
import RNSignInWithApple from 'react-native-sign-in-with-apple';

// TODO: What to do with the module?
RNSignInWithApple;
```
npm package: @gedeonix/diagram-sentences
Description: Library for presenting sentence diagrams (very early alpha).
Author: Przemysław Sołtan
Latest version: 0.0.2

# Gedeonix Diagram Sentences Lib (d3 + svg)

Library for presenting sentence diagrams (very early alpha).

## Demo
 Simple demo in ./public/diagram.html file.

 ![demo screen](./public/images/demo.png)
 
## Resource
- https://en.wikipedia.org/wiki/Sentence_diagram

### SBL Fonts
Fonts are not a direct part of the library, they were used only for the demo code.

The project (non-profit) uses fonts from www.sbl-site.org
under license
> Fonts SBL fonts are made available without cost to individual scholars for non-profit use.
>
> www.sbl-site.org/educational/biblicalfonts.aspx
npm package: @gedeonix/greek
Description: Library of simple tools to support work on text in Greek (very early alpha)
Author: Przemysław Sołtan
Latest version: 0.0.2

# Gedeonix Greek Lib (transcription of Greek into Polish)

Library of simple tools to support work on text in Greek (very early alpha)

## Demo
 Simple demo in ./public/keyboard.html file.
 
![demo screen](./public/images/demo.png)
  
## Resource

### Unicode
- https://en.wikipedia.org/wiki/Unicode_and_HTML_for_the_Hebrew_alphabet
- https://en.wikipedia.org/wiki/Greek_diacritics
- https://en.wikipedia.org/wiki/Latin_script_in_Unicode

### SBL Fonts
Fonts are not a direct part of the library, they were used only for the demo code.

The project (non-profit) uses fonts from www.sbl-site.org
under license
> Fonts SBL fonts are made available without cost to individual scholars for non-profit use.
>
> www.sbl-site.org/educational/biblicalfonts.aspx

- manual https://www.sbl-site.org/Fonts/SBLHebrewManualv1.5.pdf
npm package: @gedhean/rollup-plugin-chrome-extension
Description: Build Chrome Extensions with this Rollup plugin.
Author: Jack and Amy Steam
Latest version: 3.6.7

# [rollup-plugin-chrome-extension](https://www.extend-chrome.dev/rollup-plugin)

[![npm (scoped)](https://img.shields.io/npm/v/rollup-plugin-chrome-extension.svg)](https://www.npmjs.com/package/rollup-plugin-chrome-extension)
[![GitHub last commit](https://img.shields.io/github/last-commit/extend-chrome/rollup-plugin-chrome-extension.svg?logo=github)](https://github.com/extend-chrome/rollup-plugin-chrome-extension)
![GitHub action badge](https://github.com/extend-chrome/rollup-plugin-chrome-extension/actions/workflows/main.yml/badge.svg)
[![TypeScript Declarations Included](https://img.shields.io/badge/types-TypeScript-informational)](#typescript)

<a href="https://www.extend-chrome.dev/rollup-plugin" rel="noopener">
  <img width=200px height=200px src="https://imgur.com/wEXnCYK.png" alt="rollup-plugin-chrome-extension logo"></a>

The bundler configuration for a Chrome Extension can be pretty
complex.

Use `manifest.json` as the input. Every file in the manifest will
be bundled or copied to the output folder.

RPCE simplifies project config and supports many of Vite's
features in the Chrome Extension evironment, including HMR.

## Vite Usage

Vite support is in beta! Check out this
[90 second getting started guide]().

```sh
npm i rollup-plugin-chrome-extension@beta -D
```

```javascript
// vite.config.js

import { defineConfig } from 'vite'
import react from '@vitejs/plugin-react'
import { chromeExtension } from 'rollup-plugin-chrome-extension'

export default defineConfig({
  plugins: [react(), chromeExtension()],
})
```

Just add new features to your manifest and RPCE does the rest.

## [Documentation for v3](https://www.extend-chrome.dev/rollup-plugin)

We have
[v3 boilerplates](https://www.extend-chrome.dev/rollup-plugin#chrome-extension-boilerplates)
for
[React JavaScript](https://github.com/extend-chrome/js-react-boilerplate),
[React TypeScript](https://github.com/extend-chrome/ts-react-boilerplate)
and
[Svelte](https://github.com/kyrelldixon/svelte-tailwind-extension-boilerplate),
as well as
[instructions](https://www.extend-chrome.dev/rollup-plugin#usage)
for setting up your own project.

See the
[documentation](https://www.extend-chrome.dev/rollup-plugin) for
usage and how to get started.

## Contributing

Your help is super welcome!

🎯 Ongoing developement is for v4+ only.

👀 Be sure to take a look at the issues before starting to work
on a new feature.

🙏 Please update the tests to cover bug fixes or new features.

📕 Documentation for v4 has not yet begun, but you can open an
issue for help.

✨ If you enjoy using RPCE, please help spread the word!

## Development

Our preferred package manager is [pnpm](https://pnpm.io/), but
npm or Yarn should work.

If you're using VSCode you can run the default build task
(Ctrl+Shift+B or ⇧⌘B for Mac) to start building and type
checking.

## Change my by Jedi

- Fixed [Issue 110](https://github.com/extend-chrome/rollup-plugin-chrome-extension/issues/110): <all_urls> match patterns are not handled properly;
npm package: @gedhean/rollup-plugin-dotenv
Description: ## Installation
Author: Mateusz Burzyński
Latest version: 0.4.0

# rollup-plugin-dotenv

## Installation

```console
npm install rollup-plugin-dotenv
```

## Usage

Create a `rollup.config.js` [configuration file](https://www.rollupjs.org/guide/en/#configuration-files) and import the plugin:

```js
import dotenv from "rollup-plugin-dotenv"

export default {
  input: "src/index.js",
  output: [
    dir: "dist/build"
  ],
  plugins: [
    dotenv()
  ]
}
```

create your `.env` file in the root of your project.

```bash
# .env
FOO=bar
```

so you can use FOO in your javascript files.

```js
// src/index.js
console.log(process.env.FOO)
```

your env variables will be replaced by their values in your bundled file.

```js
// dist/build/index.js
console.log('bar')
```

if you want to know more about the principle and restrictions of replacement, please read [@rollup/plugin-replace](https://www.npmjs.com/package/@rollup/plugin-replace) notes.

## Options

You can specify the options below.

### `cwd`

Type: `String`
Default: `"."`

directory in which to search for env files.

### `envKey`

Type: `String`
Default: `"NODE_ENV"`

key used to search for .env files by node environment

Rollup will merge env vars located at

```
[
  `.env.${process.env[envKey]}.local`,
  `.env.${process.env[envKey]}`,
  '.env.local',
  '.env',
]
```

so if you are in `prod`, rollup will search in

```
['.env.prod.local', '.env.prod', '.env.local', '.env']
```

and merge the result.

### `preventAssignment`

Type: `Boolean`
Default: `true`

Prevent things such as the following code to be replaced:

```javascript
const process.env.MY_VAR = 'foo';
```

See https://github.com/rollup/plugins/tree/master/packages/replace#preventassignment

### `replaceAllEnvVars`

Type: `Boolean`
Default: `true`

Replace all variables in `process.env.*` reference in code.

[LICENSE (MIT)](/LICENSE)
npm package: @gedhean/vue-glide-js
Description: Vue component on top of the Glide.js
Author: Anton Reshetov
Latest version: 1.3.19

<h1 align="center">Vue Glide</h1>

<p align="center">
  <img src="https://img.shields.io/npm/v/vue-glide-js.svg">
  <img src="https://img.shields.io/github/issues/antonreshetov/vue-glide.svg">
  <img src="https://img.shields.io/npm/dw/vue-glide-js.svg">
  <img alt="npm bundle size" src="https://img.shields.io/bundlephobia/minzip/vue-glide-js.svg">
  <img src="https://travis-ci.com/antonreshetov/vue-glide.svg?branch=master">
  <img src="https://img.shields.io/github/license/antonreshetov/vue-glide.svg">
</p>

<p align="center">Vue component on top of the <a href="https://github.com/glidejs/glide">Glide.js</a></p>

<img src="./docs/hero.png">

## Documentation

[https://antonreshetov.github.io/vue-glide](https://antonreshetov.github.io/vue-glide/)

## Install

### NPM

Installing with npm is recommended and it works seamlessly with webpack.

```bash
npm i vue-glide-js
```

### Download

You can download latest version from the Github: [Download](https://github.com/antonreshetov/vue-glide/archive/master.zip)

## Quick Start

### Global

To use in your project, just import vue-glide and install into Vue.

```js
import Vue from 'vue'
import App from './App.vue'
import VueGlide from 'vue-glide-js'
import 'vue-glide-js/dist/vue-glide.css'

Vue.use(VueGlide)

new Vue({
  el: '#app',
  render: h => h(App)
})
```

### On demand

```html
<template>
  <div id="app">
    <vue-glide>
      <vue-glide-slide v-for="i in 10" :key="i">
        Slide {{ i }}
      </vue-glide-slide>
    </vue-glide>
  </div>
</template>

<script>
  import { Glide, GlideSlide } from 'vue-glide-js'

  export default {
    components: {
      [Glide.name]: Glide,
      [GlideSlide.name]: GlideSlide
    }
  }
</script>
```

## License

MIT © 2018-present [Anton Reshetov](http://antonreshetov.com)