npm - @surgeapi/node - Versions diffs - 0.30.0 → 0.32.0 - Mend

@surgeapi/node 0.30.0 → 0.32.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (2171) hide show

package/oidc/node_modules/npm/docs/output/using-npm/workspaces.html DELETED Viewed

@@ -1,293 +0,0 @@
-<!DOCTYPE html><html><head>
-<meta charset="utf-8">
-<title>workspaces</title>
-<style>
-body {
-    background-color: #ffffff;
-    color: #24292e;
-    margin: 0;
-    line-height: 1.5;
-    font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Helvetica, Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji";
-}
-#rainbar {
-    height: 10px;
-    background-image: linear-gradient(139deg, #fb8817, #ff4b01, #c12127, #e02aff);
-}
-a {
-    text-decoration: none;
-    color: #0366d6;
-}
-a:hover {
-    text-decoration: underline;
-}
-pre {
-    margin: 1em 0px;
-    padding: 1em;
-    border: solid 1px #e1e4e8;
-    border-radius: 6px;
-    display: block;
-    overflow: auto;
-    white-space: pre;
-    background-color: #f6f8fa;
-    color: #393a34;
-}
-code {
-    font-family: SFMono-Regular, Consolas, "Liberation Mono", Menlo, Courier, monospace;
-    font-size: 85%;
-    padding: 0.2em 0.4em;
-    background-color: #f6f8fa;
-    color: #393a34;
-}
-pre > code {
-    padding: 0;
-    background-color: inherit;
-    color: inherit;
-}
-h1, h2, h3 {
-    font-weight: 600;
-}
-#logobar {
-    background-color: #333333;
-    margin: 0 auto;
-    padding: 1em 4em;
-}
-#logobar .logo {
-    float: left;
-}
-#logobar .title {
-    font-weight: 600;
-    color: #dddddd;
-    float: left;
-    margin: 5px 0 0 1em;
-}
-#logobar:after {
-    content: "";
-    display: block;
-    clear: both;
-}
-#content {
-    margin: 0 auto;
-    padding: 0 4em;
-}
-#table_of_contents > h2 {
-    font-size: 1.17em;
-}
-#table_of_contents ul:first-child {
-    border: solid 1px #e1e4e8;
-    border-radius: 6px;
-    padding: 1em;
-    background-color: #f6f8fa;
-    color: #393a34;
-}
-#table_of_contents ul {
-    list-style-type: none;
-    padding-left: 1.5em;
-}
-#table_of_contents li {
-    font-size: 0.9em;
-}
-#table_of_contents li a {
-    color: #000000;
-}
-header.title {
-    border-bottom: solid 1px #e1e4e8;
-}
-header.title > h1 {
-    margin-bottom: 0.25em;
-}
-header.title > .description {
-    display: block;
-    margin-bottom: 0.5em;
-    line-height: 1;
-}
-header.title .version {
-    font-size: 0.8em;
-    color: #666666;
-}
-footer#edit {
-    border-top: solid 1px #e1e4e8;
-    margin: 3em 0 4em 0;
-    padding-top: 2em;
-}
-</style>
-</head>
-<body>
-<div id="banner">
-<div id="rainbar"></div>
-<div id="logobar">
-<svg class="logo" role="img" height="32" width="32" viewBox="0 0 700 700">
-<polygon fill="#cb0000" points="0,700 700,700 700,0 0,0"></polygon>
-<polygon fill="#ffffff" points="150,550 350,550 350,250 450,250 450,550 550,550 550,150 150,150"></polygon>
-</svg>
-<div class="title">
-npm command-line interface
-</div>
-</div>
-</div>
-<section id="content">
-<header class="title">
-<h1 id="----workspaces----1162">
-    <span>workspaces</span>
-    <span class="version">@11.6.2</span>
-</h1>
-<span class="description">Working with workspaces</span>
-</header>
-<section id="table_of_contents">
-<h2 id="table-of-contents">Table of contents</h2>
-<div id="_table_of_contents"><ul><li><a href="#description">Description</a></li><li><a href="#defining-workspaces">Defining workspaces</a></li><li><a href="#getting-started-with-workspaces">Getting started with workspaces</a></li><li><a href="#adding-dependencies-to-a-workspace">Adding dependencies to a workspace</a></li><li><a href="#using-workspaces">Using workspaces</a></li><li><a href="#running-commands-in-the-context-of-workspaces">Running commands in the context of workspaces</a></li><li><a href="#ignoring-missing-scripts">Ignoring missing scripts</a></li><li><a href="#see-also">See also</a></li></ul></div>
-</section>
-<div id="_content"><h3 id="description">Description</h3>
-<p><strong>Workspaces</strong> is a generic term that refers to the set of features in the npm cli that provides support for managing multiple packages from your local file system from within a singular top-level, root package.</p>
-<p>This set of features makes up for a much more streamlined workflow handling linked packages from the local file system.
-It automates the linking process as part of <code>npm install</code> and removes the need to manually use <code>npm link</code> in order to add references to packages that should be symlinked into the current <code>node_modules</code> folder.</p>
-<p>We also refer to these packages being auto-symlinked during <code>npm install</code> as a single <strong>workspace</strong>, meaning it's a nested package within the current local file system that is explicitly defined in the <a href="../configuring-npm/package-json#workspaces.html"><code>package.json</code></a>
-<code>workspaces</code> configuration.</p>
-<h3 id="defining-workspaces">Defining workspaces</h3>
-<p>Workspaces are usually defined via the <code>workspaces</code> property of the <a href="../configuring-npm/package-json#workspaces.html"><code>package.json</code></a> file, e.g:</p>
-<pre><code class="language-json">{
-  "name": "my-workspaces-powered-project",
-  "workspaces": [
-    "packages/a"
-  ]
-}
-</code></pre>
-<p>Given the above <code>package.json</code> example living at a current working directory <code>.</code> that contains a folder named <code>packages/a</code> that itself contains a <code>package.json</code> inside it, defining a Node.js package, e.g:</p>
-<pre><code>.
-+-- package.json
-`-- packages
-   +-- a
-   |   `-- package.json
-</code></pre>
-<p>The expected result once running <code>npm install</code> in this current working directory <code>.</code> is that the folder <code>packages/a</code> will get symlinked to the <code>node_modules</code> folder of the current working dir.</p>
-<p>Below is a post <code>npm install</code> example, given that same previous example structure of files and folders:</p>
-<pre><code>.
-+-- node_modules
-|  `-- a -&gt; ../packages/a
-+-- package-lock.json
-+-- package.json
-`-- packages
-   +-- a
-   |   `-- package.json
-</code></pre>
-<h3 id="getting-started-with-workspaces">Getting started with workspaces</h3>
-<p>You may automate the required steps to define a new workspace using <a href="../commands/npm-init.html">npm init</a>.
-For example in a project that already has a <code>package.json</code> defined you can run:</p>
-<pre><code>npm init -w ./packages/a
-</code></pre>
-<p>This command will create the missing folders and a new <code>package.json</code> file (if needed) while also making sure to properly configure the
-<code>"workspaces"</code> property of your root project <code>package.json</code>.</p>
-<h3 id="adding-dependencies-to-a-workspace">Adding dependencies to a workspace</h3>
-<p>It's possible to directly add/remove/update dependencies of your workspaces using the <a href="../using-npm/config#workspace.html"><code>workspace</code> config</a>.</p>
-<p>For example, assuming the following structure:</p>
-<pre><code>.
-+-- package.json
-`-- packages
-   +-- a
-   |   `-- package.json
-   `-- b
-       `-- package.json
-</code></pre>
-<p>If you want to add a dependency named <code>abbrev</code> from the registry as a dependency of your workspace <strong>a</strong>, you may use the workspace config to tell the npm installer that package should be added as a dependency of the provided workspace:</p>
-<pre><code>npm install abbrev -w a
-</code></pre>
-<p>Note: other installing commands such as <code>uninstall</code>, <code>ci</code>, etc will also respect the provided <code>workspace</code> configuration.</p>
-<h3 id="using-workspaces">Using workspaces</h3>
-<p>Given the <a href="https://nodejs.org/dist/latest-v14.x/docs/api/modules.html#modules_all_together">specifics of how Node.js handles module resolution</a> it's possible to consume any defined workspace by its declared <code>package.json</code> <code>name</code>.
-Continuing from the example defined above, let's also create a Node.js script that will require the workspace <code>a</code> example module, e.g:</p>
-<pre><code>// ./packages/a/index.js
-module.exports = 'a'
-// ./lib/index.js
-const moduleA = require('a')
-console.log(moduleA) // -&gt; a
-</code></pre>
-<p>When running it with:</p>
-<p><code>node lib/index.js</code></p>
-<p>This demonstrates how the nature of <code>node_modules</code> resolution allows for
-<strong>workspaces</strong> to enable a portable workflow for requiring each <strong>workspace</strong> in such a way that is also easy to <a href="../commands/npm-publish.html">publish</a> these nested workspaces to be consumed elsewhere.</p>
-<h3 id="running-commands-in-the-context-of-workspaces">Running commands in the context of workspaces</h3>
-<p>You can use the <code>workspace</code> configuration option to run commands in the context of a configured workspace.
-Additionally, if your current directory is in a workspace, the <code>workspace</code> configuration is implicitly set, and <code>prefix</code> is set to the root workspace.</p>
-<p>Following is a quick example on how to use the <code>npm run</code> command in the context of nested workspaces.
-For a project containing multiple workspaces, e.g:</p>
-<pre><code>.
-+-- package.json
-`-- packages
-   +-- a
-   |   `-- package.json
-   `-- b
-       `-- package.json
-</code></pre>
-<p>By running a command using the <code>workspace</code> option, it's possible to run the given command in the context of that specific workspace.
-e.g:</p>
-<pre><code>npm run test --workspace=a
-</code></pre>
-<p>You could also run the command within the workspace.</p>
-<pre><code>cd packages/a &amp;&amp; npm run test
-</code></pre>
-<p>Either will run the <code>test</code> script defined within the
-<code>./packages/a/package.json</code> file.</p>
-<p>Please note that you can also specify this argument multiple times in the command-line in order to target multiple workspaces, e.g:</p>
-<pre><code>npm run test --workspace=a --workspace=b
-</code></pre>
-<p>Or run the command for each workspace within the 'packages' folder:</p>
-<pre><code>npm run test --workspace=packages
-</code></pre>
-<p>It's also possible to use the <code>workspaces</code> (plural) configuration option to enable the same behavior but running that command in the context of <strong>all</strong> configured workspaces.
-e.g:</p>
-<pre><code>npm run test --workspaces
-</code></pre>
-<p>Will run the <code>test</code> script in both <code>./packages/a</code> and <code>./packages/b</code>.</p>
-<p>Commands will be run in each workspace in the order they appear in your <code>package.json</code></p>
-<pre><code>{
-  "workspaces": [ "packages/a", "packages/b" ]
-}
-</code></pre>
-<p>Order of run is different with:</p>
-<pre><code>{
-  "workspaces": [ "packages/b", "packages/a" ]
-}
-</code></pre>
-<h3 id="ignoring-missing-scripts">Ignoring missing scripts</h3>
-<p>It is not required for all of the workspaces to implement scripts run with the <code>npm run</code> command.</p>
-<p>By running the command with the <code>--if-present</code> flag, npm will ignore workspaces missing target script.</p>
-<pre><code>npm run test --workspaces --if-present
-</code></pre>
-<h3 id="see-also">See also</h3>
-<ul>
-<li><a href="../commands/npm-install.html">npm install</a></li>
-<li><a href="../commands/npm-publish.html">npm publish</a></li>
-<li><a href="../commands/npm-run.html">npm run</a></li>
-<li><a href="../using-npm/config.html">config</a></li>
-</ul></div>
-<footer id="edit">
-<a href="https://github.com/npm/cli/edit/latest/docs/lib/content/using-npm/workspaces.md">
-<svg role="img" viewBox="0 0 16 16" width="16" height="16" fill="currentcolor" style="vertical-align: text-bottom; margin-right: 0.3em;">
-<path fill-rule="evenodd" d="M11.013 1.427a1.75 1.75 0 012.474 0l1.086 1.086a1.75 1.75 0 010 2.474l-8.61 8.61c-.21.21-.47.364-.756.445l-3.251.93a.75.75 0 01-.927-.928l.929-3.25a1.75 1.75 0 01.445-.758l8.61-8.61zm1.414 1.06a.25.25 0 00-.354 0L10.811 3.75l1.439 1.44 1.263-1.263a.25.25 0 000-.354l-1.086-1.086zM11.189 6.25L9.75 4.81l-6.286 6.287a.25.25 0 00-.064.108l-.558 1.953 1.953-.558a.249.249 0 00.108-.064l6.286-6.286z"></path>
-</svg>
-Edit this page on GitHub
-</a>
-</footer>
-</section>
-</body></html>

package/oidc/node_modules/npm/index.js DELETED Viewed

@@ -1,5 +0,0 @@
-if (require.main === module) {
-  require('./lib/cli.js')(process)
-} else {
-  throw new Error('The programmatic API was removed in npm v8.0.0')
-}

package/oidc/node_modules/npm/lib/arborist-cmd.js DELETED Viewed

@@ -1,53 +0,0 @@
-const { log } = require('proc-log')
-const BaseCommand = require('./base-cmd.js')
-// This is the base for all commands whose execWorkspaces just gets
-// a list of workspace names and passes it on to new Arborist() to
-// be able to run a filtered Arborist.reify() at some point.
-class ArboristCmd extends BaseCommand {
-  get isArboristCmd () {
-    return true
-  }
-  static params = [
-    'workspace',
-    'workspaces',
-    'include-workspace-root',
-    'install-links',
-  ]
-  static workspaces = true
-  static ignoreImplicitWorkspace = false
-  static checkDevEngines = true
-  constructor (npm) {
-    super(npm)
-    const { config } = this.npm
-    // when location isn't set and global isn't true check for a package.json at
-    // the localPrefix and set the location to project if found
-    const locationProject = config.get('location') === 'project' || (
-      config.isDefault('location')
-      // this is different then `npm.global` which falls back to checking
-      // location which we do not want to use here
-      && !config.get('global')
-      && npm.localPackage
-    )
-    // if audit is not set and we are in global mode and location is not project
-    // and we assume its not a project related context, then we set audit=false
-    if (config.isDefault('audit') && (this.npm.global || !locationProject)) {
-      config.set('audit', false)
-    } else if (this.npm.global && config.get('audit')) {
-      log.warn('config', 'includes both --global and --audit, which is currently unsupported.')
-    }
-  }
-  async execWorkspaces (args) {
-    await this.setWorkspaces()
-    return this.exec(args)
-  }
-}
-module.exports = ArboristCmd

package/oidc/node_modules/npm/lib/base-cmd.js DELETED Viewed

@@ -1,214 +0,0 @@
-const { log } = require('proc-log')
-class BaseCommand {
-  // these defaults can be overridden by individual commands
-  static workspaces = false
-  static ignoreImplicitWorkspace = true
-  static checkDevEngines = false
-  // these should always be overridden by individual commands
-  static name = null
-  static description = null
-  static params = null
-  // this is a static so that we can read from it without instantiating a command
-  // which would require loading the config
-  static get describeUsage () {
-    const { definitions } = require('@npmcli/config/lib/definitions')
-    const { aliases: cmdAliases } = require('./utils/cmd-list')
-    const seenExclusive = new Set()
-    const wrapWidth = 80
-    const { description, usage = [''], name, params } = this
-    const fullUsage = [
-      `${description}`,
-      '',
-      'Usage:',
-      ...usage.map(u => `npm ${name} ${u}`.trim()),
-    ]
-    if (params) {
-      let results = ''
-      let line = ''
-      for (const param of params) {
-        /* istanbul ignore next */
-        if (seenExclusive.has(param)) {
-          continue
-        }
-        const { exclusive } = definitions[param]
-        let paramUsage = `${definitions[param].usage}`
-        if (exclusive) {
-          const exclusiveParams = [paramUsage]
-          seenExclusive.add(param)
-          for (const e of exclusive) {
-            seenExclusive.add(e)
-            exclusiveParams.push(definitions[e].usage)
-          }
-          paramUsage = `${exclusiveParams.join('|')}`
-        }
-        paramUsage = `[${paramUsage}]`
-        if (line.length + paramUsage.length > wrapWidth) {
-          results = [results, line].filter(Boolean).join('\n')
-          line = ''
-        }
-        line = [line, paramUsage].filter(Boolean).join(' ')
-      }
-      fullUsage.push('')
-      fullUsage.push('Options:')
-      fullUsage.push([results, line].filter(Boolean).join('\n'))
-    }
-    const aliases = Object.entries(cmdAliases).reduce((p, [k, v]) => {
-      return p.concat(v === name ? k : [])
-    }, [])
-    if (aliases.length) {
-      const plural = aliases.length === 1 ? '' : 'es'
-      fullUsage.push('')
-      fullUsage.push(`alias${plural}: ${aliases.join(', ')}`)
-    }
-    fullUsage.push('')
-    fullUsage.push(`Run "npm help ${name}" for more info`)
-    return fullUsage.join('\n')
-  }
-  constructor (npm) {
-    this.npm = npm
-    const { config } = this.npm
-    if (!this.constructor.skipConfigValidation) {
-      config.validate()
-    }
-    if (config.get('workspaces') === false && config.get('workspace').length) {
-      throw new Error('Cannot use --no-workspaces and --workspace at the same time')
-    }
-  }
-  get name () {
-    return this.constructor.name
-  }
-  get description () {
-    return this.constructor.description
-  }
-  get params () {
-    return this.constructor.params
-  }
-  get usage () {
-    return this.constructor.describeUsage
-  }
-  usageError (prefix = '') {
-    if (prefix) {
-      prefix += '\n\n'
-    }
-    return Object.assign(new Error(`\n${prefix}${this.usage}`), {
-      code: 'EUSAGE',
-    })
-  }
-  // Compare the number of entries with what was expected
-  checkExpected (entries) {
-    if (!this.npm.config.isDefault('expect-results')) {
-      const expected = this.npm.config.get('expect-results')
-      if (!!entries !== !!expected) {
-        log.warn(this.name, `Expected ${expected ? '' : 'no '}results, got ${entries}`)
-        process.exitCode = 1
-      }
-    } else if (!this.npm.config.isDefault('expect-result-count')) {
-      const expected = this.npm.config.get('expect-result-count')
-      if (expected !== entries) {
-        log.warn(this.name, `Expected ${expected} result${expected === 1 ? '' : 's'}, got ${entries}`)
-        process.exitCode = 1
-      }
-    }
-  }
-  // Checks the devEngines entry in the package.json at this.localPrefix
-  async checkDevEngines () {
-    const force = this.npm.flatOptions.force
-    const { devEngines } = await require('@npmcli/package-json')
-      .normalize(this.npm.config.localPrefix)
-      .then(p => p.content)
-      .catch(() => ({}))
-    if (typeof devEngines === 'undefined') {
-      return
-    }
-    const { checkDevEngines, currentEnv } = require('npm-install-checks')
-    const current = currentEnv.devEngines({
-      nodeVersion: this.npm.nodeVersion,
-      npmVersion: this.npm.version,
-    })
-    const failures = checkDevEngines(devEngines, current)
-    const warnings = failures.filter(f => f.isWarn)
-    const errors = failures.filter(f => f.isError)
-    const genMsg = (failure, i = 0) => {
-      return [...new Set([
-        // eslint-disable-next-line
-        i === 0 ? 'The developer of this package has specified the following through devEngines' : '',
-        `${failure.message}`,
-        `${failure.errors.map(e => e.message).join('\n')}`,
-      ])].filter(v => v).join('\n')
-    }
-    [...warnings, ...(force ? errors : [])].forEach((failure, i) => {
-      const message = genMsg(failure, i)
-      log.warn('EBADDEVENGINES', message)
-      log.warn('EBADDEVENGINES', {
-        current: failure.current,
-        required: failure.required,
-      })
-    })
-    if (force) {
-      return
-    }
-    if (errors.length) {
-      const failure = errors[0]
-      const message = genMsg(failure)
-      throw Object.assign(new Error(message), {
-        engine: failure.engine,
-        code: 'EBADDEVENGINES',
-        current: failure.current,
-        required: failure.required,
-      })
-    }
-  }
-  async setWorkspaces () {
-    const { relative } = require('node:path')
-    const includeWorkspaceRoot = this.isArboristCmd
-      ? false
-      : this.npm.config.get('include-workspace-root')
-    const prefixInsideCwd = relative(this.npm.localPrefix, process.cwd()).startsWith('..')
-    const relativeFrom = prefixInsideCwd ? this.npm.localPrefix : process.cwd()
-    const filters = this.npm.config.get('workspace')
-    const getWorkspaces = require('./utils/get-workspaces.js')
-    const ws = await getWorkspaces(filters, {
-      path: this.npm.localPrefix,
-      includeWorkspaceRoot,
-      relativeFrom,
-    })
-    this.workspaces = ws
-    this.workspaceNames = [...ws.keys()]
-    this.workspacePaths = [...ws.values()]
-  }
-}
-module.exports = BaseCommand

package/oidc/node_modules/npm/lib/cli/entry.js DELETED Viewed

@@ -1,72 +0,0 @@
-// Separated out for easier unit testing
-module.exports = async (process, validateEngines) => {
-  // set it here so that regardless of what happens later, we don't
-  // leak any private CLI configs to other programs
-  process.title = 'npm'
-  // Patch the global fs module here at the app level
-  require('graceful-fs').gracefulify(require('node:fs'))
-  const satisfies = require('semver/functions/satisfies')
-  const ExitHandler = require('./exit-handler.js')
-  const exitHandler = new ExitHandler({ process })
-  const Npm = require('../npm.js')
-  const npm = new Npm()
-  exitHandler.setNpm(npm)
-  // only log node and npm paths in argv initially since argv can contain sensitive info. a cleaned version will be logged later
-  const { log, output } = require('proc-log')
-  log.verbose('cli', process.argv.slice(0, 2).join(' '))
-  log.info('using', 'npm@%s', npm.version)
-  log.info('using', 'node@%s', process.version)
-  // At this point we've required a few files and can be pretty sure we don't contain invalid syntax for this version of node. It's possible a lazy require would, but that's unlikely enough that it's not worth catching anymore and we attach the more important exit handlers.
-  validateEngines.off()
-  exitHandler.registerUncaughtHandlers()
-  // It is now safe to log a warning if they are using a version of node that is not going to fail on syntax errors but is still unsupported and untested and might not work reliably. This is safe to use the logger now which we want since this will show up in the error log too.
-  if (!satisfies(validateEngines.node, validateEngines.engines)) {
-    log.warn('cli', validateEngines.unsupportedMessage)
-  }
-  // Now actually fire up npm and run the command.
-  // This is how to use npm programmatically:
-  try {
-    const { exec, command, args } = await npm.load()
-    if (!exec) {
-      return exitHandler.exit()
-    }
-    if (!command) {
-      output.standard(npm.usage)
-      process.exitCode = 1
-      return exitHandler.exit()
-    }
-    // Options are prefixed by a hyphen-minus (-, \u2d).
-    // Other dash-type chars look similar but are invalid.
-    const nonDashArgs = npm.argv.filter(a => /^[\u2010-\u2015\u2212\uFE58\uFE63\uFF0D]/.test(a))
-    if (nonDashArgs.length) {
-      log.error(
-        'arg',
-        'Argument starts with non-ascii dash, this is probably invalid:',
-        require('@npmcli/redact').redactLog(nonDashArgs.join(', '))
-      )
-    }
-    const execPromise = npm.exec(command, args)
-    // this is async but we don't await it, since its ok if it doesnt
-    // finish before the command finishes running. it uses command and argv
-    // so it must be initiated here, after the command name is set
-    const updateNotifier = require('./update-notifier.js')
-    // eslint-disable-next-line promise/catch-or-return
-    updateNotifier(npm).then((msg) => (npm.updateNotification = msg))
-    await execPromise
-    return exitHandler.exit()
-  } catch (err) {
-    return exitHandler.exit(err)
-  }
-}