step-node-agent 3.20.2 → 3.21.0

package/node_modules/npm/man/man1/npm-update.1

@@ -1,4 +1,4 @@
-.TH "NPM\-UPDATE" "1" "April 2022" "" ""
+.TH "NPM\-UPDATE" "1" "December 2022" "" ""
 .SH "NAME"
 \fBnpm-update\fR \- Update a package
 .SS Synopsis

package/node_modules/npm/man/man1/npm-version.1

@@ -1,4 +1,4 @@
-.TH "NPM\-VERSION" "1" "April 2022" "" ""
+.TH "NPM\-VERSION" "1" "December 2022" "" ""
 .SH "NAME"
 \fBnpm-version\fR \- Bump a package version
 .SS Synopsis

package/node_modules/npm/man/man1/npm-view.1

@@ -1,4 +1,4 @@
-.TH "NPM\-VIEW" "1" "April 2022" "" ""
+.TH "NPM\-VIEW" "1" "December 2022" "" ""
 .SH "NAME"
 \fBnpm-view\fR \- View registry info
 .SS Synopsis

package/node_modules/npm/man/man1/npm-whoami.1

@@ -1,4 +1,4 @@
-.TH "NPM\-WHOAMI" "1" "April 2022" "" ""
+.TH "NPM\-WHOAMI" "1" "December 2022" "" ""
 .SH "NAME"
 \fBnpm-whoami\fR \- Display npm username
 .SS Synopsis

package/node_modules/npm/man/man1/npm.1

@@ -1,4 +1,4 @@
-.TH "NPM" "1" "April 2022" "" ""
+.TH "NPM" "1" "December 2022" "" ""
 .SH "NAME"
 \fBnpm\fR \- javascript package manager
 .SS Synopsis
@@ -10,7 +10,7 @@ npm <command> [args]
 .RE
 .SS Version
 .P
-6\.14\.17
+6\.14\.18
 .SS Description
 .P
 npm is the package manager for the Node JavaScript platform\.  It puts

package/node_modules/npm/man/man5/folders.5

@@ -1,4 +1,4 @@
-.TH "FOLDERS" "5" "April 2022" "" ""
+.TH "FOLDERS" "5" "December 2022" "" ""
 .SH "NAME"
 \fBfolders\fR \- Folder Structures Used by npm
 .SS Description

package/node_modules/npm/man/man5/install.5

@@ -1,6 +1,6 @@
-.TH "INSTALL" "5" "April 2022" "" ""
+.TH "INSTALL" "5" "December 2022" "" ""
 .SH "NAME"
-\fBinstall\fR \- Download and Install npm
+\fBinstall\fR \- Download and install node and npm
 .SS Description
 .P
 To publish and install packages to and from the public npm registry, you must install Node\.js and the npm command line interface using either a Node version manager or a Node installer\. \fBWe strongly recommend using a Node version manager to install Node\.js and npm\.\fR We do not recommend using a Node installer, since the Node installation process installs npm in a directory with local permissions and can cause permissions errors when you run npm packages globally\.

package/node_modules/npm/man/man5/npmrc.5

@@ -1,4 +1,4 @@
-.TH "NPMRC" "5" "April 2022" "" ""
+.TH "NPMRC" "5" "December 2022" "" ""
 .SH "NAME"
 \fBnpmrc\fR \- The npm config files
 .SS Description

package/node_modules/npm/man/man5/package-json.5

@@ -1,4 +1,4 @@
-.TH "PACKAGE\.JSON" "5" "April 2022" "" ""
+.TH "PACKAGE\.JSON" "5" "December 2022" "" ""
 .SH "NAME"
 \fBpackage.json\fR \- Specifics of npm's package\.json handling
 .SS Description

package/node_modules/npm/man/man5/package-lock-json.5

@@ -1,4 +1,4 @@
-.TH "PACKAGE\-LOCK\.JSON" "5" "April 2022" "" ""
+.TH "PACKAGE\-LOCK\.JSON" "5" "December 2022" "" ""
 .SH "NAME"
 \fBpackage-lock.json\fR \- A manifestation of the manifest
 .SS Description

