@qqbrowser/openclaw-qbot 0.0.148 → 0.10.1

package/node_modules/path-to-regexp/Readme.md

@@ -1,224 +0,0 @@
-# Path-to-RegExp
-
-> Turn a path string such as `/user/:name` into a regular expression.
-
-[![NPM version][npm-image]][npm-url]
-[![NPM downloads][downloads-image]][downloads-url]
-[![Build status][build-image]][build-url]
-[![Build coverage][coverage-image]][coverage-url]
-[![License][license-image]][license-url]
-
-## Installation
-
-```
-npm install path-to-regexp --save
-```
-
-## Usage
-
-```js
-const {
-  match,
-  pathToRegexp,
-  compile,
-  parse,
-  stringify,
-} = require("path-to-regexp");
-```
-
-### Parameters
-
-Parameters match arbitrary strings in a path by matching up to the end of the segment, or up to any proceeding tokens. They are defined by prefixing a colon to the parameter name (`:foo`). Parameter names can use any valid JavaScript identifier, or be double quoted to use other characters (`:"param-name"`).
-
-```js
-const fn = match("/:foo/:bar");
-
-fn("/test/route");
-//=> { path: '/test/route', params: { foo: 'test', bar: 'route' } }
-```
-
-### Wildcard
-
-Wildcard parameters match one or more characters across multiple segments. They are defined the same way as regular parameters, but are prefixed with an asterisk (`*foo`).
-
-```js
-const fn = match("/*splat");
-
-fn("/bar/baz");
-//=> { path: '/bar/baz', params: { splat: [ 'bar', 'baz' ] } }
-```
-
-### Optional
-
-Braces can be used to define parts of the path that are optional.
-
-```js
-const fn = match("/users{/:id}/delete");
-
-fn("/users/delete");
-//=> { path: '/users/delete', params: {} }
-
-fn("/users/123/delete");
-//=> { path: '/users/123/delete', params: { id: '123' } }
-```
-
-## Match
-
-The `match` function returns a function for matching strings against a path:
-
-- **path** String, `TokenData` object, or array of strings and `TokenData` objects.
-- **options** _(optional)_ (Extends [pathToRegexp](#pathToRegexp) options)
-  - **decode** Function for decoding strings to params, or `false` to disable all processing. (default: `decodeURIComponent`)
-
-```js
-const fn = match("/foo/:bar");
-```
-
-**Please note:** `path-to-regexp` is intended for ordered data (e.g. paths, hosts). It can not handle arbitrarily ordered data (e.g. query strings, URL fragments, JSON, etc).
-
-## PathToRegexp
-
-The `pathToRegexp` function returns the `regexp` for matching strings against paths, and an array of `keys` for understanding the `RegExp#exec` matches.
-
-- **path** String, `TokenData` object, or array of strings and `TokenData` objects.
-- **options** _(optional)_ (See [parse](#parse) for more options)
-  - **sensitive** Regexp will be case sensitive. (default: `false`)
-  - **end** Validate the match reaches the end of the string. (default: `true`)
-  - **delimiter** The default delimiter for segments, e.g. `[^/]` for `:named` parameters. (default: `'/'`)
-  - **trailing** Allows optional trailing delimiter to match. (default: `true`)
-
-```js
-const { regexp, keys } = pathToRegexp("/foo/:bar");
-
-regexp.exec("/foo/123"); //=> ["/foo/123", "123"]
-```
-
-## Compile ("Reverse" Path-To-RegExp)
-
-The `compile` function will return a function for transforming parameters into a valid path:
-
-- **path** A string or `TokenData` object.
-- **options** (See [parse](#parse) for more options)
-  - **delimiter** The default delimiter for segments, e.g. `[^/]` for `:named` parameters. (default: `'/'`)
-  - **encode** Function for encoding input strings for output into the path, or `false` to disable entirely. (default: `encodeURIComponent`)
-
-```js
-const toPath = compile("/user/:id");
-
-toPath({ id: "name" }); //=> "/user/name"
-toPath({ id: "café" }); //=> "/user/caf%C3%A9"
-
-const toPathRepeated = compile("/*segment");
-
-toPathRepeated({ segment: ["foo"] }); //=> "/foo"
-toPathRepeated({ segment: ["a", "b", "c"] }); //=> "/a/b/c"
-
-// When disabling `encode`, you need to make sure inputs are encoded correctly. No arrays are accepted.
-const toPathRaw = compile("/user/:id", { encode: false });
-
-toPathRaw({ id: "%3A%2F" }); //=> "/user/%3A%2F"
-```
-
-## Stringify
-
-Transform a `TokenData` object to a Path-to-RegExp string.
-
-- **data** A `TokenData` object.
-
-```js
-const data = {
-  tokens: [
-    { type: "text", value: "/" },
-    { type: "param", name: "foo" },
-  ],
-};
-
-const path = stringify(data); //=> "/:foo"
-```
-
-## Developers
-
-- If you are rewriting paths with match and compile, consider using `encode: false` and `decode: false` to keep raw paths passed around.
-- To ensure matches work on paths containing characters usually encoded, such as emoji, consider using [encodeurl](https://github.com/pillarjs/encodeurl) for `encodePath`.
-
-### Parse
-
-The `parse` function accepts a string and returns `TokenData`, which can be used with `match` and `compile`.
-
-- **path** A string.
-- **options** _(optional)_
-  - **encodePath** A function for encoding input strings. (default: `x => x`, recommended: [`encodeurl`](https://github.com/pillarjs/encodeurl))
-
-### Tokens
-
-`TokenData` has two properties:
-
-- **tokens** A sequence of tokens, currently of types `text`, `param`, `wildcard`, or `group`.
-- **originalPath** The original path used with `parse`, shown in error messages to assist debugging.
-
-### Custom path
-
-In some applications you may not be able to use the `path-to-regexp` syntax, but you still want to use this library for `match` and `compile`. For example:
-
-```js
-import { match } from "path-to-regexp";
-
-const tokens = [
-  { type: "text", value: "/" },
-  { type: "param", name: "foo" },
-];
-const originalPath = "/[foo]"; // To help debug error messages.
-const path = { tokens, originalPath };
-const fn = match(path);
-
-fn("/test"); //=> { path: '/test', params: { foo: 'test' } }
-```
-
-## Errors
-
-An effort has been made to ensure ambiguous paths from previous releases throw an error. This means you might be seeing an error when things worked before.
-
-### Missing parameter name
-
-Parameter names must be provided after `:` or `*`, for example `/*path`. They can be valid JavaScript identifiers (e.g. `:myName`) or JSON strings (`:"my-name"`).
-
-### Unexpected `?` or `+`
-
-In past releases, `?`, `*`, and `+` were used to denote optional or repeating parameters. As an alternative, try these:
-
-- For optional (`?`), use braces: `/file{.:ext}`.
-- For one or more (`+`), use a wildcard: `/*path`.
-- For zero or more (`*`), use both: `/files{/*path}`.
-
-### Unexpected `(`, `)`, `[`, `]`, etc.
-
-Previous versions of Path-to-RegExp used these for RegExp features. This version no longer supports them so they've been reserved to avoid ambiguity. To match these characters literally, escape them with a backslash, e.g. `"\\("`.
-
-### Unterminated quote
-
-Parameter names can be wrapped in double quote characters, and this error means you forgot to close the quote character. For example, `:"foo`.
-
-### Express <= 4.x
-
-Path-To-RegExp breaks compatibility with Express <= `4.x` in the following ways:
-
-- The wildcard `*` must have a name and matches the behavior of parameters `:`.
-- The optional character `?` is no longer supported, use braces instead: `/:file{.:ext}`.
-- Regexp characters are not supported.
-- Some characters have been reserved to avoid confusion during upgrade (`()[]?+!`).
-- Parameter names now support valid JavaScript identifiers, or quoted like `:"this"`.
-
-## License
-
-MIT
-
-[npm-image]: https://img.shields.io/npm/v/path-to-regexp
-[npm-url]: https://npmjs.org/package/path-to-regexp
-[downloads-image]: https://img.shields.io/npm/dm/path-to-regexp
-[downloads-url]: https://npmjs.org/package/path-to-regexp
-[build-image]: https://img.shields.io/github/actions/workflow/status/pillarjs/path-to-regexp/ci.yml?branch=master
-[build-url]: https://github.com/pillarjs/path-to-regexp/actions/workflows/ci.yml?query=branch%3Amaster
-[coverage-image]: https://img.shields.io/codecov/c/gh/pillarjs/path-to-regexp
-[coverage-url]: https://codecov.io/gh/pillarjs/path-to-regexp
-[license-image]: http://img.shields.io/npm/l/path-to-regexp.svg?style=flat
-[license-url]: LICENSE.md

package/node_modules/pino-std-serializers/Readme.md

@@ -1,182 +0,0 @@
-# pino-std-serializers  [![CI](https://github.com/pinojs/pino-std-serializers/workflows/CI/badge.svg)](https://github.com/pinojs/pino-std-serializers/actions?query=workflow%3ACI)
-
-This module provides a set of standard object serializers for the
-[Pino](https://getpino.io) logger.
-
-## Serializers
-
-### `exports.err(error)`
-Serializes an `Error` like object. Returns an object:
-
-```js
-{
-  type: 'string', // The name of the object's constructor.
-  message: 'string', // The supplied error message.
-  stack: 'string', // The stack when the error was generated.
-  raw: Error  // Non-enumerable, i.e. will not be in the output, original
-              // Error object. This is available for subsequent serializers
-              // to use.
-  [...any additional Enumerable property the original Error had]
-}
-```
-
-Any other extra properties, e.g. `statusCode`, that have been attached to the
-object will also be present on the serialized object.
-
-If the error object has a [`cause`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/cause) property, the `cause`'s `message` and `stack` will be appended to the top-level `message` and `stack`. All other parameters that belong to the `error.cause` object will be omitted.
-
-Example:
-
-```js
-const serializer = require('pino-std-serializers').err;
-
-const innerError = new Error("inner error");
-innerError.isInner = true;
-const outerError = new Error("outer error", { cause: innerError });
-outerError.isInner = false;
-
-const serialized = serializer(outerError);
-/* Result:
-{
-  "type": "Error",
-  "message": "outer error: inner error",
-  "isInner": false,
-  "stack": "Error: outer error
-        at <...omitted..>
-    caused by: Error: inner error
-        at <...omitted..>
-}
- */
-```
-
-### `exports.errWithCause(error)`
-Serializes an `Error` like object, including any `error.cause`. Returns an object:
-
-```js
-{
-  type: 'string', // The name of the object's constructor.
-  message: 'string', // The supplied error message.
-  stack: 'string', // The stack when the error was generated.
-  cause?: Error, // If the original error had an error.cause, it will be serialized here
-  raw: Error  // Non-enumerable, i.e. will not be in the output, original
-              // Error object. This is available for subsequent serializers
-              // to use.
-  [...any additional Enumerable property the original Error had]
-}
-```
-
-Any other extra properties, e.g. `statusCode`, that have been attached to the object will also be present on the serialized object.
-
-Example:
-```javascript
-const serializer = require('pino-std-serializers').errWithCause;
-
-const innerError = new Error("inner error");
-innerError.isInner = true;
-const outerError = new Error("outer error", { cause: innerError });
-outerError.isInner = false;
-
-const serialized = serializer(outerError);
-/* Result:
-{
-  "type": "Error",
-  "message": "outer error",
-  "isInner": false,
-  "stack": "Error: outer error
-    at <...omitted..>",
-  "cause": {
-    "type": "Error",
-    "message": "inner error",
-    "isInner": true,
-    "stack": "Error: inner error
-      at <...omitted..>"
-  },
-}
- */
-```
-
-### `exports.mapHttpResponse(response)`
-Used internally by Pino for general response logging. Returns an object:
-
-```js
-{
-  res: {}
-}
-```
-
-Where `res` is the `response` as serialized by the standard response serializer.
-
-### `exports.mapHttpRequest(request)`
-Used internall by Pino for general request logging. Returns an object:
-
-```js
-{
-  req: {}
-}
-```
-
-Where `req` is the `request` as serialized by the standard request serializer.
-
-### `exports.req(request)`
-The default `request` serializer. Returns an object:
-
-```js
-{
-  id: 'string', // Defaults to `undefined`, unless there is an `id` property
-                // already attached to the `request` object or to the `request.info`
-                // object. Attach a synchronous function
-                // to the `request.id` that returns an identifier to have
-                // the value filled.
-  method: 'string',
-  url: 'string', // the request pathname (as per req.url in core HTTP)
-  query: 'object', // the request query (as per req.query in express or hapi)
-  params: 'object', // the request params (as per req.params in express or hapi)
-  headers: Object, // a reference to the `headers` object from the request
-                   // (as per req.headers in core HTTP)
-  remoteAddress: 'string',
-  remotePort: Number,
-  raw: Object // Non-enumerable, i.e. will not be in the output, original
-              // request object. This is available for subsequent serializers
-              // to use. In cases where the `request` input already has
-              // a `raw` property this will replace the original `request.raw`
-              // property
-}
-```
-
-### `exports.res(response)`
-The default `response` serializer. Returns an object:
-
-```js
-{
-  statusCode: Number, // Response status code, will be null before headers are flushed
-  headers: Object, // The headers to be sent in the response.
-  raw: Object // Non-enumerable, i.e. will not be in the output, original
-              // response object. This is available for subsequent serializers
-              // to use.
-}
-```
-
-### `exports.wrapErrorSerializer(customSerializer)`
-A utility method for wrapping the default error serializer. This allows
-custom serializers to work with the already serialized object.
-
-The `customSerializer` accepts one parameter — the newly serialized error
-object — and returns the new (or updated) error object.
-
-### `exports.wrapRequestSerializer(customSerializer)`
-A utility method for wrapping the default request serializer. This allows
-custom serializers to work with the already serialized object.
-
-The `customSerializer` accepts one parameter — the newly serialized request
-object — and returns the new (or updated) request object.
-
-### `exports.wrapResponseSerializer(customSerializer)`
-A utility method for wrapping the default response serializer. This allows
-custom serializers to work with the already serialized object.
-
-The `customSerializer` accepts one parameter — the newly serialized response
-object — and returns the new (or updated) response object.
-
-## License
-
-MIT License

package/node_modules/process-nextick-args/license.md

@@ -1,19 +0,0 @@
-# Copyright (c) 2015 Calvin Metcalf
-
-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.**

package/node_modules/process-nextick-args/readme.md

@@ -1,18 +0,0 @@
-process-nextick-args
-=====
-
-[![Build Status](https://travis-ci.org/calvinmetcalf/process-nextick-args.svg?branch=master)](https://travis-ci.org/calvinmetcalf/process-nextick-args)
-
-```bash
-npm install --save process-nextick-args
-```
-
-Always be able to pass arguments to process.nextTick, no matter the platform
-
-```js
-var pna = require('process-nextick-args');
-
-pna.nextTick(function (a, b, c) {
-  console.log(a, b, c);
-}, 'step', 3,  'profit');
-```

package/node_modules/proper-lockfile/node_modules/retry/License

@@ -1,21 +0,0 @@
-Copyright (c) 2011:
-Tim Koschützki (tim@debuggable.com)
-Felix Geisendörfer (felix@debuggable.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.

package/node_modules/proper-lockfile/node_modules/retry/README.md

@@ -1,227 +0,0 @@
-<!-- badges/ -->
-[![Build Status](https://secure.travis-ci.org/tim-kos/node-retry.png?branch=master)](http://travis-ci.org/tim-kos/node-retry "Check this project's build status on TravisCI")
-[![codecov](https://codecov.io/gh/tim-kos/node-retry/branch/master/graph/badge.svg)](https://codecov.io/gh/tim-kos/node-retry)
-<!-- /badges -->
-
-# retry
-
-Abstraction for exponential and custom retry strategies for failed operations.
-
-## Installation
-
-    npm install retry
-
-## Current Status
-
-This module has been tested and is ready to be used.
-
-## Tutorial
-
-The example below will retry a potentially failing `dns.resolve` operation
-`10` times using an exponential backoff strategy. With the default settings, this
-means the last attempt is made after `17 minutes and 3 seconds`.
-
-``` javascript
-var dns = require('dns');
-var retry = require('retry');
-
-function faultTolerantResolve(address, cb) {
-  var operation = retry.operation();
-
-  operation.attempt(function(currentAttempt) {
-    dns.resolve(address, function(err, addresses) {
-      if (operation.retry(err)) {
-        return;
-      }
-
-      cb(err ? operation.mainError() : null, addresses);
-    });
-  });
-}
-
-faultTolerantResolve('nodejs.org', function(err, addresses) {
-  console.log(err, addresses);
-});
-```
-
-Of course you can also configure the factors that go into the exponential
-backoff. See the API documentation below for all available settings.
-currentAttempt is an int representing the number of attempts so far.
-
-``` javascript
-var operation = retry.operation({
-  retries: 5,
-  factor: 3,
-  minTimeout: 1 * 1000,
-  maxTimeout: 60 * 1000,
-  randomize: true,
-});
-```
-
-## API
-
-### retry.operation([options])
-
-Creates a new `RetryOperation` object. `options` is the same as `retry.timeouts()`'s `options`, with two additions:
-
-* `forever`: Whether to retry forever, defaults to `false`.
-* `unref`: Whether to [unref](https://nodejs.org/api/timers.html#timers_unref) the setTimeout's, defaults to `false`.
-* `maxRetryTime`: The maximum time (in milliseconds) that the retried operation is allowed to run. Default is `Infinity`.  
-
-### retry.timeouts([options])
-
-Returns an array of timeouts. All time `options` and return values are in
-milliseconds. If `options` is an array, a copy of that array is returned.
-
-`options` is a JS object that can contain any of the following keys:
-
-* `retries`: The maximum amount of times to retry the operation. Default is `10`. Seting this to `1` means `do it once, then retry it once`.
-* `factor`: The exponential factor to use. Default is `2`.
-* `minTimeout`: The number of milliseconds before starting the first retry. Default is `1000`.
-* `maxTimeout`: The maximum number of milliseconds between two retries. Default is `Infinity`.
-* `randomize`: Randomizes the timeouts by multiplying with a factor between `1` to `2`. Default is `false`.
-
-The formula used to calculate the individual timeouts is:
-
-```
-Math.min(random * minTimeout * Math.pow(factor, attempt), maxTimeout)
-```
-
-Have a look at [this article][article] for a better explanation of approach.
-
-If you want to tune your `factor` / `times` settings to attempt the last retry
-after a certain amount of time, you can use wolfram alpha. For example in order
-to tune for `10` attempts in `5 minutes`, you can use this equation:
-
-![screenshot](https://github.com/tim-kos/node-retry/raw/master/equation.gif)
-
-Explaining the various values from left to right:
-
-* `k = 0 ... 9`:  The `retries` value (10)
-* `1000`: The `minTimeout` value in ms (1000)
-* `x^k`: No need to change this, `x` will be your resulting factor
-* `5 * 60 * 1000`: The desired total amount of time for retrying in ms (5 minutes)
-
-To make this a little easier for you, use wolfram alpha to do the calculations:
-
-<http://www.wolframalpha.com/input/?i=Sum%5B1000*x^k%2C+{k%2C+0%2C+9}%5D+%3D+5+*+60+*+1000>
-
-[article]: http://dthain.blogspot.com/2009/02/exponential-backoff-in-distributed.html
-
-### retry.createTimeout(attempt, opts)
-
-Returns a new `timeout` (integer in milliseconds) based on the given parameters.
-
-`attempt` is an integer representing for which retry the timeout should be calculated. If your retry operation was executed 4 times you had one attempt and 3 retries. If you then want to calculate a new timeout, you should set `attempt` to 4 (attempts are zero-indexed).
-
-`opts` can include `factor`, `minTimeout`, `randomize` (boolean) and `maxTimeout`. They are documented above.
-
-`retry.createTimeout()` is used internally by `retry.timeouts()` and is public for you to be able to create your own timeouts for reinserting an item, see [issue #13](https://github.com/tim-kos/node-retry/issues/13).
-
-### retry.wrap(obj, [options], [methodNames])
-
-Wrap all functions of the `obj` with retry. Optionally you can pass operation options and
-an array of method names which need to be wrapped.
-
-```
-retry.wrap(obj)
-
-retry.wrap(obj, ['method1', 'method2'])
-
-retry.wrap(obj, {retries: 3})
-
-retry.wrap(obj, {retries: 3}, ['method1', 'method2'])
-```
-The `options` object can take any options that the usual call to `retry.operation` can take.
-
-### new RetryOperation(timeouts, [options])
-
-Creates a new `RetryOperation` where `timeouts` is an array where each value is
-a timeout given in milliseconds.
-
-Available options:
-* `forever`: Whether to retry forever, defaults to `false`.
-* `unref`: Wether to [unref](https://nodejs.org/api/timers.html#timers_unref) the setTimeout's, defaults to `false`.
-
-If `forever` is true, the following changes happen:
-* `RetryOperation.errors()` will only output an array of one item: the last error.
-* `RetryOperation` will repeatedly use the `timeouts` array. Once all of its timeouts have been used up, it restarts with the first timeout, then uses the second and so on.
-
-#### retryOperation.errors()
-
-Returns an array of all errors that have been passed to `retryOperation.retry()` so far. The
-returning array has the errors ordered chronologically based on when they were passed to
-`retryOperation.retry()`, which means the first passed error is at index zero and the last is
-at the last index.
-
-#### retryOperation.mainError()
-
-A reference to the error object that occured most frequently. Errors are
-compared using the `error.message` property.
-
-If multiple error messages occured the same amount of time, the last error
-object with that message is returned.
-
-If no errors occured so far, the value is `null`.
-
-#### retryOperation.attempt(fn, timeoutOps)
-
-Defines the function `fn` that is to be retried and executes it for the first
-time right away. The `fn` function can receive an optional `currentAttempt` callback that represents the number of attempts to execute `fn` so far.
-
-Optionally defines `timeoutOps` which is an object having a property `timeout` in miliseconds and a property `cb` callback function.
-Whenever your retry operation takes longer than `timeout` to execute, the timeout callback function `cb` is called.
-
-
-#### retryOperation.try(fn)
-
-This is an alias for `retryOperation.attempt(fn)`. This is deprecated. Please use `retryOperation.attempt(fn)` instead.
-
-#### retryOperation.start(fn)
-
-This is an alias for `retryOperation.attempt(fn)`. This is deprecated. Please use `retryOperation.attempt(fn)` instead.
-
-#### retryOperation.retry(error)
-
-Returns `false` when no `error` value is given, or the maximum amount of retries
-has been reached.
-
-Otherwise it returns `true`, and retries the operation after the timeout for
-the current attempt number.
-
-#### retryOperation.stop()
-
-Allows you to stop the operation being retried. Useful for aborting the operation on a fatal error etc.
-
-#### retryOperation.reset()
-
-Resets the internal state of the operation object, so that you can call `attempt()` again as if this was a new operation object.
-
-#### retryOperation.attempts()
-
-Returns an int representing the number of attempts it took to call `fn` before it was successful.
-
-## License
-
-retry is licensed under the MIT license.
-
-
-# Changelog
-
-0.10.0 Adding `stop` functionality, thanks to @maxnachlinger.
-
-0.9.0 Adding `unref` functionality, thanks to @satazor.
-
-0.8.0 Implementing retry.wrap.
-
-0.7.0 Some bug fixes and made retry.createTimeout() public. Fixed issues [#10](https://github.com/tim-kos/node-retry/issues/10), [#12](https://github.com/tim-kos/node-retry/issues/12), and [#13](https://github.com/tim-kos/node-retry/issues/13).
-
-0.6.0 Introduced optional timeOps parameter for the attempt() function which is an object having a property timeout in milliseconds and a property cb callback function. Whenever your retry operation takes longer than timeout to execute, the timeout callback function cb is called.
-
-0.5.0 Some minor refactoring.
-
-0.4.0 Changed retryOperation.try() to retryOperation.attempt(). Deprecated the aliases start() and try() for it.
-
-0.3.0 Added retryOperation.start() which is an alias for retryOperation.try().
-
-0.2.0 Added attempts() function and parameter to retryOperation.try() representing the number of attempts it took to call fn().