@qqbrowser/openclaw-qbot 0.0.148 → 0.10.1

package/node_modules/depd/Readme.md

@@ -1,280 +0,0 @@
-# depd
-
-[![NPM Version][npm-version-image]][npm-url]
-[![NPM Downloads][npm-downloads-image]][npm-url]
-[![Node.js Version][node-image]][node-url]
-[![Linux Build][travis-image]][travis-url]
-[![Windows Build][appveyor-image]][appveyor-url]
-[![Coverage Status][coveralls-image]][coveralls-url]
-
-Deprecate all the things
-
-> With great modules comes great responsibility; mark things deprecated!
-
-## Install
-
-This module is installed directly using `npm`:
-
-```sh
-$ npm install depd
-```
-
-This module can also be bundled with systems like
-[Browserify](http://browserify.org/) or [webpack](https://webpack.github.io/),
-though by default this module will alter it's API to no longer display or
-track deprecations.
-
-## API
-
-<!-- eslint-disable no-unused-vars -->
-
-```js
-var deprecate = require('depd')('my-module')
-```
-
-This library allows you to display deprecation messages to your users.
-This library goes above and beyond with deprecation warnings by
-introspection of the call stack (but only the bits that it is interested
-in).
-
-Instead of just warning on the first invocation of a deprecated
-function and never again, this module will warn on the first invocation
-of a deprecated function per unique call site, making it ideal to alert
-users of all deprecated uses across the code base, rather than just
-whatever happens to execute first.
-
-The deprecation warnings from this module also include the file and line
-information for the call into the module that the deprecated function was
-in.
-
-**NOTE** this library has a similar interface to the `debug` module, and
-this module uses the calling file to get the boundary for the call stacks,
-so you should always create a new `deprecate` object in each file and not
-within some central file.
-
-### depd(namespace)
-
-Create a new deprecate function that uses the given namespace name in the
-messages and will display the call site prior to the stack entering the
-file this function was called from. It is highly suggested you use the
-name of your module as the namespace.
-
-### deprecate(message)
-
-Call this function from deprecated code to display a deprecation message.
-This message will appear once per unique caller site. Caller site is the
-first call site in the stack in a different file from the caller of this
-function.
-
-If the message is omitted, a message is generated for you based on the site
-of the `deprecate()` call and will display the name of the function called,
-similar to the name displayed in a stack trace.
-
-### deprecate.function(fn, message)
-
-Call this function to wrap a given function in a deprecation message on any
-call to the function. An optional message can be supplied to provide a custom
-message.
-
-### deprecate.property(obj, prop, message)
-
-Call this function to wrap a given property on object in a deprecation message
-on any accessing or setting of the property. An optional message can be supplied
-to provide a custom message.
-
-The method must be called on the object where the property belongs (not
-inherited from the prototype).
-
-If the property is a data descriptor, it will be converted to an accessor
-descriptor in order to display the deprecation message.
-
-### process.on('deprecation', fn)
-
-This module will allow easy capturing of deprecation errors by emitting the
-errors as the type "deprecation" on the global `process`. If there are no
-listeners for this type, the errors are written to STDERR as normal, but if
-there are any listeners, nothing will be written to STDERR and instead only
-emitted. From there, you can write the errors in a different format or to a
-logging source.
-
-The error represents the deprecation and is emitted only once with the same
-rules as writing to STDERR. The error has the following properties:
-
-  - `message` - This is the message given by the library
-  - `name` - This is always `'DeprecationError'`
-  - `namespace` - This is the namespace the deprecation came from
-  - `stack` - This is the stack of the call to the deprecated thing
-
-Example `error.stack` output:
-
-```
-DeprecationError: my-cool-module deprecated oldfunction
-    at Object.<anonymous> ([eval]-wrapper:6:22)
-    at Module._compile (module.js:456:26)
-    at evalScript (node.js:532:25)
-    at startup (node.js:80:7)
-    at node.js:902:3
-```
-
-### process.env.NO_DEPRECATION
-
-As a user of modules that are deprecated, the environment variable `NO_DEPRECATION`
-is provided as a quick solution to silencing deprecation warnings from being
-output. The format of this is similar to that of `DEBUG`:
-
-```sh
-$ NO_DEPRECATION=my-module,othermod node app.js
-```
-
-This will suppress deprecations from being output for "my-module" and "othermod".
-The value is a list of comma-separated namespaces. To suppress every warning
-across all namespaces, use the value `*` for a namespace.
-
-Providing the argument `--no-deprecation` to the `node` executable will suppress
-all deprecations (only available in Node.js 0.8 or higher).
-
-**NOTE** This will not suppress the deperecations given to any "deprecation"
-event listeners, just the output to STDERR.
-
-### process.env.TRACE_DEPRECATION
-
-As a user of modules that are deprecated, the environment variable `TRACE_DEPRECATION`
-is provided as a solution to getting more detailed location information in deprecation
-warnings by including the entire stack trace. The format of this is the same as
-`NO_DEPRECATION`:
-
-```sh
-$ TRACE_DEPRECATION=my-module,othermod node app.js
-```
-
-This will include stack traces for deprecations being output for "my-module" and
-"othermod". The value is a list of comma-separated namespaces. To trace every
-warning across all namespaces, use the value `*` for a namespace.
-
-Providing the argument `--trace-deprecation` to the `node` executable will trace
-all deprecations (only available in Node.js 0.8 or higher).
-
-**NOTE** This will not trace the deperecations silenced by `NO_DEPRECATION`.
-
-## Display
-
-![message](files/message.png)
-
-When a user calls a function in your library that you mark deprecated, they
-will see the following written to STDERR (in the given colors, similar colors
-and layout to the `debug` module):
-
-```
-bright cyan    bright yellow
-|              |          reset       cyan
-|              |          |           |
-▼              ▼          ▼           ▼
-my-cool-module deprecated oldfunction [eval]-wrapper:6:22
-▲              ▲          ▲           ▲
-|              |          |           |
-namespace      |          |           location of mycoolmod.oldfunction() call
-               |          deprecation message
-               the word "deprecated"
-```
-
-If the user redirects their STDERR to a file or somewhere that does not support
-colors, they see (similar layout to the `debug` module):
-
-```
-Sun, 15 Jun 2014 05:21:37 GMT my-cool-module deprecated oldfunction at [eval]-wrapper:6:22
-▲                             ▲              ▲          ▲              ▲
-|                             |              |          |              |
-timestamp of message          namespace      |          |             location of mycoolmod.oldfunction() call
-                                             |          deprecation message
-                                             the word "deprecated"
-```
-
-## Examples
-
-### Deprecating all calls to a function
-
-This will display a deprecated message about "oldfunction" being deprecated
-from "my-module" on STDERR.
-
-```js
-var deprecate = require('depd')('my-cool-module')
-
-// message automatically derived from function name
-// Object.oldfunction
-exports.oldfunction = deprecate.function(function oldfunction () {
-  // all calls to function are deprecated
-})
-
-// specific message
-exports.oldfunction = deprecate.function(function () {
-  // all calls to function are deprecated
-}, 'oldfunction')
-```
-
-### Conditionally deprecating a function call
-
-This will display a deprecated message about "weirdfunction" being deprecated
-from "my-module" on STDERR when called with less than 2 arguments.
-
-```js
-var deprecate = require('depd')('my-cool-module')
-
-exports.weirdfunction = function () {
-  if (arguments.length < 2) {
-    // calls with 0 or 1 args are deprecated
-    deprecate('weirdfunction args < 2')
-  }
-}
-```
-
-When calling `deprecate` as a function, the warning is counted per call site
-within your own module, so you can display different deprecations depending
-on different situations and the users will still get all the warnings:
-
-```js
-var deprecate = require('depd')('my-cool-module')
-
-exports.weirdfunction = function () {
-  if (arguments.length < 2) {
-    // calls with 0 or 1 args are deprecated
-    deprecate('weirdfunction args < 2')
-  } else if (typeof arguments[0] !== 'string') {
-    // calls with non-string first argument are deprecated
-    deprecate('weirdfunction non-string first arg')
-  }
-}
-```
-
-### Deprecating property access
-
-This will display a deprecated message about "oldprop" being deprecated
-from "my-module" on STDERR when accessed. A deprecation will be displayed
-when setting the value and when getting the value.
-
-```js
-var deprecate = require('depd')('my-cool-module')
-
-exports.oldprop = 'something'
-
-// message automatically derives from property name
-deprecate.property(exports, 'oldprop')
-
-// explicit message
-deprecate.property(exports, 'oldprop', 'oldprop >= 0.10')
-```
-
-## License
-
-[MIT](LICENSE)
-
-[appveyor-image]: https://badgen.net/appveyor/ci/dougwilson/nodejs-depd/master?label=windows
-[appveyor-url]: https://ci.appveyor.com/project/dougwilson/nodejs-depd
-[coveralls-image]: https://badgen.net/coveralls/c/github/dougwilson/nodejs-depd/master
-[coveralls-url]: https://coveralls.io/r/dougwilson/nodejs-depd?branch=master
-[node-image]: https://badgen.net/npm/node/depd
-[node-url]: https://nodejs.org/en/download/
-[npm-downloads-image]: https://badgen.net/npm/dm/depd
-[npm-url]: https://npmjs.org/package/depd
-[npm-version-image]: https://badgen.net/npm/v/depd
-[travis-image]: https://badgen.net/travis/dougwilson/nodejs-depd/master?label=linux
-[travis-url]: https://travis-ci.org/dougwilson/nodejs-depd

package/node_modules/domelementtype/readme.md

@@ -1 +0,0 @@
-All the types of nodes in htmlparser2's DOM.

package/node_modules/domhandler/readme.md

@@ -1,92 +0,0 @@
-# domhandler [![Build Status](https://travis-ci.com/fb55/domhandler.svg?branch=master)](https://travis-ci.com/fb55/domhandler)
-
-The DOM handler creates a tree containing all nodes of a page.
-The tree can be manipulated using the [domutils](https://github.com/fb55/domutils)
-or [cheerio](https://github.com/cheeriojs/cheerio) libraries and
-rendered using [dom-serializer](https://github.com/cheeriojs/dom-serializer) .
-
-## Usage
-
-```javascript
-const handler = new DomHandler([ <func> callback(err, dom), ] [ <obj> options ]);
-// const parser = new Parser(handler[, options]);
-```
-
-Available options are described below.
-
-## Example
-
-```javascript
-const { Parser } = require("htmlparser2");
-const { DomHandler } = require("domhandler");
-const rawHtml =
-    "Xyz <script language= javascript>var foo = '<<bar>>';</script><!--<!-- Waah! -- -->";
-const handler = new DomHandler((error, dom) => {
-    if (error) {
-        // Handle error
-    } else {
-        // Parsing completed, do something
-        console.log(dom);
-    }
-});
-const parser = new Parser(handler);
-parser.write(rawHtml);
-parser.end();
-```
-
-Output:
-
-```javascript
-[
-    {
-        data: "Xyz ",
-        type: "text",
-    },
-    {
-        type: "script",
-        name: "script",
-        attribs: {
-            language: "javascript",
-        },
-        children: [
-            {
-                data: "var foo = '<bar>';<",
-                type: "text",
-            },
-        ],
-    },
-    {
-        data: "<!-- Waah! -- ",
-        type: "comment",
-    },
-];
-```
-
-## Option: `withStartIndices`
-
-Add a `startIndex` property to nodes.
-When the parser is used in a non-streaming fashion, `startIndex` is an integer
-indicating the position of the start of the node in the document.
-The default value is `false`.
-
-## Option: `withEndIndices`
-
-Add an `endIndex` property to nodes.
-When the parser is used in a non-streaming fashion, `endIndex` is an integer
-indicating the position of the end of the node in the document.
-The default value is `false`.
-
----
-
-License: BSD-2-Clause
-
-## Security contact information
-
-To report a security vulnerability, please use the [Tidelift security contact](https://tidelift.com/security).
-Tidelift will coordinate the fix and disclosure.
-
-## `domhandler` for enterprise
-
-Available as part of the Tidelift Subscription
-
-The maintainers of `domhandler` and thousands of other packages are working with Tidelift to deliver commercial support and maintenance for the open source dependencies you use to build your applications. Save time, reduce risk, and improve code health, while paying the maintainers of the exact dependencies you use. [Learn more.](https://tidelift.com/subscription/pkg/npm-domhandler?utm_source=npm-domhandler&utm_medium=referral&utm_campaign=enterprise&utm_term=repo)

package/node_modules/domutils/readme.md

@@ -1,31 +0,0 @@
-# domutils [![Node.js CI](https://github.com/fb55/domutils/actions/workflows/nodejs-test.yml/badge.svg)](https://github.com/fb55/domutils/actions/workflows/nodejs-test.yml)
-
-Utilities for working with [htmlparser2](https://github.com/fb55/htmlparser2)'s DOM.
-
-All functions are exported as a single module. Look [through the docs](https://domutils.js.org/modules.html) to see what is available.
-
-## Ecosystem
-
-| Name                                                          | Description                                             |
-| ------------------------------------------------------------- | ------------------------------------------------------- |
-| [htmlparser2](https://github.com/fb55/htmlparser2)            | Fast & forgiving HTML/XML parser                        |
-| [domhandler](https://github.com/fb55/domhandler)              | Handler for htmlparser2 that turns documents into a DOM |
-| [domutils](https://github.com/fb55/domutils)                  | Utilities for working with domhandler's DOM             |
-| [css-select](https://github.com/fb55/css-select)              | CSS selector engine, compatible with domhandler's DOM   |
-| [cheerio](https://github.com/cheeriojs/cheerio)               | The jQuery API for domhandler's DOM                     |
-| [dom-serializer](https://github.com/cheeriojs/dom-serializer) | Serializer for domhandler's DOM                         |
-
----
-
-License: BSD-2-Clause
-
-## Security contact information
-
-To report a security vulnerability, please use the [Tidelift security contact](https://tidelift.com/security).
-Tidelift will coordinate the fix and disclosure.
-
-## `domutils` for enterprise
-
-Available as part of the Tidelift Subscription
-
-The maintainers of `domutils` and thousands of other packages are working with Tidelift to deliver commercial support and maintenance for the open source dependencies you use to build your applications. Save time, reduce risk, and improve code health, while paying the maintainers of the exact dependencies you use. [Learn more.](https://tidelift.com/subscription/pkg/npm-domutils?utm_source=npm-domutils&utm_medium=referral&utm_campaign=enterprise&utm_term=repo)

package/node_modules/entities/readme.md

@@ -1,122 +0,0 @@
-# entities [![NPM version](https://img.shields.io/npm/v/entities.svg)](https://npmjs.org/package/entities) [![Downloads](https://img.shields.io/npm/dm/entities.svg)](https://npmjs.org/package/entities) [![Node.js CI](https://github.com/fb55/entities/actions/workflows/nodejs-test.yml/badge.svg)](https://github.com/fb55/entities/actions/workflows/nodejs-test.yml)
-
-Encode & decode HTML & XML entities with ease & speed.
-
-## Features
-
--   😇 Tried and true: `entities` is used by many popular libraries; eg.
-    [`htmlparser2`](https://github.com/fb55/htmlparser2), the official
-    [AWS SDK](https://github.com/aws/aws-sdk-js-v3) and
-    [`commonmark`](https://github.com/commonmark/commonmark.js) use it to
-    process HTML entities.
--   ⚡️ Fast: `entities` is the fastest library for decoding HTML entities (as
-    of April 2022); see [performance](#performance).
--   🎛 Configurable: Get an output tailored for your needs. You are fine with
-    UTF8? That'll save you some bytes. Prefer to only have ASCII characters? We
-    can do that as well!
-
-## How to…
-
-### …install `entities`
-
-    npm install entities
-
-### …use `entities`
-
-```javascript
-const entities = require("entities");
-
-// Encoding
-entities.escapeUTF8("& ü"); // "& ü"
-entities.encodeXML("& ü"); // "& ü"
-entities.encodeHTML("& ü"); // "& ü"
-
-// Decoding
-entities.decodeXML("asdf & ÿ ü '"); // "asdf & ÿ ü '"
-entities.decodeHTML("asdf & ÿ ü '"); // "asdf & ÿ ü '"
-```
-
-## Performance
-
-This is how `entities` compares to other libraries on a very basic benchmark
-(see `scripts/benchmark.ts`, for 10,000,000 iterations; **lower is better**):
-
-| Library        | Version | `decode` perf | `encode` perf | `escape` perf |
-| -------------- | ------- | ------------- | ------------- | ------------- |
-| entities       | `3.0.1` | 1.418s        | 6.786s        | 2.196s        |
-| html-entities  | `2.3.2` | 2.530s        | 6.829s        | 2.415s        |
-| he             | `1.2.0` | 5.800s        | 24.237s       | 3.624s        |
-| parse-entities | `3.0.0` | 9.660s        | N/A           | N/A           |
-
----
-
-## FAQ
-
-> What methods should I actually use to encode my documents?
-
-If your target supports UTF-8, the `escapeUTF8` method is going to be your best
-choice. Otherwise, use either `encodeHTML` or `encodeXML` based on whether
-you're dealing with an HTML or an XML document.
-
-You can have a look at the options for the `encode` and `decode` methods to see
-everything you can configure.
-
-> When should I use strict decoding?
-
-When strict decoding, entities not terminated with a semicolon will be ignored.
-This is helpful for decoding entities in legacy environments.
-
-> Why should I use `entities` instead of alternative modules?
-
-As of April 2022, `entities` is a bit faster than other modules. Still, this is
-not a very differentiated space and other modules can catch up.
-
-**More importantly**, you might already have `entities` in your dependency graph
-(as a dependency of eg. `cheerio`, or `htmlparser2`), and including it directly
-might not even increase your bundle size. The same is true for other entity
-libraries, so have a look through your `node_modules` directory!
-
-> Does `entities` support tree shaking?
-
-Yes! `entities` ships as both a CommonJS and a ES module. Note that for best
-results, you should not use the `encode` and `decode` functions, as they wrap
-around a number of other functions, all of which will remain in the bundle.
-Instead, use the functions that you need directly.
-
----
-
-## Acknowledgements
-
-This library wouldn't be possible without the work of these individuals. Thanks
-to
-
--   [@mathiasbynens](https://github.com/mathiasbynens) for his explanations
-    about character encodings, and his library `he`, which was one of the
-    inspirations for `entities`
--   [@inikulin](https://github.com/inikulin) for his work on optimized tries for
-    decoding HTML entities for the `parse5` project
--   [@mdevils](https://github.com/mdevils) for taking on the challenge of
-    producing a quick entity library with his `html-entities` library.
-    `entities` would be quite a bit slower if there wasn't any competition.
-    Right now `entities` is on top, but we'll see how long that lasts!
-
----
-
-License: BSD-2-Clause
-
-## Security contact information
-
-To report a security vulnerability, please use the
-[Tidelift security contact](https://tidelift.com/security). Tidelift will
-coordinate the fix and disclosure.
-
-## `entities` for enterprise
-
-Available as part of the Tidelift Subscription
-
-The maintainers of `entities` and thousands of other packages are working with
-Tidelift to deliver commercial support and maintenance for the open source
-dependencies you use to build your applications. Save time, reduce risk, and
-improve code health, while paying the maintainers of the exact dependencies you
-use.
-[Learn more.](https://tidelift.com/subscription/pkg/npm-entities?utm_source=npm-entities&utm_medium=referral&utm_campaign=enterprise&utm_term=repo)

package/node_modules/escalade/license

@@ -1,9 +0,0 @@
-MIT License
-
-Copyright (c) Luke Edwards <luke.edwards05@gmail.com> (lukeed.com)
-
-Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.