open-index/open-npm huggingface dataset:
npm package: @levelworks/typedi
Description: Dependency injection for TypeScript.
Author: TypeStack contributors
Latest version: 0.11.2

# TypeDI

![Build Status](https://github.com/level-works/typedi/workflows/CI/badge.svg)
[![npm version](https://img.shields.io/npm/v/@level-works/typedi)](https://npmjs.com/package/@level-works/typedi)

TypeDI is a [dependency injection](https://en.wikipedia.org/wiki/Dependency_injection) tool for TypeScript and JavaScript. With it you can build well-structured and easily testable applications in Node or in the browser.

Main features includes:

- property based injection
- constructor based injection
- singleton and transient services
- support for multiple DI containers

## Installation

> Note: This installation guide is for usage with TypeScript, if you wish to use
> TypeDI without Typescript please read the documentation about how get started.

To start using TypeDI install the required packages via NPM:

```bash
npm install typedi reflect-metadata
```

Import the `reflect-metadata` package at the **first line** of your application:

```ts
import 'reflect-metadata';

// Your other imports and initialization code
// comes here after you imported the reflect-metadata package!
```

As a last step, you need to enable emitting decorator metadata in your Typescript config. Add these two lines to your `tsconfig.json` file under the `compilerOptions` key:

```json
"emitDecoratorMetadata": true,
"experimentalDecorators": true,
```

Now you are ready to use TypeDI with Typescript!

## Basic Usage

```ts
import { Container, Service } from '@levelworks/typedi';

@Service()
class ExampleInjectedService {
  printMessage() {
    console.log('I am alive!');
  }
}

@Service()
class ExampleService {
  constructor(
    // because we annotated ExampleInjectedService with the @Service()
    // decorator TypeDI will automatically inject an instance of
    // ExampleInjectedService here when the ExampleService class is requested
    // from TypeDI.
    public injectedService: ExampleInjectedService
  ) {}
}

const serviceInstance = Container.get(ExampleService);
// we request an instance of ExampleService from TypeDI

serviceInstance.injectedService.printMessage();
// logs "I am alive!" to the console
```

## Documentation

The detailed usage guide and API documentation for the project can be found:

- at [docs.typestack.community/typedi][docs-stable]
- in the `./docs` folder of the repository

[docs-stable]: https://docs.typestack.community/typedi/
[docs-development]: https://docs.typestack.community/typedi/v/develop/

## Why the fork?

The only activity on [the original typedi](https://github.com/typestack/typedi)
was by bots, not by maintainers. Because of this lack of maintenance, no release
has been made since Jan 15, 2021 even though bugfixes have been merged into it's
develop branch.

This fork is solely to have the most recent state of
[typedi](https://npmjs.com/package/typedi) available on npmjs. Should the
original typedi receive updates again, this fork should track those instead of
implementing other behavior.

## Contributing

Please read our [contributing guidelines](./CONTRIBUTING.md) to get started.
npm package: @levelxup/ai-git-review
Description: AI Git Code Reviewer for Laravel + Vue projects
Author: Abdulalim Mohamed
Latest version: 1.0.0

# AI Git Code Reviewer

A global AI code review tool for Laravel + Vue projects.
Automatically reviews staged code before commits and blocks commits if critical issues are found (e.g., `dd()`, `dump()`, `console.log()`, security or performance issues).

This tool uses [OpenRouter](https://openrouter.ai) or compatible OpenAI endpoints.

---

## Installation

1. Install the package globally via NPM:

```bash
npm install -g ai-git-review
```

Make sure you have **Node.js >= 18** installed.

---

## Configuration

Copy the `.env-example` to `.env` inside the package folder:

```bash
cd $(npm root -g)/ai-git-review
cp .env-example .env
```

Edit the `.env` file and add your API key and configuration:

```env
OPENROUTER_API_KEY=your_openrouter_api_key_here
OPENROUTER_MODEL=deepseek/deepseek-coder
OPENROUTER_API_ENDPOINT=https://openrouter.ai/api/v1
OPENROUTER_MAX_TOKENS=400
```

> ⚠️ The script will always use the `.env` file located next to `index.js`, not your project's `.env`.

---

## Setup Git Pre-commit Hook (Optional)

To automatically run AI review on every commit:

**1. Create a global Git hooks folder** (if you don't have one yet):

```bash
mkdir -p ~/.git-hooks
```

**2. Create a `pre-commit` file inside it:**

```bash
nano ~/.git-hooks/pre-commit
```

**3. Add the following content:**

```sh
#!/bin/sh
# Run the global AI reviewer
AI_REVIEWER="$(npm root -g)/ai-git-review/index.js"

if [ ! -f "$AI_REVIEWER" ]; then
    echo "❌ AI reviewer script not found at $AI_REVIEWER"
    exit 0
fi

node "$AI_REVIEWER"
STATUS=$?

if [ $STATUS -eq 1 ]; then
    echo "❌ Commit blocked due to AI detected issues."
    exit 1
fi

echo "✅ Commit passed AI review."
exit 0
```

**4. Make it executable:**

```bash
chmod +x ~/.git-hooks/pre-commit
```

**5. Tell Git to use this global hooks folder:**

```bash
git config --global core.hooksPath ~/.git-hooks
```

Now all your repositories will automatically run AI code review on commit.

---

## Usage

Run manually in any repo:

```bash
ai-git-review
```

Or automatically via the Git pre-commit hook (recommended).

---

## Logging

All AI review results and errors are logged in your project at:

```
storage/logs/ai-review.log
```

The log includes timestamps and reasons for failed commits.

---

## Notes

- Only **staged changes** (`git add`) are reviewed.
- Only `.php`, `.js`, and `.vue` files are checked.
- Large diffs (>15,000 characters) are skipped automatically.
- Commits are **blocked only** if AI detects critical issues.
npm package: @levenpang/element-ui
Description: A Component Library for Vue.js.
Latest version: 1.1.14

# element-ui customize version
element-ui is [here](github.com/ElemeFE/element))

  Change Log:

  v1.0.6 2020-09-22

    1.Set left panel as prev month.
    2.add class-set to the cell on selected range even of not belong to the current month .

  v1.0.5 2020-07-06

    1.show time at datepicker panel header(display only)

  v1.0.4 2020-07-06

    1.add props to decide default time display on the input box or not

  v1.0.3 2020-06-19

    1.el selector customize css
    2.customize style
    3.filter search position

Branch base on tag v2.13.2


## LICENSE
[MIT](LICENSE)
npm package: @leventeszucs/devtools-detect
Description: Detects if devTools is open.
Author: @leventeszucs
Latest version: 1.0.4

## This package is a fork of [devtools-detect](https://www.npmjs.com/package/devtools-detect)

Added functionalities:
- `detectOnce` function

#### Usage
```js
import { detectOnce } from "@leventeszucs/devtools-detect"

const {isOpen, checkerName} = await detectOnce();
```
npm package: @leventsezer/multicorder
Description: Record video from cameras or screen. A base Vue 2 component as well as full Vuetify 2 UI is provided.
Latest version: 1.13.8

# Multicorder

[![multicorder](https://snyk.io/advisor/npm-package/multicorder/badge.svg)](https://snyk.io/advisor/npm-package/multicorder)  

* Record video from cameras
* Record video from desktop screens
* Playback recordings
* Take snapshots of video
* Download videos or snapshots

## Demo App

View the Multicorder on [Netlify](https://eloquent-kowalevski-0dbda6.netlify.app/).
Expect new versions weekly for a while.

## Why Multicorder?

1. Lightweight

All of the core logic is in a single Vue 2 component with no . outside of Vue. All the functionality can harnessed in any Vue 2 or Vue 3 app.

2. Batteries included!

A full featured Vuetify UI is included. If you are alredy using Vuetify you can record and download video and snapshots out of the box, no coding needed.

3. Full AWS Amplify integration (coming soon!)

This was designed from the outset to work well with AWS Amplify and S3 Storage. We'll publish a number of sample apps that showcase the functionality.

## Demo Site

You can see the app [deployed on Netlify](https://eloquent-kowalevski-0dbda6.netlify.app/).

 
## Installing

```bash
npm install multicorder
```

## Using the Multicorder core module

100% of the core functionality can be imported into any [Vue](https://vuejs.org/) 2 or Vue 3 app with no extra dependencies.

The [AWS Amplify](https://aws.amazon.com/amplify/) functionality will be in a separate component.

### Import the component in your `<script>`

```javascript
import { Multicorder } from 'multicorder';
```

## Using the Vuetify UI

To get up and running quickly a full UI is provided built on the wonderful [Vuetify](https://vuetifyjs.com/) framework.

### Import the Vue file from source

```javascript
import  MulticorderUI  from 'multicorder/vuetify_ui/src/components/MulticorderUI.vue';
```

### Export the component

```javascript
  export default {
    components: {
      MulticorderUI
    },
```

### Use in the template

```html
<MulticorderUI />
```

#### Define video options

You can limit the options to just cameras or just sreensharing if that is more appropriate for your needs.

Just define the videoTypes prop on the component as an array with he options(s) you want to support.

```html
<MulticorderUI 
  :videoTypes="['screen', 'camera']"
/>
```

or if you just want cameras offered:

```html
<MulticorderUI 
  :videoTypes="['camera']"
/>
```

The only options are `screen` and `camera`.
npm package: @leverage-js/ui
Description: Leverage UI
Author: Architech Labs
Latest version: 0.0.11

# UI

## Development

### Package

```bash
dev/npm install
dev/npm run watch
```

`dev/npm run watch` builds the package every time you update any component.
And it copies `dist/*` to `demo/node_modules/@leverage-js/ui` to make demo
always have the current `ui`.

### Demo

```bash
cd demo
dev/npm install
dev/npm run publish-ui-assets
dev/npm run serve
```

`dev/npm run serve` launches the dev web server with hot module reload. Demo file
updates are instant, while `ui` updates may take a couple of seconds for a full
dev server restart.

Latest demo is deployed on [ui.architechlabs.com](http://ui.architechlabs.com)
(test server):

```bash
deploy ui.architechlabs.com
```

### Export components

`index.js` contains all the exports. You put any new components or
component renames here.

## Publishing

### Version increment

Three commands for three kinds of increment:
- `npm version patch` 0.0.1 -> 0.0.2
- `npm version minor` 0.0.1 -> 0.1.0
- `npm version major` 0.0.1 -> 1.0.0

It creates a git tag as well. `dev/npm` fails to create a git tag in my env.

### Build

```bash
dev/npm run build
```

For some reason, npm package publishing doesn't work with Docker npm.
Until we have a fix, you'd publish with local npm:
```bash
npm publish
```

## Installation

```bash
npm install @leverage-js/ui
```

`demo` directory has a reference app.

Notice the `publish-ui-assets`
npm command that copies the `ui` assets to `web/ui`. You need a similar
command for your app because some components expect their assets to be available
in `/ui` from a web root.

For sane `ui` error messages in app, you need a dev `ui` build:

```bash
dev/npm run build:dev
```

Then copy `dist/index.js` to `node_modules/@leverage-js/ui/dist` in app
and rebuild it. `ui` error messages should be fine now.
npm package: @leverage/plugin-discord
Description: A Discord plugin for Leverage
Author: Jake Hamilton
Latest version: 3.1.0

# Discord for [Leverage](http://github.com/jakehamilton/leverage)!

This is a plugin for Leverage that handles the `discord` type of components.

## Discord Component

A Discord Component has the following interface:

```typescript
import { ComponentConfig, ComponentUnit } from '@leverage/core';

export interface DiscordConfig extends ComponentConfig {
    discord?: {
        event?: string; // A `Discord.js` event name (defaults to 'message')
        command?: string; // A prefix to listen for on "message" events (defaults to '')
    };
}

export interface DiscordComponent extends ComponentUnit {
    config: DiscordConfig;

    // The `payload` is a `Discord.js` object related to the event your component is listening to
    discord: (payload: any) => void;
}
```

## Example

```js
import { manager } from '@leverage/core';
import { Discord, DiscordComponent } from '@leverage/plugin-discord';

const discord = new Discord();

const component: DiscordComponent = {
    is: 'component',
    type: 'discord',
    discord ({ channel }) {
        // Respond to all messages with "Hello, World!"
        channel.send('Hello, World!');
    },
};

manager.add(discord, component);

discord.login('<YOUR_BOT_TOKEN>');
```

## Questions

Have a question? Feel free to [file an issue](https://github.com/jakehamilton/leverage-plugin-discord/issues/new)!