package/node_modules/npm/man/man5/package-locks.5

@@ -1,4 +1,4 @@
-.TH "PACKAGE\-LOCKS" "5" "April 2022" "" ""
+.TH "PACKAGE\-LOCKS" "5" "December 2022" "" ""
 .SH "NAME"
 \fBpackage-locks\fR \- An explanation of npm lockfiles
 .SS Description

package/node_modules/npm/man/man5/shrinkwrap-json.5

@@ -1,6 +1,6 @@
-.TH "NPM\-SHRINKWRAP\.JSON" "5" "April 2022" "" ""
+.TH "SHRINKWRAP\.JSON" "5" "December 2022" "" ""
 .SH "NAME"
-\fBnpm-shrinkwrap.json\fR \- A publishable lockfile
+\fBshrinkwrap.json\fR \- A publishable lockfile
 .SS Description
 .P
 \fBnpm\-shrinkwrap\.json\fP is a file created by npm help \fBshrinkwrap\fP\|\. It is identical to

package/node_modules/npm/man/man7/config.7

@@ -1,4 +1,4 @@
-.TH "CONFIG" "7" "April 2022" "" ""
+.TH "CONFIG" "7" "December 2022" "" ""
 .SH "NAME"
 \fBconfig\fR \- More than you probably want to know about npm configuration
 .SS Description

package/node_modules/npm/man/man7/developers.7

@@ -1,4 +1,4 @@
-.TH "DEVELOPERS" "7" "April 2022" "" ""
+.TH "DEVELOPERS" "7" "December 2022" "" ""
 .SH "NAME"
 \fBdevelopers\fR \- Developer Guide
 .SS Description

package/node_modules/npm/man/man7/orgs.7

@@ -1,4 +1,4 @@
-.TH "ORGS" "7" "April 2022" "" ""
+.TH "ORGS" "7" "December 2022" "" ""
 .SH "NAME"
 \fBorgs\fR \- Working with Teams & Orgs
 .SS Description

package/node_modules/npm/man/man7/registry.7

@@ -1,4 +1,4 @@
-.TH "REGISTRY" "7" "April 2022" "" ""
+.TH "REGISTRY" "7" "December 2022" "" ""
 .SH "NAME"
 \fBregistry\fR \- The JavaScript Package Registry
 .SS Description
