open-index/open-npm huggingface dataset:
npm package: @offline-ai/cli-plugin-provider-openai
Description: Offline(local) AI CLI OpenAI Provider
Author: Riceball LEE
Latest version: 0.1.32

# AI CLI OpenAI Provider Plugin

> 【English|[中文](./README.cn.md)】
---

The [Offline AI Client](https://npmjs.org/package/@offline-ai/cli) plugin for OpenAI and OpenAI-compatible Provider.

[![oclif](https://img.shields.io/badge/cli-oclif-brightgreen.svg)](https://oclif.io)
[![Version](https://img.shields.io/npm/v/%40offline-ai%2Fcli-plugin-provider-openai.svg)](https://npmjs.org/package/@offline-ai/cli-plugin-provider-openai)
[![Downloads/week](https://img.shields.io/npm/dw/%40offline-ai%2Fcli-plugin-provider-openai.svg)](https://npmjs.org/package/@offline-ai/cli-plugin-provider-openai)

# Quick Start

Before using, you need to first install the [Offline AI Client](https://npmjs.org/package/@offline-ai/cli).

# Install

```bash
#If not already installed, install the client:
npm install -g @offline-ai/cli
```

<!-- toc -->
* [AI CLI OpenAI Provider Plugin](#ai-cli-openai-provider-plugin)
* [Quick Start](#quick-start)
* [Install](#install)
* [Commands](#commands)
<!-- tocstop -->

# Commands

<!-- commands -->

<!-- commandsstop -->
npm package: @offlinech/laravel-mix-browser-sync-notifier
Description: Display a Browser Sync notification for compilation errors in Laravel Mix
Author: Tobias Kuendig
Latest version: 1.0.1

# Laravel Mix Browser Sync Notifier

Display a Browser Sync notification for compilation errors in Laravel Mix

## Usage

Install the package:

```bash
npm i --save-dev @offlinech/laravel-mix-browser-sync-notifier
# yarn add -D @offlinech/laravel-mix-browser-sync-notifier
```

Then include it in your `webpack.mix.js`:


```js
const mix = require('laravel-mix')

require('@offlinech/laravel-mix-browser-sync-notifier')

mix
    .browserSync()
    .browserSyncNotifyErrors() 
```
npm package: @offlinech/postcss-normalize
Description: PostCSS plugin that automatically applies normalize.css
Author: Sean King
Latest version: 0.4.1

# PostCSS Normalize

This is a fork of https://github.com/seaneking/postcss-normalize

[PostCSS][PostCSS] plugin that that automatically applies the latest normalize.css.

```css
.foo {
  color: #fff;
}
```

```css

/* Normalize styles here */

.foo {
  color: #fff;
}
```

--

### Usage

```js
postcss([ require('postcss-normalize') ])
```

See [PostCSS][PostCSS] docs for examples for your environment.

--

### License

MIT ©
npm package: @offliner/dltracker-dir-compare
Description: Compare directories of packages obtained by npm download
Author: Matthew Rafferty
Latest version: 1.0.0

# dltracker-dir-compare
Compare directories of packages obtained by the `npm download` command

## Overview
*The `npm download` command is only available when an installation of `npm` has been overlaid with [npm-two-stage](https://github.com/mmraff/npm-two-stage#readme).
The official `npm` interface **does not** have a `download` command at this time.*

In short, `npm download` fetches named packages, and all the packages of their dependency trees, as a means of collecting all that is needed for offline installation on another system.

If one has used this command several times, retaining the results but not always reusing the same target directory, it may result in many duplicate copies of packages distributed across multiple directories.

This module provides a command line interface to compare the contents of two or more such directories, and report what they have in common - or, alternately, what each has that none of the other directories have.

## To Install

Typical CLI use is from a global installation:
```
$ npm install -g dltracker-dir-compare
```
But local installation is valid, and possibly useful for the submodules:
```
$ npm install --save dltracker-dir-compare
```
*See documentation for the submodules in lib_API.md.*

## Usage
Enter the `dltdir-compare` command with the paths of two or more `npm download` directories.
```
$ dltdir-compare PATH_1 PATH_2 [... PATH_n]
```

A Posix glob expression may be given for one or more of the path arguments, provided that the argument list resolves to at least two existing directories. *See [documentation for **node-glob**](https://github.com/isaacs/node-glob/tree/v7.1.7#readme).*

By default, `dltdir-compare` reports only the files that directories have in common. An option is provided to report files unique to each directory instead:
```
$ dltdir-compare --unique PATH_1 PATH_2 [... PATH_n]
```

Another option is provided to get counts rather than lists of files, whether in common for sets of directories or unique to each:
```
$ dltdir-compare --count PATH_1 PATH_2 [... PATH_n]
$ dltdir-compare --unique --count PATH_1 PATH_2 [... PATH_n]
```

Show version and exit:
```
$ dltdir-compare --version
```

------

**License: MIT**
npm package: @offliner/npm2stage-v7.24.0
Description: CLI to manage npm-two-stage installation for npm 7.24.0
Author: Matthew Rafferty
Latest version: 1.0.0

# @offliner/npm2stage-v7.24.0
CLI to manage [**npm-two-stage**](https://github.com/mmraff/npm-two-stage/tree/npm7.24.0 "Learn why you might want this!") installation for npm 7.24.0

## Installation
```
$ npm install -g @offliner/npm2stage-v7.24.0
```

## Usage
The installed npm that is to be the target of this tool's commands must be of the targeted version. If it doesn't match, the tool will tell you so, and it will not operate on it.

In these examples, the OS is Windows, the tool is used in a git bash console, and the target location is the typical global installation location. However, the tool (and [**npm-two-stage**](https://github.com/mmraff/npm-two-stage/tree/npm7.24.0 "Learn why you might want this!")) are platform-agnostic, and the target npm installation can be any accessible location, including on a removeable drive.
```
$ npm2stage status

    Checking npm version at given path...
    Target npm home is C:\Program Files\nodejs\node_modules\npm
    No backups present.
    No standard files missing.
    No new files present.
    npm-two-stage is not installed at this location.

```
At this point, it's appropriate to run `npm2stage install`.
```
$ npm2stage install

   Checking npm version at given path...
   Target npm home is C:\Program Files\nodejs\node_modules\npm
   Backing up files to be replaced:
     # (original files listed here)
   Copying into target directory:
     # (replacements and new files/dirs listed here)

   Installation of npm-two-stage was successful.

```
At this point, `npm download` and `npm install --offline` are ready to be used.

# 

```
$ npm2stage status

   Checking npm version at given path...
   Target npm home is C:\Program Files\nodejs\node_modules\npm
   All backups present.
   No standard files missing.
   All expected new files present.
   npm-two-stage is fully installed at this location.

```
At this point, you may run `npm2stage uninstall` (if you must).
```
$ npm2stage uninstall

   Checking npm version at given path...
   Target npm home is C:\Program Files\nodejs\node_modules\npm
   Removing items added by npm-two-stage install:
     # (replacements and new files/dirs listed here)
   Restoring backed-up original files...
     # (original files listed here)
    
   Removal of npm-two-stage was successful.

```

#

For the `install` and `uninstall` commands, there are the abbreviations that the power user of npm will be familiar with: `i` and `un`. Also for these two commands, there is the `--silent` option to mute output unless there is an error.

For help:
```
$ npm2stage help
```
...or specifically for a command:
```
$ npm2stage install -h
```
npm package: @offliner/npm2stage-v7.24.2
Description: CLI to manage npm-two-stage installation for npm 7.24.2
Author: Matthew Rafferty
Latest version: 1.0.0

# @offliner/npm2stage-v7.24.2
CLI to manage [**npm-two-stage**](https://github.com/mmraff/npm-two-stage/tree/npm7.24.2 "Learn why you might want this!") installation for npm 7.24.2

## Installation
```
$ npm install -g @offliner/npm2stage-v7.24.2
```

## Usage
The installed npm that is to be the target of this tool's commands must be of the targeted version. If it doesn't match, the tool will tell you so, and it will not operate on it.

In these examples, the OS is Windows, the tool is used in a git bash console, and the target location is the typical global installation location. However, the tool (and [**npm-two-stage**](https://github.com/mmraff/npm-two-stage/tree/npm7.24.2 "Learn why you might want this!")) are platform-agnostic, and the target npm installation can be any accessible location, including on a removeable drive.
```
$ npm2stage status

    Checking npm version at given path...
    Target npm home is C:\Program Files\nodejs\node_modules\npm
    No backups present.
    No standard files missing.
    No new files present.
    npm-two-stage is not installed at this location.

```
At this point, it's appropriate to run `npm2stage install`.
```
$ npm2stage install

   Checking npm version at given path...
   Target npm home is C:\Program Files\nodejs\node_modules\npm
   Backing up files to be replaced:
     # (original files listed here)
   Copying into target directory:
     # (replacements and new files/dirs listed here)

   Installation of npm-two-stage was successful.

```
At this point, `npm download` and `npm install --offline` are ready to be used.

# 

```
$ npm2stage status

   Checking npm version at given path...
   Target npm home is C:\Program Files\nodejs\node_modules\npm
   All backups present.
   No standard files missing.
   All expected new files present.
   npm-two-stage is fully installed at this location.

```
At this point, you may run `npm2stage uninstall` (if you must).
```
$ npm2stage uninstall

   Checking npm version at given path...
   Target npm home is C:\Program Files\nodejs\node_modules\npm
   Removing items added by npm-two-stage install:
     # (replacements and new files/dirs listed here)
   Restoring backed-up original files...
     # (original files listed here)
    
   Removal of npm-two-stage was successful.

```

#

For the `install` and `uninstall` commands, there are the abbreviations that the power user of npm will be familiar with: `i` and `un`. Also for these two commands, there is the `--silent` option to mute output unless there is an error.

For help:
```
$ npm2stage help
```
...or specifically for a command:
```
$ npm2stage install -h
```
npm package: @offliner/npm2stage-v8.19.4
Description: CLI to manage npm-two-stage installation for npm 8.19.4
Author: Matthew Rafferty
Latest version: 1.0.0

# @offliner/npm2stage-v8.19.4
CLI to manage [**npm-two-stage**](https://github.com/mmraff/npm-two-stage/tree/npm8.19.4 "Learn why you might want this!") installation for npm 8.19.4

## Installation
```
$ npm install -g @offliner/npm2stage-v8.19.4
```

## Usage
The installed npm that is to be the target of this tool's commands must be of the targeted version. If it doesn't match, the tool will tell you so, and it will not operate on it.

In these examples, the OS is Windows, the tool is used in a git bash console, and the target location is the typical global installation location. However, the tool (and [**npm-two-stage**](https://github.com/mmraff/npm-two-stage/tree/npm8.19.4 "Learn why you might want this!")) are platform-agnostic, and the target npm installation can be any accessible location, including on a removeable drive.
```
$ npm2stage status

    Checking npm version at given path...
    Target npm home is C:\Program Files\nodejs\node_modules\npm
    No backups present.
    No standard files missing.
    No new files present.
    npm-two-stage is not installed at this location.

```
At this point, it's appropriate to run `npm2stage install`.
```
$ npm2stage install

   Checking npm version at given path...
   Target npm home is C:\Program Files\nodejs\node_modules\npm
   Backing up files to be replaced:
     # (original files listed here)
   Copying into target directory:
     # (replacements and new files/dirs listed here)

   Installation of npm-two-stage was successful.

```
At this point, `npm download` and `npm install --offline` are ready to be used.

# 

```
$ npm2stage status

   Checking npm version at given path...
   Target npm home is C:\Program Files\nodejs\node_modules\npm
   All backups present.
   No standard files missing.
   All expected new files present.
   npm-two-stage is fully installed at this location.

```
At this point, you may run `npm2stage uninstall` (if you must).
```
$ npm2stage uninstall

   Checking npm version at given path...
   Target npm home is C:\Program Files\nodejs\node_modules\npm
   Removing items added by npm-two-stage install:
     # (replacements and new files/dirs listed here)
   Restoring backed-up original files...
     # (original files listed here)
    
   Removal of npm-two-stage was successful.

```

#

For the `install` and `uninstall` commands, there are the abbreviations that the power user of npm will be familiar with: `i` and `un`. Also for these two commands, there is the `--silent` option to mute output unless there is an error.

For help:
```
$ npm2stage help
```
...or specifically for a command:
```
$ npm2stage install -h
```
npm package: @offliner/npm2stage-v9.5.1
Description: CLI to manage npm-two-stage installation for npm 9.5.1
Author: Matthew Rafferty
Latest version: 1.0.0

# @offliner/npm2stage-v9.5.1
CLI to manage [**npm-two-stage**](https://github.com/mmraff/npm-two-stage/tree/npm9.5.1 "Learn why you might want this!") installation for npm 9.5.1

## Installation
```
$ npm install -g @offliner/npm2stage-v9.5.1
```

## Usage
The npm installation that is to be the target of this tool's commands must have the targeted version. If it doesn't match, the tool will tell you so, and it will not operate on it.

In these examples, the OS is Windows, the tool is used in a git bash console, and the target location is the typical global installation location. However, the tool (and [**npm-two-stage**](https://github.com/mmraff/npm-two-stage/tree/npm9.5.1 "Learn why you might want this!")) are platform-agnostic, and the target npm installation can be any accessible location, including on a removeable drive.
```
$ npm2stage status

    Checking npm version at given path...
    Target npm home is C:\Program Files\nodejs\node_modules\npm
    No backups present.
    No standard files missing.
    No new files present.
    npm-two-stage is not installed at this location.

```
At this point, it's appropriate to run `npm2stage install`.
```
$ npm2stage install

   Checking npm version at given path...
   Target npm home is C:\Program Files\nodejs\node_modules\npm
   Backing up files to be replaced:
     # (original files listed here)
   Copying into target directory:
     # (replacements and new files/dirs listed here)

   Installation of npm-two-stage was successful.

```
At this point, `npm download` and `npm install --offline` are ready to be used.

# 

```
$ npm2stage status

   Checking npm version at given path...
   Target npm home is C:\Program Files\nodejs\node_modules\npm
   All backups present.
   No standard files missing.
   All expected new files present.
   npm-two-stage is fully installed at this location.

```
At this point, you may run `npm2stage uninstall` (if you must).
```
$ npm2stage uninstall

   Checking npm version at given path...
   Target npm home is C:\Program Files\nodejs\node_modules\npm
   Removing items added by npm-two-stage install:
     # (replacements and new files/dirs listed here)
   Restoring backed-up original files...
     # (original files listed here)
    
   Removal of npm-two-stage was successful.

```

#

For the `install` and `uninstall` commands, there are the abbreviations that the power user of npm will be familiar with: `i` and `un`. Also for these two commands, there is the `--silent` option to mute output unless there is an error.

For help:
```
$ npm2stage help
```
...or specifically for a command:
```
$ npm2stage install -h
```
npm package: @offliner/npm2stage-v9.6.7
Description: CLI to manage npm-two-stage installation for npm 9.6.7
Author: Matthew Rafferty
Latest version: 1.0.0

# @offliner/npm2stage-v9.6.7
CLI to manage [**npm-two-stage**](https://github.com/mmraff/npm-two-stage/tree/npm9.6.7 "Learn why you might want this!") installation for npm 9.6.7

## Installation
```
$ npm install -g @offliner/npm2stage-v9.6.7
```

## Usage
The npm installation that is to be the target of this tool's commands must have the targeted version. If it doesn't match, the tool will tell you so, and it will not operate on it.

In these examples, the OS is Windows, the tool is used in a git bash console, and the target location is the typical global installation location. However, the tool (and [**npm-two-stage**](https://github.com/mmraff/npm-two-stage/tree/npm9.6.7 "Learn why you might want this!")) are platform-agnostic, and the target npm installation can be any accessible location, including on a removeable drive.
```
$ npm2stage status

    Checking npm version at given path...
    Target npm home is C:\Program Files\nodejs\node_modules\npm
    No backups present.
    No standard files missing.
    No new files present.
    npm-two-stage is not installed at this location.

```
At this point, it's appropriate to run `npm2stage install`.
```
$ npm2stage install

   Checking npm version at given path...
   Target npm home is C:\Program Files\nodejs\node_modules\npm
   Backing up files to be replaced:
     # (original files listed here)
   Copying into target directory:
     # (replacements and new files/dirs listed here)

   Installation of npm-two-stage was successful.

```
At this point, `npm download` and `npm install --offline` are ready to be used.

# 

```
$ npm2stage status

   Checking npm version at given path...
   Target npm home is C:\Program Files\nodejs\node_modules\npm
   All backups present.
   No standard files missing.
   All expected new files present.
   npm-two-stage is fully installed at this location.

```
At this point, you may run `npm2stage uninstall` (if you must).
```
$ npm2stage uninstall

   Checking npm version at given path...
   Target npm home is C:\Program Files\nodejs\node_modules\npm
   Removing items added by npm-two-stage install:
     # (replacements and new files/dirs listed here)
   Restoring backed-up original files...
     # (original files listed here)
    
   Removal of npm-two-stage was successful.

```

#

For the `install` and `uninstall` commands, there are the abbreviations that the power user of npm will be familiar with: `i` and `un`. Also for these two commands, there is the `--silent` option to mute output unless there is an error.

For help:
```
$ npm2stage help
```
...or specifically for a command:
```
$ npm2stage install -h
```
npm package: @offliner/npm2stage-v9.7.2
Description: CLI to manage npm-two-stage installation for npm 9.7.2
Author: Matthew Rafferty
Latest version: 1.0.0

# @offliner/npm2stage-v9.7.2
CLI to manage [**npm-two-stage**](https://github.com/mmraff/npm-two-stage/tree/npm9.7.2 "Learn why you might want this!") installation for npm 9.7.2

## Installation
```
$ npm install -g @offliner/npm2stage-v9.7.2
```

## Usage
The npm installation that is to be the target of this tool's commands must have the targeted version. If it doesn't match, the tool will tell you so, and it will not operate on it.

In these examples, the OS is Windows, the tool is used in a git bash console, and the target location is the typical global installation location. However, the tool (and [**npm-two-stage**](https://github.com/mmraff/npm-two-stage/tree/npm9.7.2 "Learn why you might want this!")) are platform-agnostic, and the target npm installation can be any accessible location, including on a removeable drive.
```
$ npm2stage status

    Checking npm version at given path...
    Target npm home is C:\Program Files\nodejs\node_modules\npm
    No backups present.
    No standard files missing.
    No new files present.
    npm-two-stage is not installed at this location.

```
At this point, it's appropriate to run `npm2stage install`.
```
$ npm2stage install

   Checking npm version at given path...
   Target npm home is C:\Program Files\nodejs\node_modules\npm
   Backing up files to be replaced:
     # (original files listed here)
   Copying into target directory:
     # (replacements and new files/dirs listed here)

   Installation of npm-two-stage was successful.

```
At this point, `npm download` and `npm install --offline` are ready to be used.

# 

```
$ npm2stage status

   Checking npm version at given path...
   Target npm home is C:\Program Files\nodejs\node_modules\npm
   All backups present.
   No standard files missing.
   All expected new files present.
   npm-two-stage is fully installed at this location.

```
At this point, you may run `npm2stage uninstall` (if you must).
```
$ npm2stage uninstall

   Checking npm version at given path...
   Target npm home is C:\Program Files\nodejs\node_modules\npm
   Removing items added by npm-two-stage install:
     # (replacements and new files/dirs listed here)
   Restoring backed-up original files...
     # (original files listed here)
    
   Removal of npm-two-stage was successful.

```

#

For the `install` and `uninstall` commands, there are the abbreviations that the power user of npm will be familiar with: `i` and `un`. Also for these two commands, there is the `--silent` option to mute output unless there is an error.

For help:
```
$ npm2stage help
```
...or specifically for a command:
```
$ npm2stage install -h
```
npm package: @offliner/npm2stage-v9.8.1
Description: CLI to manage npm-two-stage installation for npm 9.8.1
Author: Matthew Rafferty
Latest version: 1.0.0

# @offliner/npm2stage-v9.8.1
CLI to manage [**npm-two-stage**](https://github.com/mmraff/npm-two-stage/tree/npm9.8.1 "Learn why you might want this!") installation for npm 9.8.1

## Installation
```
$ npm install -g @offliner/npm2stage-v9.8.1
```

## Usage
The npm installation that is to be the target of this tool's commands must have the targeted version. If it doesn't match, the tool will tell you so, and it will not operate on it.

In these examples, the OS is Windows, the tool is used in a git bash console, and the target location is the typical global installation location. However, the tool (and [**npm-two-stage**](https://github.com/mmraff/npm-two-stage/tree/npm9.8.1 "Learn why you might want this!")) are platform-agnostic, and the target npm installation can be any accessible location, including on a removeable drive.
```
$ npm2stage status

    Checking npm version at given path...
    Target npm home is C:\Program Files\nodejs\node_modules\npm
    No backups present.
    No standard files missing.
    No new files present.
    npm-two-stage is not installed at this location.

```
At this point, it's appropriate to run `npm2stage install`.
```
$ npm2stage install

   Checking npm version at given path...
   Target npm home is C:\Program Files\nodejs\node_modules\npm
   Backing up files to be replaced:
     # (original files listed here)
   Copying into target directory:
     # (replacements and new files/dirs listed here)

   Installation of npm-two-stage was successful.

```
At this point, `npm download` and `npm install --offline` are ready to be used.

# 

```
$ npm2stage status

   Checking npm version at given path...
   Target npm home is C:\Program Files\nodejs\node_modules\npm
   All backups present.
   No standard files missing.
   All expected new files present.
   npm-two-stage is fully installed at this location.

```
At this point, you may run `npm2stage uninstall` (if you must).
```
$ npm2stage uninstall

   Checking npm version at given path...
   Target npm home is C:\Program Files\nodejs\node_modules\npm
   Removing items added by npm-two-stage install:
     # (replacements and new files/dirs listed here)
   Restoring backed-up original files...
     # (original files listed here)
    
   Removal of npm-two-stage was successful.

```

#

For the `install` and `uninstall` commands, there are the abbreviations that the power user of npm will be familiar with: `i` and `un`. Also for these two commands, there is the `--silent` option to mute output unless there is an error.

For help:
```
$ npm2stage help
```
...or specifically for a command:
```
$ npm2stage install -h
```