open-index/open-npm huggingface dataset:
npm package: @kesplus/dagre
Description: Graph layout for JavaScript
Author: Chris Pettitt
Latest version: 1.1.3

# dagre - Graph layout for JavaScript

[![Build Status](https://github.com/dagrejs/dagre/workflows/Build%20Status/badge.svg?branch=master)](https://github.com/dagrejs/dagre/actions?query=workflow%3A%22Build+Status%22)
[![npm](https://img.shields.io/npm/v/dagre.svg)](https://www.npmjs.com/package/dagre)


Dagre is a JavaScript library that makes it easy to lay out directed graphs on the client-side.

For more details, including examples and configuration options, please see our [wiki](https://github.com/dagrejs/dagre/wiki).

There are 2 versions on NPM, but only [the one in the DagreJs org](https://www.npmjs.com/package/@dagrejs/dagre) is receiving updates right now.

## License

dagre is licensed under the terms of the MIT License. See the LICENSE file for details.
npm package: @kesplus/editor-for-vue
Description: wangEditor component for vue@next
Author: liuqh0609
Latest version: 5.1.12

# wangEditor for vue-next component

[![GitHub license](https://img.shields.io/badge/license-MIT-blue.svg)](https://github.com/facebook/react/blob/main/LICENSE) [![npm](https://img.shields.io/npm/v/@wangeditor/editor-for-vue/next.svg)](https://www.npmjs.com/package/@wangeditor/editor-for-vue/v/next) [![build status](https://github.com/wangeditor-team/wangEditor-for-vue3/actions/workflows/npm-publish.yml/badge.svg?branch=main)](https://github.com/wangeditor-team/wangEditor-for-vue3/actions)

[English documentation](./README-en.md)

## 介绍

基于 [wangEditor](https://www.wangeditor.com/) 封装的开箱即用的 [Vue3 组件](https://www.wangeditor.com/v5/for-frame.html#vue3)

## 安装

```shell
yarn add @wangeditor/editor
yarn add @wangeditor/editor-for-vue@next
```

## 使用

参考[文档](https://www.wangeditor.com/v5/for-frame.html#vue3)
npm package: @kesplus/findup-sync
Description: Find the first file matching a given pattern in the current directory or the nearest ancestor directory.
Author: Gulp Team
Latest version: 5.0.0

<p align="center">
  <a href="http://gulpjs.com">
    <img height="257" width="114" src="https://raw.githubusercontent.com/gulpjs/artwork/master/gulp-2x.png">
  </a>
</p>

# findup-sync

[![NPM version][npm-image]][npm-url] [![Downloads][downloads-image]][npm-url] [![Build Status][ci-image]][ci-url] [![Coveralls Status][coveralls-image]][coveralls-url]

Find the first file matching a given pattern in the current directory or the nearest ancestor directory.

Matching is done with [micromatch][micromatch], please report any matching related issues on that repository.

## Usage

```js
var findup = require('findup-sync');
findup(patternOrPatterns [, micromatchOptions]);

// Start looking in the CWD.
var filepath1 = findup('{a,b}*.txt');

// Start looking somewhere else, and ignore case (probably a good idea).
var filepath2 = findup('{a,b}*.txt', {cwd: '/some/path', nocase: true});
```

## API

### `findup(patterns, [options])`

- `patterns` **{String|Array}**: Glob pattern(s) or file path(s) to match against.
- `options` **{Object}**: Options to pass to [micromatch]. Note that if you want to start in a different directory than the current working directory, specify a `cwd` property here.
- `returns` **{String}**: Returns the first matching file.

## License

MIT

<!-- prettier-ignore-start -->

[downloads-image]: https://img.shields.io/npm/dm/findup-sync.svg?style=flat-square
[npm-url]: https://www.npmjs.com/package/findup-sync
[npm-image]: https://img.shields.io/npm/v/findup-sync.svg?style=flat-square
[ci-url]: https://github.com/gulpjs/findup-sync/actions?query=workflow:dev
[ci-image]: https://img.shields.io/github/workflow/status/gulpjs/findup-sync/dev?style=flat-square
[coveralls-url]: https://coveralls.io/r/gulpjs/findup-sync
[coveralls-image]: https://img.shields.io/coveralls/gulpjs/findup-sync/master.svg

<!-- prettier-ignore-nd -->

<!-- prettier-ignore-start -->

[micromatch]: http://github.com/micromatch/micromatch

<!-- prettier-ignore-nd -->
npm package: @kesplus/pirates
Description: Properly hijack require, i.e., properly define require hooks and customizations
Author: Ari Porad
Latest version: 4.0.6

# Pirates [![Coverage][codecov-badge]][codecov-link]

### Properly hijack require

[codecov-badge]: https://img.shields.io/codecov/c/github/danez/pirates/master.svg?style=flat "codecov"
[codecov-link]: https://codecov.io/gh/danez/pirates "codecov"

## Why?

Two reasons:
1. Babel and istanbul were breaking each other.
2. Everyone seemed to re-invent the wheel on this, and everyone wanted a solution that was DRY, simple, easy to use,
and made everything Just Work™, while allowing multiple require hooks, in a fashion similar to calling `super`.

For some context, see [the Babel issue thread][] which started this all, then [the nyc issue thread][], where
discussion was moved (as we began to discuss just using the code nyc had developed), and finally to [#1][issue-1]
where discussion was finally moved.

[the Babel issue thread]: https://github.com/babel/babel/pull/3062 "Babel Issue Thread"
[the nyc issue thread]: https://github.com/bcoe/nyc/issues/70 "NYC Issue Thread"
[issue-1]: https://github.com/danez/pirates/issues/1 "Issue #1"

## Installation

    npm install --save pirates

## Usage

Using pirates is really easy:
```javascript
// my-module/register.js
const addHook = require('pirates').addHook;
// Or if you use ES modules
// import { addHook } from 'pirates';

function matcher(filename) {
  // Here, you can inspect the filename to determine if it should be hooked or
  // not. Just return a truthy/falsey. Files in node_modules are automatically ignored,
  // unless otherwise specified in options (see below).

  // TODO: Implement your logic here
  return true;
}

const revert = addHook(
  (code, filename) => code.replace('@@foo', 'console.log(\'foo\');'),
  { exts: ['.js'], matcher }
);

// And later, if you want to un-hook require, you can just do:
revert();
```

## API

### pirates.addHook(hook, [opts={ [matcher: true], [exts: ['.js']], [ignoreNodeModules: true] }]);
Add a require hook. `hook` must be a function that takes `(code, filename)`, and returns the modified code. `opts` is
an optional options object. Available options are: `matcher`, which is a function that accepts a filename, and
returns a truthy value if the file should be hooked (defaults to a function that always returns true), falsey if
otherwise; `exts`, which is an array of extensions to hook, they should begin with `.` (defaults to `['.js']`);
`ignoreNodeModules`, if true, any file in a `node_modules` folder wont be hooked (the matcher also wont be called),
if false, then the matcher will be called for any files in `node_modules` (defaults to true).


## Projects that use Pirates

See the [wiki page](https://github.com/danez/pirates/wiki/Projects-using-Pirates). If you add Pirates to your project,
(And you should! It works best if everyone uses it. Then we can have a happy world full of happy require hooks!), please
add yourself to the wiki.
npm package: @kessl/next-flash
Description: Universal flash messages for express. Works both client- and server-side. Fork of original next-flash
Author: Daniel Kessl
Latest version: 1.0.3

# Flash messages for next.js

[Flash messages](https://docs.typo3.org/typo3cms/CoreApiReference/ApiOverview/FlashMessages/Index.html) for [next.js](https://github.com/zeit/next.js). Works on both the client and the server.

## Examples

Example use in a server context:
```js
import flash from '@kessl/next-flash'

server.get('/set', (req, res) => {
  flash.set({ req, res }, { testFlash: 'Test flash message' });
  res.send('Flash message set');
});

server.get('/get', (req, res) => {
  const flash = flash.get({ req, res });
  res.send('Active flash messages: ' + JSON.stringify(flash));
});
```

Example use in a client context:
```js
import flash from 'next-flash';

export default class Page extends Component {
  static async getInitialProps (ctx) {
    return flash.get(ctx) || {}
  }

  create () {
    flash.set({ name: 'matt' })
  }

  render () {
    return (
      <div>
        <Head>
          <title>Flash messages in Next</title>
          <meta name='viewport' content='width=device-width, initial-scale=1' />
        </Head>
        { this.props.name ? <div>FLASH MESSAGE {this.props.name}</div> : <div /> }
        <button onClick={() => this.create()}>Create flash message</button>
        <br />
        <Link href={`/?${Date.now()}`}>Client-Side Route</Link>
      </div>
    )
  }
}
```

## Installation

```sh
npm install --save @kessl/next-flash
```

## License

MIT
npm package: @kessler/ansi-html-stream
Description: Stream ANSI terminal output to an HTML format.
Author: Hugh Kennedy
Latest version: 1.0.0

# ansi-html-stream [![Build Status](https://secure.travis-ci.org/hughsk/ansi-html-stream.png?branch=master)](http://travis-ci.org/hughsk/ansi-html-stream) [ ![Codeship Status for hughsk/ansi-html-stream](https://codeship.io/projects/a0eb0ea0-30a9-0132-9637-7a1e36b51a42/status)](https://codeship.io/projects/39881)

A through-stream that converts terminal output to HTML.

## this is a fork

of [ansi-html-stream](https://github.com/hughsk/ansi-html-stream) module, made by the wonderful Open Source author [@hughsk](https://github.com/hughsk). all credit goes to him. 

changes:

- mocha version was updated and tests too.
- the non-functioning module `clone` was replaced with the "native" function `structuredClone`


## Installation

``` bash
$ npm install ansi-html-stream
```

Or, if you want to install the CLI tool:

``` bash
$ [sudo] npm install -g ansi-html-stream
```

## Usage

Take this example to pipe a log of NPM's `install` command to an HTML file:

``` bash
$ npm install browserify --color always 2&>1 | ansi-html > browserify.html
```

And an equivalent from Node:

``` javascript
var spawn = require('child_process').spawn
  , ansi = require('ansi-html-stream')
  , fs = require('fs')

var npm = spawn('npm', ['install', 'browserify', '--color', 'always'], {
    cwd: process.cwd()
})

var stream = ansi({ chunked: false })
  , file = fs.createWriteStream('browserify.html', 'utf8')

npm.stdout.pipe(stream)
npm.stderr.pipe(stream)

stream.pipe(file, { end: false })

stream.once('end', function() {
  file.end('</pre>\n')
})

file.write('<pre>\n');
```

There are a few options you can pass to the stream too:

* `classes`: Use classes instead of inline styles for formatting.
* `theme`: Override the styling for particular ANSI codes. See [`colors.js`](http://github.com/hughsk/ansi-html-stream/blob/master/colors.js) for two examples.
* `chunked`: Ensure that each chunk's elements are self-contained - closes any open `<span>`s at the end and reopens them on the next chunk. Defaults to false.