@@ -98,7 +98,5 @@ npm help config
 npm help npmrc
 .IP \(bu 2
 npm help developers
-.IP \(bu 2
-npm help disputes
 
 .RE

package/node_modules/npm/man/man7/removal.7

@@ -1,4 +1,4 @@
-.TH "REMOVAL" "7" "April 2022" "" ""
+.TH "REMOVAL" "7" "December 2022" "" ""
 .SH "NAME"
 \fBremoval\fR \- Cleaning the Slate
 .SS Synopsis

package/node_modules/npm/man/man7/scope.7

@@ -1,4 +1,4 @@
-.TH "SCOPE" "7" "April 2022" "" ""
+.TH "SCOPE" "7" "December 2022" "" ""
 .SH "NAME"
 \fBscope\fR \- Scoped packages
 .SS Description
@@ -97,7 +97,8 @@ desired, with \fBnpm access\fP or on the npmjs\.com website\.
 .P
 Scopes can be associated with a separate registry\. This allows you to
 seamlessly use a mix of packages from the primary npm registry and one or more
-private registries, such as npm Enterprise\.
+private registries, such as GitHub Packages or the open source Verdaccio
+project\.
 .P
 You can associate a scope with a registry at login, e\.g\.
 .P

package/node_modules/npm/man/man7/scripts.7

@@ -1,4 +1,4 @@
-.TH "SCRIPTS" "7" "April 2022" "" ""
+.TH "SCRIPTS" "7" "December 2022" "" ""
 .SH "NAME"
 \fBscripts\fR \- How npm handles the "scripts" field
 .SS Description

package/node_modules/npm/man/man7/semver.7

@@ -1,4 +1,4 @@
-.TH "SEMVER" "7" "April 2022" "" ""
+.TH "SEMVER" "7" "December 2022" "" ""
 .SH "NAME"
 \fBsemver\fR \- The semantic versioner for npm
 .SH Install

package/node_modules/npm/node_modules/@iarna/cli/LICENSE

@@ -0,0 +1,14 @@
+Copyright (c) 2015, Rebecca Turner <me@re-becca.org>
+
+Permission to use, copy, modify, and/or distribute this software for any
+purpose with or without fee is hereby granted, provided that the above
+copyright notice and this permission notice appear in all copies.
+
+THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
+WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
+ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
+WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
+ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
+OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
+

package/node_modules/npm/node_modules/@iarna/cli/README.md

@@ -0,0 +1,152 @@
+# @iarna/cli
+
+Some simple CLI scaffolding for promise returning applications.
+
+[![Coverage Status](https://coveralls.io/repos/github/iarna/cli/badge.svg?branch=latest)](https://coveralls.io/github/iarna/cli?branch=latest)
+
+## EXAMPLE
+
+`example.js`
+```js
+require('@iarna/cli')(main)
+
+const util = require('util');
+const sleep = util.promisify(setTimeout);
+
+// opts will only contain the _ var, for compatibility with yargs
+async function main (opts, arg1, arg2, arg3) {
+  console.log('Got:', arg1, arg2, arg3)
+  await sleep(40)
+}
+```
+
+## WHAT YOU GET
+
+* Automatic glob parsing on Windows so that your passing `*.foo` works the
+  same on Mac/Linux/Windows.
+* Error detetion and handling:
+  * _exit without resolving warnings_ - If your program finishes without
+    resolving its promises (like if it crashes hard or you process.exit, or
+    you just don't resolve the promise) then we warn about that.
+  * If your entry point function rejects then that's reported with a stack
+    trace (if the rejected value has `.stack`) else with the rejected value
+    and your process will exit with an error code.
+* Optional `yargs` support.  If `yargs` is requirable then it will be used. 
+  The wrapper around the main function returns a yargs object, so you can
+  configure it as usual.  The `argv` object is passed in as the first
+  argument of your entry point function.  The rest of your positional
+  arguments are passed in as the remaining function arguments.
+* Optional `update-notifier` support.  If `update-notifier` is requirable
+  then it will be used.  A default update notifier is setup for your app so
+  users will learn about new versions when you publish them.  Your app needs
+  to have a name, version and bin entry in its `package.json`.  (The bin
+  entry needs to have the script using `@iarna/cli` in it for the update
+  notifier to trigger.)
+
+## With Yargs
+
+If you have yargs installed as a dependency you can customize it further by
+chaining off the require in the usual yargsish way.
+
+`example.js`
+```js
+require('@iarna/cli')(main)
+  .boolean('silent')
+  .boolean('exit')
+  .boolean('error')
+  .boolean('reject')
+  .boolean('code50')
+  .version()
+  .help()
+
+const util = require('util');
+const sleep = util.promisify(setTimeout);
+
+function main (opts, arg1, arg2, arg3) {
+  if (!opts.silent) console.error('Starting up!')
+  console.log('Got:', arg1, arg2, arg3)
+  if (opts.exit) process.exit()
+  if (opts.error) throw new Error('throw')
+  if (opts.reject) return Promise.reject(new Error('reject'))
+  if (opts.code50) return Promise.reject(50)
+  return sleep(10000)
+}
+
+// alternatively use:
+// function main (opts, ...args) {
+```
+
+```console
+$ node example hello there world
+Starting up!
+Got: hello there world
+$ node example hello there world
+Starting up!
+Got: hello there world
+^C
+Abnormal exit: SIGINT
+$ node example --silent hello there world
+Got: hello there world
+$ node example --silent hello there world --exit
+Got: hello there world
+Abnormal exit: Promises not resolved
+$ node example --silent hello there world --error
+Got: hello there world
+Error: throw
+    at main (/Users/rebecca/code/cli/example.js:11:25)
+    at Immediate.setImmediate (/Users/rebecca/code/cli/app.js:38:32)
+    at runCallback (timers.js:800:20)
+    at tryOnImmediate (timers.js:762:5)
+    at processImmediate [as _immediateCallback] (timers.js:733:5)
+$ node example --silent hello there world --reject
+Got: hello there world
+Error: reject
+    at main (/Users/rebecca/code/cli/example.js:12:42)
+    at Immediate.setImmediate [as _onImmediate] (/Users/rebecca/code/cli/app.js:38:32)
+    at runCallback (timers.js:800:20)
+    at tryOnImmediate (timers.js:762:5)
+    at processImmediate [as _immediateCallback] (timers.js:733:5)
+$ node example --silent hello there world --code50
+Got: hello there world
+$ echo $?
+50
+```
+
+## WHAT ITS NOT
+
+A full framework for writing cli apps.  You'll likely outgrow the error
+handling pretty fast if this is anything beyond a little one off.  This
+mostly exists to scratch my own itch.  I kept on writing this code and I
+wanted to stop.  =D
+
+It's designed to be only be as heavy as it needs to be.  It only has one
+direct dependency, but it can provide enhanced functionality if you depend on
+`yargs` or `update-notifier`.
+
+## USAGE
+
+### require('@iarna/cli')(entryPointFunction) → [yargs]
+
+The module itself exports a function that you need to call with the name of
+your main function.  Your main function is like `main` in C, it's the entry
+point for your program.  It needs to return a promise that resolves when
+your program completes.
+
+The return value from the call is, if you have `yargs` installed, a `yargs`
+object you can use to configure what options your script takes. If you
+don't have yargs installed then it's a proxy that throws if you try to do
+anything with it.
+
+Your entry point function can be named anything, but it needs to return a
+promise and it takes arguments like this:
+
+`main(opts, arg1, arg2, …, argn) → Promise`
+
+If you have `yargs` installed then the `opts` argument is `yargs.argv`
+and the additional arguments are from `argv._`, so `arg1 === argv._[0]`,
+`arg2 === argv._[1]` and so on.
+
+If you don't have `yargs` installed then `opts` argument is an object with
+an `_` property containing all arguments, for compatibility with the `yargs`
+mode.  As with that mode `arg1 === argv._[0]`, `arg2 === argv._[1]` and so
+on.

package/node_modules/npm/node_modules/@iarna/cli/app.js

@@ -0,0 +1,109 @@
+'use strict'
+const onExit = require('signal-exit')
+const path = require('path')
+const fs = require('fs')
+const process = require('process')
+const binName = path.basename(require.main.filename, '.js')
+const mainPath = path.resolve(require.main.paths[0], '..')
+
+module.exports = function (entry) {
+  let started = false
+  let exited = false
+  onExit((code, signal) => {
+    if (started && !exited) {
+      // tested, but exit mechanism can't collect coverage
+      /* istanbul ignore next */
+      if (signal) {
+        /* istanbul ignore next */
+        console.error('Abnormal exit:', signal)
+      } else {
+        console.error('Abnormal exit: Promises not resolved')
+      }
+      process.exit(code || 1)
+    }
+  })
+  fs.readFile(mainPath + '/package.json', (err, data) => {
+    try {
+      const pkg = JSON.parse(data)
+      const nameMatch = new RegExp(binName, 'i')
+      let isInPackage = typeof pkg.bin === 'string'
+        ? nameMatch.test(pkg.bin)
+        : pkg.bin && Object.keys(pkg.bin).some(b => nameMatch.test(b) || nameMatch.test(pkg.bin[b]))
+      if (isInPackage) {
+        /* istanbul ignore next */
+        if (global['NO_NOTIFIER']) throw new Error('NO NOTIFIER')
+        const updateNotifier = require('update-notifier');
+        updateNotifier({pkg: pkg}).notify()
+      }
+    } catch (ex) { /* don't care */ }
+  })
+
+  let haveYargs
+  let yargs
+  let opts
+  let argv = process.argv.slice(2)
+  if (process.platform === 'win32') {
+    const glob = require('glob').sync
+    const cwd = process.cwd()
+    const statCache = {}
+    const nonull = true
+    const expandedArgs = []
+    argv.forEach(_ => expandedArgs.push.apply(expandedArgs, glob(_, {cwd, statCache, nonull})))
+    argv = expandedArgs
+  }
+  try {
+    /* istanbul ignore next */
+    if (global['NO_YARGS']) throw new Error('NO YARGS')
+    yargs = require('yargs')(argv)
+    haveYargs = true
+  } catch (_) {
+    opts = {_: argv}
+    const noYargs = () => {
+      throw new Error('Argument parsing is not available (could not find yargs), to install run: npm i yargs')
+    }
+    // only missing on v4, which has incomplete coverage anyway
+    /* istanbul ignore next */
+    yargs = global.Proxy && new global.Proxy({}, {
+      getPrototypeOf: noYargs,
+      setPrototypeOf: noYargs,
+      isExtensible: noYargs,
+      preventExtensions: noYargs,
+      getOwnPropertyDescriptor: noYargs,
+      defineProperty: noYargs,
+      has: noYargs,
+      get: noYargs,
+      set: noYargs,
+      deleteProperty: noYargs,
+      ownKeys: noYargs,
+      apply: noYargs,
+      construct: noYargs
+    })
+  }
+  setImmediate(() => {
+    if (haveYargs) {
+      opts = yargs.argv
+      argv = opts._
+    }
+    started = true
+    try {
+      const appPromise = entry.apply(null, [opts].concat(argv))
+      if (!appPromise || !appPromise.then) {
+        return onError(new Error('Application entry point' + (entry.name ? ` (${entry.name})` : '') + ' did not return a promise.'))
+      }
+      appPromise.then(() => exited = true, onError)
+    } catch (ex) {
+      onError (ex)
+    }
+    function onError (err) {
+      exited = true
+      if (typeof err === 'number') {
+        process.exit(err)
+      } else if (err) {
+        console.error((err && err.stack) ? err.stack : err)
+      }
+      process.exit(1)
+    }
+  })
+  return yargs
+}
+

package/node_modules/npm/node_modules/@iarna/cli/package.json

@@ -0,0 +1,35 @@
+{
+  "name": "@iarna/cli",
+  "version": "2.1.0",
+  "description": "Some simple CLI scaffolding for promise returning applications.",
+  "main": "app.js",
+  "scripts": {
+    "test": "tap --100 test/scenarios.js"
+  },
+  "keywords": [],
+  "author": "Rebecca Turner <me@re-becca.org> (http://re-becca.org/)",
+  "license": "ISC",
+  "dependencies": {
+    "signal-exit": "^3.0.2",
+    "glob": "^7.1.2"
+  },
+  "files": [
+    "app.js"
+  ],
+  "devDependencies": {
+    "@perl/qr": "^1.2.0",
+    "@perl/qx": "^1.0.2",
+    "require-inject": "^1.4.4",
+    "tap": "^12.0.1",
+    "update-notifier": "^2.2.0",
+    "yargs": "^8.0.2"
+  },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/iarna/cli.git"
+  },
+  "bugs": {
+    "url": "https://github.com/iarna/cli/issues"
+  },
+  "homepage": "https://github.com/iarna/cli#readme"
+}

package/node_modules/npm/{docs → node_modules/are-we-there-yet/node_modules/readable-stream/node_modules/safe-buffer}/LICENSE

@@ -1,6 +1,6 @@
 The MIT License (MIT)
 
-Copyright (c) 2015 gatsbyjs
+Copyright (c) Feross Aboukhadijeh
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal
@@ -9,14 +9,13 @@ 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 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.
-
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.