From 7773f091651cee51ddedd082788b64921bd2bebc Mon Sep 17 00:00:00 2001 From: AmirSa12 Date: Mon, 25 Aug 2025 20:36:03 +0330 Subject: [PATCH 1/8] update --- bin/completion-handlers.ts | 314 +++++++++++++++++++++++++++---------- 1 file changed, 229 insertions(+), 85 deletions(-) diff --git a/bin/completion-handlers.ts b/bin/completion-handlers.ts index b0815cb..9954fb1 100644 --- a/bin/completion-handlers.ts +++ b/bin/completion-handlers.ts @@ -54,43 +54,99 @@ export function setupCompletionForPackageManager( export function setupPnpmCompletions(completion: PackageManagerCompletion) { // Package management - const addCmd = completion.command('add', 'Install packages'); - addCmd.option('save-dev', 'Save to devDependencies', 'D'); - addCmd.option('save-optional', 'Save to optionalDependencies', 'O'); - addCmd.option('save-exact', 'Save exact version', 'E'); - addCmd.option('global', 'Install globally', 'g'); - addCmd.option('workspace', 'Install to workspace'); - addCmd.option('filter', 'Filter packages'); + const addCmd = completion.command( + 'add', + 'Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency' + ); + addCmd.option('save-dev', 'Save package to your `devDependencies`', 'D'); + addCmd.option( + 'save-optional', + 'Save package to your `optionalDependencies`', + 'O' + ); + addCmd.option('save-exact', 'Install exact version', 'E'); + addCmd.option('global', 'Install as a global package', 'g'); + addCmd.option( + 'workspace', + 'Only adds the new dependency if it is found in the workspace' + ); + addCmd.option( + 'filter', + 'Restricts the scope to package names matching the given pattern' + ); - const removeCmd = completion.command('remove', 'Remove packages'); + const removeCmd = completion.command( + 'remove', + "Removes packages from node_modules and from the project's package.json" + ); removeCmd.argument('package', dependencyCompletion); removeCmd.option('global', 'Remove globally', 'g'); - const installCmd = completion.command('install', 'Install dependencies'); - installCmd.option('frozen-lockfile', 'Install with frozen lockfile'); - installCmd.option('prefer-frozen-lockfile', 'Prefer frozen lockfile'); - installCmd.option('production', 'Install production dependencies only'); - installCmd.option('dev', 'Install dev dependencies only'); - installCmd.option('optional', 'Include optional dependencies'); - installCmd.option('filter', 'Filter packages'); + const installCmd = completion.command( + 'install', + 'Install all dependencies for a project' + ); + installCmd.option( + 'frozen-lockfile', + "Don't generate a lockfile and fail if an update is needed" + ); + installCmd.option( + 'prefer-frozen-lockfile', + 'If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation' + ); + installCmd.option( + 'production', + "Packages in `devDependencies` won't be installed" + ); + installCmd.option('dev', 'Only `devDependencies` are installed'); + installCmd.option('optional', '`optionalDependencies` are not installed'); + installCmd.option( + 'filter', + 'Restricts the scope to package names matching the given pattern' + ); - const updateCmd = completion.command('update', 'Update dependencies'); + const updateCmd = completion.command( + 'update', + 'Updates packages to their latest version based on the specified range' + ); updateCmd.argument('package', dependencyCompletion); - updateCmd.option('latest', 'Update to latest versions'); - updateCmd.option('global', 'Update global packages', 'g'); - updateCmd.option('interactive', 'Interactive update', 'i'); + updateCmd.option('latest', 'Ignore version ranges in package.json'); + updateCmd.option('global', 'Update globally installed packages', 'g'); + updateCmd.option( + 'interactive', + 'Show outdated dependencies and select which ones to update', + 'i' + ); // Script execution - const runCmd = completion.command('run', 'Run scripts'); + const runCmd = completion.command('run', 'Runs a defined package script'); runCmd.argument('script', scriptCompletion, true); - runCmd.option('parallel', 'Run scripts in parallel'); - runCmd.option('stream', 'Stream output'); - runCmd.option('filter', 'Filter packages'); + runCmd.option( + 'parallel', + 'Completely disregard concurrency and topological sorting, running a given script immediately in all matching packages with prefixed streaming output' + ); + runCmd.option( + 'stream', + 'Stream output from child processes immediately, prefixed with the originating package directory' + ); + runCmd.option( + 'filter', + 'Restricts the scope to package names matching the given pattern' + ); - const execCmd = completion.command('exec', 'Execute commands'); - execCmd.option('filter', 'Filter packages'); + const execCmd = completion.command( + 'exec', + 'Executes a shell command in scope of a project' + ); + execCmd.option( + 'filter', + 'Restricts the scope to package names matching the given pattern' + ); execCmd.option('parallel', 'Run in parallel'); - execCmd.option('stream', 'Stream output'); + execCmd.option( + 'stream', + 'Stream output from child processes immediately, prefixed with the originating package directory' + ); completion.command('dlx', 'Run package without installing'); @@ -116,18 +172,30 @@ export function setupPnpmCompletions(completion: PackageManagerCompletion) { unlinkCmd.option('global', 'Unlink globally', 'g'); // Information - const listCmd = completion.command('list', 'List packages'); - listCmd.option('depth', 'Max depth'); + const listCmd = completion.command( + 'list', + 'Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure' + ); + listCmd.option( + 'depth', + 'How deep should levels of dependencies be inspected' + ); listCmd.option('global', 'List global packages', 'g'); listCmd.option('long', 'Show extended information'); listCmd.option('parseable', 'Parseable output'); listCmd.option('json', 'JSON output'); - const outdatedCmd = completion.command('outdated', 'Check outdated packages'); + const outdatedCmd = completion.command( + 'outdated', + 'Check for outdated packages' + ); outdatedCmd.option('global', 'Check global packages', 'g'); outdatedCmd.option('long', 'Show extended information'); - const auditCmd = completion.command('audit', 'Security audit'); + const auditCmd = completion.command( + 'audit', + 'Checks for known security issues with the installed packages' + ); auditCmd.option('fix', 'Automatically fix vulnerabilities'); auditCmd.option('json', 'JSON output'); @@ -136,9 +204,18 @@ export function setupPnpmCompletions(completion: PackageManagerCompletion) { // Store management completion.command('store', 'Store management'); - completion.command('store status', 'Store status'); - completion.command('store prune', 'Prune store'); - completion.command('store path', 'Store path'); + completion.command( + 'store status', + 'Checks for modified packages in the store' + ); + completion.command( + 'store prune', + 'Removes unreferenced (extraneous, orphan) packages from the store' + ); + completion.command( + 'store path', + 'Prints the path to the active store directory' + ); // Configuration completion.command('config', 'Configuration'); @@ -149,18 +226,27 @@ export function setupPnpmCompletions(completion: PackageManagerCompletion) { // Other useful commands completion.command('why', 'Explain why package is installed'); - completion.command('rebuild', 'Rebuild packages'); - completion.command('root', 'Print root directory'); + completion.command('rebuild', 'Rebuild a package'); + completion.command('root', 'Prints the effective modules directory'); completion.command('bin', 'Print bin directory'); - completion.command('start', 'Run start script'); - completion.command('test', 'Run test script'); + completion.command( + 'start', + 'Runs an arbitrary command specified in the package\'s "start" property of its "scripts" object' + ); + completion.command( + 'test', + 'Runs a package\'s "test" script, if one was provided' + ); completion.command('restart', 'Run restart script'); completion.command('stop', 'Run stop script'); } export function setupNpmCompletions(completion: PackageManagerCompletion) { // Package management - const installCmd = completion.command('install', 'Install packages'); + const installCmd = completion.command( + 'install', + 'install all the dependencies in your project' + ); installCmd.option('save', 'Save to dependencies', 'S'); installCmd.option('save-dev', 'Save to devDependencies', 'D'); installCmd.option('save-optional', 'Save to optionalDependencies', 'O'); @@ -169,7 +255,7 @@ export function setupNpmCompletions(completion: PackageManagerCompletion) { installCmd.option('production', 'Production install'); installCmd.option('only', 'Install only specific dependencies'); - const uninstallCmd = completion.command('uninstall', 'Remove packages'); + const uninstallCmd = completion.command('uninstall', 'Remove a package'); uninstallCmd.argument('package', dependencyCompletion); uninstallCmd.option('save', 'Remove from dependencies', 'S'); uninstallCmd.option('save-dev', 'Remove from devDependencies', 'D'); @@ -180,7 +266,7 @@ export function setupNpmCompletions(completion: PackageManagerCompletion) { updateCmd.option('global', 'Update global packages', 'g'); // Script execution - const runCmd = completion.command('run', 'Run scripts'); + const runCmd = completion.command('run', 'run the script named '); runCmd.argument('script', scriptCompletion, true); const runScriptCmd = completion.command('run-script', 'Run scripts'); @@ -260,35 +346,63 @@ export function setupNpmCompletions(completion: PackageManagerCompletion) { completion.command('rebuild', 'Rebuild packages'); completion.command('start', 'Run start script'); completion.command('stop', 'Run stop script'); - completion.command('test', 'Run test script'); + completion.command('test', "run this project's tests"); completion.command('restart', 'Run restart script'); } export function setupYarnCompletions(completion: PackageManagerCompletion) { // Package management - const addCmd = completion.command('add', 'Add packages'); - addCmd.option('dev', 'Add to devDependencies', 'D'); - addCmd.option('peer', 'Add to peerDependencies', 'P'); - addCmd.option('optional', 'Add to optionalDependencies', 'O'); - addCmd.option('exact', 'Add exact version', 'E'); - addCmd.option('tilde', 'Add with tilde range', 'T'); - - const removeCmd = completion.command('remove', 'Remove packages'); + const addCmd = completion.command( + 'add', + 'Installs a package and any packages that it depends on.' + ); + addCmd.option('dev', 'save package to your `devDependencies`', 'D'); + addCmd.option('peer', 'save package to your `peerDependencies`', 'P'); + addCmd.option('optional', 'save package to your `optionalDependencies`', 'O'); + addCmd.option('exact', 'install exact version', 'E'); + addCmd.option( + 'tilde', + 'install most recent release with the same minor version', + 'T' + ); + + const removeCmd = completion.command( + 'remove', + 'Removes a package from your direct dependencies updating your package.json and yarn.lock.' + ); removeCmd.argument('package', dependencyCompletion); - const installCmd = completion.command('install', 'Install dependencies'); - installCmd.option('frozen-lockfile', 'Install with frozen lockfile'); - installCmd.option('prefer-offline', 'Prefer offline'); + const installCmd = completion.command( + 'install', + 'Yarn install is used to install all dependencies for a project.' + ); + installCmd.option( + 'frozen-lockfile', + "don't generate a lockfile and fail if an update is needed" + ); + installCmd.option( + 'prefer-offline', + 'use network only if dependencies are not available in local cache' + ); installCmd.option('production', 'Production install'); - installCmd.option('pure-lockfile', 'Pure lockfile'); - installCmd.option('focus', 'Focus install'); - installCmd.option('har', 'Save HAR file'); + installCmd.option('pure-lockfile', "don't generate a lockfile"); + installCmd.option( + 'focus', + 'Focus on a single workspace by installing remote copies of its sibling workspaces' + ); + installCmd.option('har', 'save HAR output of network traffic'); - const upgradeCmd = completion.command('upgrade', 'Upgrade packages'); + const upgradeCmd = completion.command( + 'upgrade', + 'Upgrades packages to their latest version based on the specified range.' + ); upgradeCmd.argument('package', dependencyCompletion); - upgradeCmd.option('latest', 'Upgrade to latest'); - upgradeCmd.option('pattern', 'Upgrade pattern'); - upgradeCmd.option('scope', 'Upgrade scope'); + upgradeCmd.option( + 'latest', + 'list the latest version of packages, ignoring version ranges in package.json' + ); + upgradeCmd.option('pattern', 'upgrade packages that match pattern'); + upgradeCmd.option('scope', 'upgrade packages under the specified scope'); const upgradeInteractiveCmd = completion.command( 'upgrade-interactive', @@ -376,48 +490,75 @@ export function setupYarnCompletions(completion: PackageManagerCompletion) { export function setupBunCompletions(completion: PackageManagerCompletion) { // Package management - const addCmd = completion.command('add', 'Add packages'); - addCmd.option('development', 'Add to devDependencies', 'd'); - addCmd.option('optional', 'Add to optionalDependencies'); - addCmd.option('exact', 'Add exact version', 'E'); + const addCmd = completion.command( + 'add', + 'Add a dependency to package.json (bun a)' + ); + addCmd.option('development', 'Add dependency to "devDependencies"', 'd'); + addCmd.option('optional', 'Add dependency to "optionalDependencies"'); + addCmd.option('exact', 'Add the exact version instead of the ^range', 'E'); addCmd.option('global', 'Install globally', 'g'); - const removeCmd = completion.command('remove', 'Remove packages'); + const removeCmd = completion.command( + 'remove', + 'Remove a dependency from package.json (bun rm)' + ); removeCmd.argument('package', dependencyCompletion); removeCmd.option('global', 'Remove globally', 'g'); - const installCmd = completion.command('install', 'Install dependencies'); - installCmd.option('production', 'Production install'); - installCmd.option('frozen-lockfile', 'Use frozen lockfile'); - installCmd.option('dry-run', 'Dry run'); - installCmd.option('force', 'Force install'); - installCmd.option('silent', 'Silent install'); + const installCmd = completion.command( + 'install', + 'Install dependencies for a package.json (bun i)' + ); + installCmd.option('production', "Don't install devDependencies"); + installCmd.option('frozen-lockfile', 'Disallow changes to lockfile'); + installCmd.option('dry-run', "Don't install anything"); + installCmd.option( + 'force', + 'Always request the latest versions from the registry & reinstall all dependencies' + ); + installCmd.option('silent', "Don't log anything"); - const updateCmd = completion.command('update', 'Update packages'); + const updateCmd = completion.command( + 'update', + 'Update outdated dependencies' + ); updateCmd.argument('package', dependencyCompletion); updateCmd.option('global', 'Update global packages', 'g'); // Script execution and running - const runCmd = completion.command('run', 'Run scripts'); + const runCmd = completion.command('run', 'Execute a file with Bun'); runCmd.argument('script', scriptCompletion, true); - runCmd.option('silent', 'Silent output'); + runCmd.option('silent', "Don't log anything"); runCmd.option('bun', 'Use bun runtime'); - const xCmd = completion.command('x', 'Execute packages'); + const xCmd = completion.command( + 'x', + 'Execute a package binary (CLI), installing if needed (bunx)' + ); xCmd.option('bun', 'Use bun runtime'); // Bun-specific commands completion.command('dev', 'Development server'); - completion.command('build', 'Build project'); - completion.command('test', 'Run tests'); + completion.command( + 'build', + 'Bundle TypeScript & JavaScript into a single file' + ); + completion.command('test', 'Run unit tests with Bun'); // Project management - completion.command('create', 'Create new project'); - const initCmd = completion.command('init', 'Initialize project'); + completion.command('create', 'Create a new project from a template (bun c)'); + const initCmd = completion.command( + 'init', + 'Start an empty Bun project from a built-in template' + ); initCmd.option('yes', 'Use defaults', 'y'); // Publishing - const publishCmd = completion.command('publish', 'Publish package'); + const publishCmd = completion.command( + 'publish', + 'Publish a package to the npm registry' + ); publishCmd.option('tag', 'Publish with tag'); publishCmd.option('access', 'Set access level'); publishCmd.option('otp', 'One-time password'); @@ -425,15 +566,18 @@ export function setupBunCompletions(completion: PackageManagerCompletion) { completion.command('pack', 'Create tarball'); // Linking - completion.command('link', 'Link packages'); - completion.command('unlink', 'Unlink packages'); + completion.command('link', 'Register or link a local npm package'); + completion.command('unlink', 'Unregister a local npm package'); // Information const listCmd = completion.command('list', 'List packages'); listCmd.option('global', 'List global packages', 'g'); - completion.command('outdated', 'Check outdated packages'); - completion.command('audit', 'Security audit'); + completion.command( + 'outdated', + 'Display latest versions of outdated dependencies' + ); + completion.command('audit', 'Check installed packages for vulnerabilities'); // Configuration completion.command('config', 'Configuration'); @@ -441,14 +585,14 @@ export function setupBunCompletions(completion: PackageManagerCompletion) { // Bun runtime commands completion.command('bun', 'Run with Bun runtime'); completion.command('node', 'Node.js compatibility'); - completion.command('upgrade', 'Upgrade Bun'); + completion.command('upgrade', 'Upgrade to latest version of Bun.'); completion.command('completions', 'Generate completions'); completion.command('discord', 'Open Discord'); completion.command('help', 'Show help'); // File operations completion.command('install.cache', 'Cache operations'); - completion.command('pm', 'Package manager operations'); + completion.command('pm', 'Additional package management utilities'); // Other commands completion.command('start', 'Run start script'); From ece6de5280ba520a30ff93ce8c2e01c317afea50 Mon Sep 17 00:00:00 2001 From: AmirSa12 Date: Mon, 25 Aug 2025 20:38:24 +0330 Subject: [PATCH 2/8] trigger ci From f14d7d5adc39b1eb8cccab824714dc9fd55bb4b6 Mon Sep 17 00:00:00 2001 From: AmirSa12 Date: Sun, 31 Aug 2025 13:15:13 +0330 Subject: [PATCH 3/8] machanism change - parse --help --- bin/cli.ts | 2 +- bin/completion-handlers.ts | 652 ++++++------------------------------- 2 files changed, 107 insertions(+), 547 deletions(-) diff --git a/bin/cli.ts b/bin/cli.ts index cf4b414..27827a7 100644 --- a/bin/cli.ts +++ b/bin/cli.ts @@ -30,7 +30,7 @@ async function main() { if (dashIndex !== -1) { // Use the new PackageManagerCompletion wrapper const completion = new PackageManagerCompletion(packageManager); - setupCompletionForPackageManager(packageManager, completion); + await setupCompletionForPackageManager(packageManager, completion); const toComplete = process.argv.slice(dashIndex + 1); await completion.parse(toComplete); process.exit(0); diff --git a/bin/completion-handlers.ts b/bin/completion-handlers.ts index 9954fb1..e073000 100644 --- a/bin/completion-handlers.ts +++ b/bin/completion-handlers.ts @@ -1,5 +1,6 @@ import { PackageManagerCompletion } from './package-manager-completion.js'; import { readFileSync } from 'fs'; +import { execSync } from 'child_process'; // Helper functions for dynamic completions function getPackageJsonScripts(): string[] { @@ -37,565 +38,124 @@ const dependencyCompletion = async (complete: any) => { deps.forEach((dep) => complete(dep, '')); }; -export function setupCompletionForPackageManager( +export async function setupCompletionForPackageManager( packageManager: string, completion: PackageManagerCompletion ) { if (packageManager === 'pnpm') { - setupPnpmCompletions(completion); + await setupPnpmCompletions(completion); } else if (packageManager === 'npm') { - setupNpmCompletions(completion); + await setupNpmCompletions(completion); } else if (packageManager === 'yarn') { - setupYarnCompletions(completion); + await setupYarnCompletions(completion); } else if (packageManager === 'bun') { - setupBunCompletions(completion); + await setupBunCompletions(completion); } } -export function setupPnpmCompletions(completion: PackageManagerCompletion) { - // Package management - const addCmd = completion.command( - 'add', - 'Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency' - ); - addCmd.option('save-dev', 'Save package to your `devDependencies`', 'D'); - addCmd.option( - 'save-optional', - 'Save package to your `optionalDependencies`', - 'O' - ); - addCmd.option('save-exact', 'Install exact version', 'E'); - addCmd.option('global', 'Install as a global package', 'g'); - addCmd.option( - 'workspace', - 'Only adds the new dependency if it is found in the workspace' - ); - addCmd.option( - 'filter', - 'Restricts the scope to package names matching the given pattern' - ); - - const removeCmd = completion.command( - 'remove', - "Removes packages from node_modules and from the project's package.json" - ); - removeCmd.argument('package', dependencyCompletion); - removeCmd.option('global', 'Remove globally', 'g'); - - const installCmd = completion.command( - 'install', - 'Install all dependencies for a project' - ); - installCmd.option( - 'frozen-lockfile', - "Don't generate a lockfile and fail if an update is needed" - ); - installCmd.option( - 'prefer-frozen-lockfile', - 'If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation' - ); - installCmd.option( - 'production', - "Packages in `devDependencies` won't be installed" - ); - installCmd.option('dev', 'Only `devDependencies` are installed'); - installCmd.option('optional', '`optionalDependencies` are not installed'); - installCmd.option( - 'filter', - 'Restricts the scope to package names matching the given pattern' - ); - - const updateCmd = completion.command( - 'update', - 'Updates packages to their latest version based on the specified range' - ); - updateCmd.argument('package', dependencyCompletion); - updateCmd.option('latest', 'Ignore version ranges in package.json'); - updateCmd.option('global', 'Update globally installed packages', 'g'); - updateCmd.option( - 'interactive', - 'Show outdated dependencies and select which ones to update', - 'i' - ); - - // Script execution - const runCmd = completion.command('run', 'Runs a defined package script'); - runCmd.argument('script', scriptCompletion, true); - runCmd.option( - 'parallel', - 'Completely disregard concurrency and topological sorting, running a given script immediately in all matching packages with prefixed streaming output' - ); - runCmd.option( - 'stream', - 'Stream output from child processes immediately, prefixed with the originating package directory' - ); - runCmd.option( - 'filter', - 'Restricts the scope to package names matching the given pattern' - ); - - const execCmd = completion.command( - 'exec', - 'Executes a shell command in scope of a project' - ); - execCmd.option( - 'filter', - 'Restricts the scope to package names matching the given pattern' - ); - execCmd.option('parallel', 'Run in parallel'); - execCmd.option( - 'stream', - 'Stream output from child processes immediately, prefixed with the originating package directory' - ); - - completion.command('dlx', 'Run package without installing'); - - // Project management - completion.command('create', 'Create new project'); - completion.command('init', 'Initialize project'); - - // Publishing - const publishCmd = completion.command('publish', 'Publish package'); - publishCmd.option('tag', 'Publish with tag'); - publishCmd.option('access', 'Set access level'); - publishCmd.option('otp', 'One-time password'); - publishCmd.option('dry-run', 'Dry run'); - - const packCmd = completion.command('pack', 'Create tarball'); - packCmd.option('pack-destination', 'Destination directory'); - - // Linking - const linkCmd = completion.command('link', 'Link packages'); - linkCmd.option('global', 'Link globally', 'g'); - - const unlinkCmd = completion.command('unlink', 'Unlink packages'); - unlinkCmd.option('global', 'Unlink globally', 'g'); - - // Information - const listCmd = completion.command( - 'list', - 'Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure' - ); - listCmd.option( - 'depth', - 'How deep should levels of dependencies be inspected' - ); - listCmd.option('global', 'List global packages', 'g'); - listCmd.option('long', 'Show extended information'); - listCmd.option('parseable', 'Parseable output'); - listCmd.option('json', 'JSON output'); - - const outdatedCmd = completion.command( - 'outdated', - 'Check for outdated packages' - ); - outdatedCmd.option('global', 'Check global packages', 'g'); - outdatedCmd.option('long', 'Show extended information'); - - const auditCmd = completion.command( - 'audit', - 'Checks for known security issues with the installed packages' - ); - auditCmd.option('fix', 'Automatically fix vulnerabilities'); - auditCmd.option('json', 'JSON output'); - - // Workspace commands - completion.command('workspace', 'Workspace commands'); - - // Store management - completion.command('store', 'Store management'); - completion.command( - 'store status', - 'Checks for modified packages in the store' - ); - completion.command( - 'store prune', - 'Removes unreferenced (extraneous, orphan) packages from the store' - ); - completion.command( - 'store path', - 'Prints the path to the active store directory' - ); - - // Configuration - completion.command('config', 'Configuration'); - completion.command('config get', 'Get config value'); - completion.command('config set', 'Set config value'); - completion.command('config delete', 'Delete config value'); - completion.command('config list', 'List config'); - - // Other useful commands - completion.command('why', 'Explain why package is installed'); - completion.command('rebuild', 'Rebuild a package'); - completion.command('root', 'Prints the effective modules directory'); - completion.command('bin', 'Print bin directory'); - completion.command( - 'start', - 'Runs an arbitrary command specified in the package\'s "start" property of its "scripts" object' - ); - completion.command( - 'test', - 'Runs a package\'s "test" script, if one was provided' - ); - completion.command('restart', 'Run restart script'); - completion.command('stop', 'Run stop script'); -} - -export function setupNpmCompletions(completion: PackageManagerCompletion) { - // Package management - const installCmd = completion.command( - 'install', - 'install all the dependencies in your project' - ); - installCmd.option('save', 'Save to dependencies', 'S'); - installCmd.option('save-dev', 'Save to devDependencies', 'D'); - installCmd.option('save-optional', 'Save to optionalDependencies', 'O'); - installCmd.option('save-exact', 'Save exact version', 'E'); - installCmd.option('global', 'Install globally', 'g'); - installCmd.option('production', 'Production install'); - installCmd.option('only', 'Install only specific dependencies'); - - const uninstallCmd = completion.command('uninstall', 'Remove a package'); - uninstallCmd.argument('package', dependencyCompletion); - uninstallCmd.option('save', 'Remove from dependencies', 'S'); - uninstallCmd.option('save-dev', 'Remove from devDependencies', 'D'); - uninstallCmd.option('global', 'Remove globally', 'g'); - - const updateCmd = completion.command('update', 'Update packages'); - updateCmd.argument('package', dependencyCompletion); - updateCmd.option('global', 'Update global packages', 'g'); - - // Script execution - const runCmd = completion.command('run', 'run the script named '); - runCmd.argument('script', scriptCompletion, true); - - const runScriptCmd = completion.command('run-script', 'Run scripts'); - runScriptCmd.argument('script', scriptCompletion, true); - - completion.command('exec', 'Execute command'); - - // Project management - const initCmd = completion.command('init', 'Initialize project'); - initCmd.option('yes', 'Use defaults', 'y'); - initCmd.option('scope', 'Set scope'); - - // Publishing - const publishCmd = completion.command('publish', 'Publish package'); - publishCmd.option('tag', 'Publish with tag'); - publishCmd.option('access', 'Set access level'); - publishCmd.option('otp', 'One-time password'); - publishCmd.option('dry-run', 'Dry run'); - - completion.command('pack', 'Create tarball'); - - // Linking - completion.command('link', 'Link packages'); - completion.command('unlink', 'Unlink packages'); - - // Information - const listCmd = completion.command('list', 'List packages'); - listCmd.option('depth', 'Max depth'); - listCmd.option('global', 'List global packages', 'g'); - listCmd.option('long', 'Show extended information'); - listCmd.option('parseable', 'Parseable output'); - listCmd.option('json', 'JSON output'); - - const lsCmd = completion.command('ls', 'List packages (alias)'); - lsCmd.option('depth', 'Max depth'); - lsCmd.option('global', 'List global packages', 'g'); - - const outdatedCmd = completion.command('outdated', 'Check outdated packages'); - outdatedCmd.option('global', 'Check global packages', 'g'); - - const auditCmd = completion.command('audit', 'Security audit'); - auditCmd.option('fix', 'Fix vulnerabilities'); - auditCmd.option('json', 'JSON output'); - - // Configuration - completion.command('config', 'Configuration'); - completion.command('config get', 'Get config value'); - completion.command('config set', 'Set config value'); - completion.command('config delete', 'Delete config value'); - completion.command('config list', 'List config'); - - // Other commands - completion.command('version', 'Bump version'); - completion.command('view', 'View package info'); - completion.command('search', 'Search packages'); - completion.command('whoami', 'Display username'); - completion.command('login', 'Login to registry'); - completion.command('logout', 'Logout from registry'); - completion.command('adduser', 'Add user'); - completion.command('owner', 'Manage package owners'); - completion.command('deprecate', 'Deprecate package'); - completion.command('dist-tag', 'Manage distribution tags'); - completion.command('cache', 'Manage cache'); - completion.command('completion', 'Tab completion'); - completion.command('explore', 'Browse package'); - completion.command('docs', 'Open documentation'); - completion.command('repo', 'Open repository'); - completion.command('bugs', 'Open bug tracker'); - completion.command('help', 'Get help'); - completion.command('root', 'Print root directory'); - completion.command('prefix', 'Print prefix'); - completion.command('bin', 'Print bin directory'); - completion.command('fund', 'Fund packages'); - completion.command('find-dupes', 'Find duplicate packages'); - completion.command('dedupe', 'Deduplicate packages'); - completion.command('prune', 'Remove extraneous packages'); - completion.command('rebuild', 'Rebuild packages'); - completion.command('start', 'Run start script'); - completion.command('stop', 'Run stop script'); - completion.command('test', "run this project's tests"); - completion.command('restart', 'Run restart script'); +export async function setupPnpmCompletions( + completion: PackageManagerCompletion +) { + try { + const commandsWithDescriptions = await getPnpmCommandsFromMainHelp(); + + for (const [command, description] of Object.entries( + commandsWithDescriptions + )) { + const cmd = completion.command(command, description); + + if (['remove', 'rm', 'update', 'up'].includes(command)) { + cmd.argument('package', dependencyCompletion); + } + if (command === 'run') { + cmd.argument('script', scriptCompletion, true); + } + } + } catch (error) { + console.error('Failed to setup pnpm completions:', error.message); + } } -export function setupYarnCompletions(completion: PackageManagerCompletion) { - // Package management - const addCmd = completion.command( - 'add', - 'Installs a package and any packages that it depends on.' - ); - addCmd.option('dev', 'save package to your `devDependencies`', 'D'); - addCmd.option('peer', 'save package to your `peerDependencies`', 'P'); - addCmd.option('optional', 'save package to your `optionalDependencies`', 'O'); - addCmd.option('exact', 'install exact version', 'E'); - addCmd.option( - 'tilde', - 'install most recent release with the same minor version', - 'T' - ); - - const removeCmd = completion.command( - 'remove', - 'Removes a package from your direct dependencies updating your package.json and yarn.lock.' - ); - removeCmd.argument('package', dependencyCompletion); - - const installCmd = completion.command( - 'install', - 'Yarn install is used to install all dependencies for a project.' - ); - installCmd.option( - 'frozen-lockfile', - "don't generate a lockfile and fail if an update is needed" - ); - installCmd.option( - 'prefer-offline', - 'use network only if dependencies are not available in local cache' - ); - installCmd.option('production', 'Production install'); - installCmd.option('pure-lockfile', "don't generate a lockfile"); - installCmd.option( - 'focus', - 'Focus on a single workspace by installing remote copies of its sibling workspaces' - ); - installCmd.option('har', 'save HAR output of network traffic'); - - const upgradeCmd = completion.command( - 'upgrade', - 'Upgrades packages to their latest version based on the specified range.' - ); - upgradeCmd.argument('package', dependencyCompletion); - upgradeCmd.option( - 'latest', - 'list the latest version of packages, ignoring version ranges in package.json' - ); - upgradeCmd.option('pattern', 'upgrade packages that match pattern'); - upgradeCmd.option('scope', 'upgrade packages under the specified scope'); - - const upgradeInteractiveCmd = completion.command( - 'upgrade-interactive', - 'Interactive upgrade' - ); - upgradeInteractiveCmd.option('latest', 'Show latest versions'); - - // Script execution - const runCmd = completion.command('run', 'Run scripts'); - runCmd.argument('script', scriptCompletion, true); - - completion.command('exec', 'Execute command'); - - // Project management - completion.command('create', 'Create new project'); - const initCmd = completion.command('init', 'Initialize project'); - initCmd.option('yes', 'Use defaults', 'y'); - initCmd.option('private', 'Create private package', 'p'); - - // Publishing - const publishCmd = completion.command('publish', 'Publish package'); - publishCmd.option('tag', 'Publish with tag'); - publishCmd.option('access', 'Set access level'); - publishCmd.option('new-version', 'Set new version'); - - const packCmd = completion.command('pack', 'Create tarball'); - packCmd.option('filename', 'Output filename'); - - // Linking - completion.command('link', 'Link packages'); - completion.command('unlink', 'Unlink packages'); - - // Information - const listCmd = completion.command('list', 'List packages'); - listCmd.option('depth', 'Max depth'); - listCmd.option('pattern', 'Filter pattern'); - - completion.command('info', 'Show package info'); - completion.command('outdated', 'Check outdated packages'); - const auditCmd = completion.command('audit', 'Security audit'); - auditCmd.option('level', 'Minimum severity level'); - - // Workspace commands - completion.command('workspace', 'Workspace commands'); - completion.command('workspaces', 'Workspaces commands'); - completion.command('workspaces info', 'Workspace info'); - completion.command('workspaces run', 'Run in workspaces'); - - // Configuration - completion.command('config', 'Configuration'); - completion.command('config get', 'Get config value'); - completion.command('config set', 'Set config value'); - completion.command('config delete', 'Delete config value'); - completion.command('config list', 'List config'); - - // Cache management - completion.command('cache', 'Cache management'); - completion.command('cache list', 'List cache'); - completion.command('cache dir', 'Cache directory'); - completion.command('cache clean', 'Clean cache'); - - // Other commands - completion.command('version', 'Show version'); - completion.command('versions', 'Show all versions'); - completion.command('why', 'Explain installation'); - completion.command('owner', 'Manage owners'); - completion.command('team', 'Manage teams'); - completion.command('login', 'Login to registry'); - completion.command('logout', 'Logout from registry'); - completion.command('tag', 'Manage tags'); - completion.command('global', 'Global packages'); - completion.command('bin', 'Print bin directory'); - completion.command('dir', 'Print modules directory'); - completion.command('licenses', 'List licenses'); - completion.command('generate-lock-entry', 'Generate lock entry'); - completion.command('check', 'Verify package tree'); - completion.command('import', 'Import from npm'); - completion.command('install-peerdeps', 'Install peer dependencies'); - completion.command('autoclean', 'Clean unnecessary files'); - completion.command('policies', 'Policies'); - completion.command('start', 'Run start script'); - completion.command('test', 'Run test script'); - completion.command('node', 'Run node'); +async function getPnpmCommandsFromMainHelp(): Promise> { + try { + const output = execSync('pnpm --help', { encoding: 'utf8', timeout: 3000 }); + const lines = output.split('\n'); + const commands: Record = {}; + + let inCommandSection = false; + let currentCommand = ''; + let currentDescription = ''; + + for (let i = 0; i < lines.length; i++) { + const line = lines[i]; + + if ( + line.match( + /^(Manage your dependencies|Review your dependencies|Run your scripts|Other|Manage your store):/ + ) + ) { + inCommandSection = true; + continue; + } + + // exclude options section + if (line.match(/^Options:/)) { + break; + } + + if (inCommandSection && line.trim()) { + const commandMatch = line.match(/^\s+([a-z,\s-]+?)\s{8,}(.+)$/); + if (commandMatch) { + if (currentCommand && currentDescription) { + const commandNames = currentCommand + .split(',') + .map((c) => c.trim()) + .filter((c) => c); + for (const cmd of commandNames) { + commands[cmd] = currentDescription.trim(); + } + } + + const [, cmdPart, description] = commandMatch; + currentCommand = cmdPart; + currentDescription = description; + + // sometimes the description is on multiple lines + let j = i + 1; + while (j < lines.length && lines[j].match(/^\s{25,}/)) { + currentDescription += ' ' + lines[j].trim(); + j++; + } + i = j - 1; + } + } + } + + if (currentCommand && currentDescription) { + const commandNames = currentCommand + .split(',') + .map((c) => c.trim()) + .filter((c) => c); + for (const cmd of commandNames) { + commands[cmd] = currentDescription.trim(); + } + } + + return commands; + } catch (error) { + console.error('Error parsing pnpm help:', error.message); + return {}; + } } -export function setupBunCompletions(completion: PackageManagerCompletion) { - // Package management - const addCmd = completion.command( - 'add', - 'Add a dependency to package.json (bun a)' - ); - addCmd.option('development', 'Add dependency to "devDependencies"', 'd'); - addCmd.option('optional', 'Add dependency to "optionalDependencies"'); - addCmd.option('exact', 'Add the exact version instead of the ^range', 'E'); - addCmd.option('global', 'Install globally', 'g'); - - const removeCmd = completion.command( - 'remove', - 'Remove a dependency from package.json (bun rm)' - ); - removeCmd.argument('package', dependencyCompletion); - removeCmd.option('global', 'Remove globally', 'g'); - - const installCmd = completion.command( - 'install', - 'Install dependencies for a package.json (bun i)' - ); - installCmd.option('production', "Don't install devDependencies"); - installCmd.option('frozen-lockfile', 'Disallow changes to lockfile'); - installCmd.option('dry-run', "Don't install anything"); - installCmd.option( - 'force', - 'Always request the latest versions from the registry & reinstall all dependencies' - ); - installCmd.option('silent', "Don't log anything"); - - const updateCmd = completion.command( - 'update', - 'Update outdated dependencies' - ); - updateCmd.argument('package', dependencyCompletion); - updateCmd.option('global', 'Update global packages', 'g'); - - // Script execution and running - const runCmd = completion.command('run', 'Execute a file with Bun'); - runCmd.argument('script', scriptCompletion, true); - runCmd.option('silent', "Don't log anything"); - runCmd.option('bun', 'Use bun runtime'); - - const xCmd = completion.command( - 'x', - 'Execute a package binary (CLI), installing if needed (bunx)' - ); - xCmd.option('bun', 'Use bun runtime'); - - // Bun-specific commands - completion.command('dev', 'Development server'); - completion.command( - 'build', - 'Bundle TypeScript & JavaScript into a single file' - ); - completion.command('test', 'Run unit tests with Bun'); - - // Project management - completion.command('create', 'Create a new project from a template (bun c)'); - const initCmd = completion.command( - 'init', - 'Start an empty Bun project from a built-in template' - ); - initCmd.option('yes', 'Use defaults', 'y'); - - // Publishing - const publishCmd = completion.command( - 'publish', - 'Publish a package to the npm registry' - ); - publishCmd.option('tag', 'Publish with tag'); - publishCmd.option('access', 'Set access level'); - publishCmd.option('otp', 'One-time password'); - - completion.command('pack', 'Create tarball'); - - // Linking - completion.command('link', 'Register or link a local npm package'); - completion.command('unlink', 'Unregister a local npm package'); - - // Information - const listCmd = completion.command('list', 'List packages'); - listCmd.option('global', 'List global packages', 'g'); - - completion.command( - 'outdated', - 'Display latest versions of outdated dependencies' - ); - completion.command('audit', 'Check installed packages for vulnerabilities'); - - // Configuration - completion.command('config', 'Configuration'); - - // Bun runtime commands - completion.command('bun', 'Run with Bun runtime'); - completion.command('node', 'Node.js compatibility'); - completion.command('upgrade', 'Upgrade to latest version of Bun.'); - completion.command('completions', 'Generate completions'); - completion.command('discord', 'Open Discord'); - completion.command('help', 'Show help'); +export async function setupNpmCompletions( + completion: PackageManagerCompletion +) {} - // File operations - completion.command('install.cache', 'Cache operations'); - completion.command('pm', 'Additional package management utilities'); +export async function setupYarnCompletions( + completion: PackageManagerCompletion +) {} - // Other commands - completion.command('start', 'Run start script'); - completion.command('stop', 'Run stop script'); - completion.command('restart', 'Run restart script'); -} +export async function setupBunCompletions( + completion: PackageManagerCompletion +) {} From 35dbac82431ac58ce1826f1209aaaf0221cb81a1 Mon Sep 17 00:00:00 2001 From: AmirSa12 Date: Sun, 31 Aug 2025 13:25:17 +0330 Subject: [PATCH 4/8] types --- bin/completion-handlers.ts | 17 +++++++++++++---- src/t.ts | 2 +- 2 files changed, 14 insertions(+), 5 deletions(-) diff --git a/bin/completion-handlers.ts b/bin/completion-handlers.ts index e073000..e943da9 100644 --- a/bin/completion-handlers.ts +++ b/bin/completion-handlers.ts @@ -1,6 +1,7 @@ import { PackageManagerCompletion } from './package-manager-completion.js'; import { readFileSync } from 'fs'; import { execSync } from 'child_process'; +import type { Complete } from '../src/t.js'; // Helper functions for dynamic completions function getPackageJsonScripts(): string[] { @@ -28,12 +29,12 @@ function getPackageJsonDependencies(): string[] { } // Common completion handlers -const scriptCompletion = async (complete: any) => { +const scriptCompletion = async (complete: Complete) => { const scripts = getPackageJsonScripts(); scripts.forEach((script) => complete(script, `Run ${script} script`)); }; -const dependencyCompletion = async (complete: any) => { +const dependencyCompletion = async (complete: Complete) => { const deps = getPackageJsonDependencies(); deps.forEach((dep) => complete(dep, '')); }; @@ -72,7 +73,11 @@ export async function setupPnpmCompletions( } } } catch (error) { - console.error('Failed to setup pnpm completions:', error.message); + if (error instanceof Error) { + console.error('Failed to setup pnpm completions:', error.message); + } else { + console.error('Failed to setup pnpm completions:', error); + } } } @@ -143,7 +148,11 @@ async function getPnpmCommandsFromMainHelp(): Promise> { return commands; } catch (error) { - console.error('Error parsing pnpm help:', error.message); + if (error instanceof Error) { + console.error('Failed to setup pnpm completions:', error.message); + } else { + console.error('Failed to setup pnpm completions:', error); + } return {}; } } diff --git a/src/t.ts b/src/t.ts index 65eda28..cbfc6c9 100644 --- a/src/t.ts +++ b/src/t.ts @@ -12,7 +12,7 @@ export const ShellCompDirective = { export type OptionsMap = Map; -type Complete = (value: string, description: string) => void; +export type Complete = (value: string, description: string) => void; export type OptionHandler = ( this: Option, From 32911050eed8bae2115c603d6914898a64ad3a52 Mon Sep 17 00:00:00 2001 From: AmirSa12 Date: Mon, 1 Sep 2025 21:40:06 +0330 Subject: [PATCH 5/8] fix/descriptions --- bin/completion-handlers.ts | 103 +++++++++++++++++++++++++++++++++++++ 1 file changed, 103 insertions(+) diff --git a/bin/completion-handlers.ts b/bin/completion-handlers.ts index e943da9..0aefbdf 100644 --- a/bin/completion-handlers.ts +++ b/bin/completion-handlers.ts @@ -71,6 +71,10 @@ export async function setupPnpmCompletions( if (command === 'run') { cmd.argument('script', scriptCompletion, true); } + + // TODO: AMIR: MANUAL OPTIONS ? + + setupLazyOptionLoading(cmd, command); } } catch (error) { if (error instanceof Error) { @@ -168,3 +172,102 @@ export async function setupYarnCompletions( export async function setupBunCompletions( completion: PackageManagerCompletion ) {} + +function setupLazyOptionLoading(cmd: any, command: string) { + cmd._lazyCommand = command; + cmd._optionsLoaded = false; + + const originalOptions = cmd.options; + Object.defineProperty(cmd, 'options', { + get() { + if (!this._optionsLoaded) { + this._optionsLoaded = true; + loadDynamicOptionsSync(this, this._lazyCommand); + } + return originalOptions; + }, + configurable: true, + }); +} + +function loadDynamicOptionsSync(cmd: any, command: string) { + try { + const output = execSync(`pnpm ${command} --help`, { + encoding: 'utf8', + timeout: 3000, + }); + const lines = output.split('\n'); + let inOptionsSection = false; + let currentOption = ''; + let currentDescription = ''; + let currentShortFlag: string | undefined; + + for (let i = 0; i < lines.length; i++) { + const line = lines[i]; + + if (line.match(/^Options:/)) { + inOptionsSection = true; + continue; + } + + if (inOptionsSection && line.match(/^[A-Z][a-z].*:/)) { + break; + } + + if (inOptionsSection && line.trim()) { + const optionMatch = line.match( + /^\s*(?:-([A-Za-z]),\s*)?--([a-z-]+)(?!\s+<|\s+\[)\s+(.*)/ + ); + if (optionMatch) { + if (currentOption && currentDescription) { + const existingOption = cmd.options.get(currentOption); + if (!existingOption) { + cmd.option( + currentOption, + currentDescription.trim(), + currentShortFlag + ); + } + } + + const [, shortFlag, optionName, description] = optionMatch; + + // TODO: AMIR: lets only proccess options that don't have ? + if (!line.includes('<') && !line.includes('[')) { + currentOption = optionName; + currentShortFlag = shortFlag || undefined; + currentDescription = description; + + let j = i + 1; + while ( + j < lines.length && + lines[j].match(/^\s{25,}/) && + !lines[j].match(/^\s*(?:-[A-Za-z],\s*)?--[a-z-]/) + ) { + currentDescription += ' ' + lines[j].trim(); + j++; + } + i = j - 1; + } else { + currentOption = ''; + currentDescription = ''; + currentShortFlag = undefined; + } + } + } + } + + if (currentOption && currentDescription) { + const existingOption = cmd.options.get(currentOption); + if (!existingOption) { + cmd.option(currentOption, currentDescription.trim(), currentShortFlag); + } + } + } catch (error) { + if (error instanceof Error) { + console.error(`Failed to load options for ${command}:`, error.message); + } else { + console.error(`Failed to load options for ${command}:`, error); + } + } +} From 9a4d53f11ea0ab88beb0f5480fe4a1b992d39ae3 Mon Sep 17 00:00:00 2001 From: AmirSa12 Date: Sat, 6 Sep 2025 12:01:33 +0330 Subject: [PATCH 6/8] big update --- bin/completion-handlers.ts | 292 +- bin/completions/completion-producers.ts | 21 + bin/handlers/bun-handler.ts | 5 + bin/handlers/npm-handler.ts | 5 + bin/handlers/pnpm-handler.ts | 217 ++ bin/handlers/yarn-handler.ts | 5 + bin/utils/package-json-utils.ts | 25 + bin/utils/text-utils.ts | 35 + completion-debug.log | 3524 +++++++++++++++++++++++ 9 files changed, 3863 insertions(+), 266 deletions(-) create mode 100644 bin/completions/completion-producers.ts create mode 100644 bin/handlers/bun-handler.ts create mode 100644 bin/handlers/npm-handler.ts create mode 100644 bin/handlers/pnpm-handler.ts create mode 100644 bin/handlers/yarn-handler.ts create mode 100644 bin/utils/package-json-utils.ts create mode 100644 bin/utils/text-utils.ts create mode 100644 completion-debug.log diff --git a/bin/completion-handlers.ts b/bin/completion-handlers.ts index 0aefbdf..28b6c97 100644 --- a/bin/completion-handlers.ts +++ b/bin/completion-handlers.ts @@ -1,273 +1,33 @@ -import { PackageManagerCompletion } from './package-manager-completion.js'; -import { readFileSync } from 'fs'; -import { execSync } from 'child_process'; -import type { Complete } from '../src/t.js'; +/** + * Main entry point for package manager completion handlers + * Delegates to specific package manager handlers + */ -// Helper functions for dynamic completions -function getPackageJsonScripts(): string[] { - try { - const packageJson = JSON.parse(readFileSync('package.json', 'utf8')); - return Object.keys(packageJson.scripts || {}); - } catch { - return []; - } -} - -function getPackageJsonDependencies(): string[] { - try { - const packageJson = JSON.parse(readFileSync('package.json', 'utf8')); - const deps = { - ...packageJson.dependencies, - ...packageJson.devDependencies, - ...packageJson.peerDependencies, - ...packageJson.optionalDependencies, - }; - return Object.keys(deps); - } catch { - return []; - } -} - -// Common completion handlers -const scriptCompletion = async (complete: Complete) => { - const scripts = getPackageJsonScripts(); - scripts.forEach((script) => complete(script, `Run ${script} script`)); -}; - -const dependencyCompletion = async (complete: Complete) => { - const deps = getPackageJsonDependencies(); - deps.forEach((dep) => complete(dep, '')); -}; +import type { PackageManagerCompletion } from './package-manager-completion.js'; +import { setupPnpmCompletions } from './handlers/pnpm-handler.js'; +import { setupNpmCompletions } from './handlers/npm-handler.js'; +import { setupYarnCompletions } from './handlers/yarn-handler.js'; +import { setupBunCompletions } from './handlers/bun-handler.js'; export async function setupCompletionForPackageManager( packageManager: string, completion: PackageManagerCompletion -) { - if (packageManager === 'pnpm') { - await setupPnpmCompletions(completion); - } else if (packageManager === 'npm') { - await setupNpmCompletions(completion); - } else if (packageManager === 'yarn') { - await setupYarnCompletions(completion); - } else if (packageManager === 'bun') { - await setupBunCompletions(completion); - } -} - -export async function setupPnpmCompletions( - completion: PackageManagerCompletion -) { - try { - const commandsWithDescriptions = await getPnpmCommandsFromMainHelp(); - - for (const [command, description] of Object.entries( - commandsWithDescriptions - )) { - const cmd = completion.command(command, description); - - if (['remove', 'rm', 'update', 'up'].includes(command)) { - cmd.argument('package', dependencyCompletion); - } - if (command === 'run') { - cmd.argument('script', scriptCompletion, true); - } - - // TODO: AMIR: MANUAL OPTIONS ? - - setupLazyOptionLoading(cmd, command); - } - } catch (error) { - if (error instanceof Error) { - console.error('Failed to setup pnpm completions:', error.message); - } else { - console.error('Failed to setup pnpm completions:', error); - } - } -} - -async function getPnpmCommandsFromMainHelp(): Promise> { - try { - const output = execSync('pnpm --help', { encoding: 'utf8', timeout: 3000 }); - const lines = output.split('\n'); - const commands: Record = {}; - - let inCommandSection = false; - let currentCommand = ''; - let currentDescription = ''; - - for (let i = 0; i < lines.length; i++) { - const line = lines[i]; - - if ( - line.match( - /^(Manage your dependencies|Review your dependencies|Run your scripts|Other|Manage your store):/ - ) - ) { - inCommandSection = true; - continue; - } - - // exclude options section - if (line.match(/^Options:/)) { - break; - } - - if (inCommandSection && line.trim()) { - const commandMatch = line.match(/^\s+([a-z,\s-]+?)\s{8,}(.+)$/); - if (commandMatch) { - if (currentCommand && currentDescription) { - const commandNames = currentCommand - .split(',') - .map((c) => c.trim()) - .filter((c) => c); - for (const cmd of commandNames) { - commands[cmd] = currentDescription.trim(); - } - } - - const [, cmdPart, description] = commandMatch; - currentCommand = cmdPart; - currentDescription = description; - - // sometimes the description is on multiple lines - let j = i + 1; - while (j < lines.length && lines[j].match(/^\s{25,}/)) { - currentDescription += ' ' + lines[j].trim(); - j++; - } - i = j - 1; - } - } - } - - if (currentCommand && currentDescription) { - const commandNames = currentCommand - .split(',') - .map((c) => c.trim()) - .filter((c) => c); - for (const cmd of commandNames) { - commands[cmd] = currentDescription.trim(); - } - } - - return commands; - } catch (error) { - if (error instanceof Error) { - console.error('Failed to setup pnpm completions:', error.message); - } else { - console.error('Failed to setup pnpm completions:', error); - } - return {}; - } -} - -export async function setupNpmCompletions( - completion: PackageManagerCompletion -) {} - -export async function setupYarnCompletions( - completion: PackageManagerCompletion -) {} - -export async function setupBunCompletions( - completion: PackageManagerCompletion -) {} - -function setupLazyOptionLoading(cmd: any, command: string) { - cmd._lazyCommand = command; - cmd._optionsLoaded = false; - - const originalOptions = cmd.options; - Object.defineProperty(cmd, 'options', { - get() { - if (!this._optionsLoaded) { - this._optionsLoaded = true; - loadDynamicOptionsSync(this, this._lazyCommand); - } - return originalOptions; - }, - configurable: true, - }); -} - -function loadDynamicOptionsSync(cmd: any, command: string) { - try { - const output = execSync(`pnpm ${command} --help`, { - encoding: 'utf8', - timeout: 3000, - }); - const lines = output.split('\n'); - let inOptionsSection = false; - let currentOption = ''; - let currentDescription = ''; - let currentShortFlag: string | undefined; - - for (let i = 0; i < lines.length; i++) { - const line = lines[i]; - - if (line.match(/^Options:/)) { - inOptionsSection = true; - continue; - } - - if (inOptionsSection && line.match(/^[A-Z][a-z].*:/)) { - break; - } - - if (inOptionsSection && line.trim()) { - const optionMatch = line.match( - /^\s*(?:-([A-Za-z]),\s*)?--([a-z-]+)(?!\s+<|\s+\[)\s+(.*)/ - ); - if (optionMatch) { - if (currentOption && currentDescription) { - const existingOption = cmd.options.get(currentOption); - if (!existingOption) { - cmd.option( - currentOption, - currentDescription.trim(), - currentShortFlag - ); - } - } - - const [, shortFlag, optionName, description] = optionMatch; - - // TODO: AMIR: lets only proccess options that don't have ? - if (!line.includes('<') && !line.includes('[')) { - currentOption = optionName; - currentShortFlag = shortFlag || undefined; - currentDescription = description; - - let j = i + 1; - while ( - j < lines.length && - lines[j].match(/^\s{25,}/) && - !lines[j].match(/^\s*(?:-[A-Za-z],\s*)?--[a-z-]/) - ) { - currentDescription += ' ' + lines[j].trim(); - j++; - } - i = j - 1; - } else { - currentOption = ''; - currentDescription = ''; - currentShortFlag = undefined; - } - } - } - } - - if (currentOption && currentDescription) { - const existingOption = cmd.options.get(currentOption); - if (!existingOption) { - cmd.option(currentOption, currentDescription.trim(), currentShortFlag); - } - } - } catch (error) { - if (error instanceof Error) { - console.error(`Failed to load options for ${command}:`, error.message); - } else { - console.error(`Failed to load options for ${command}:`, error); - } +): Promise { + switch (packageManager) { + case 'pnpm': + await setupPnpmCompletions(completion); + break; + case 'npm': + await setupNpmCompletions(completion); + break; + case 'yarn': + await setupYarnCompletions(completion); + break; + case 'bun': + await setupBunCompletions(completion); + break; + default: + // silently ignore unknown package managers + break; } } diff --git a/bin/completions/completion-producers.ts b/bin/completions/completion-producers.ts new file mode 100644 index 0000000..4450250 --- /dev/null +++ b/bin/completions/completion-producers.ts @@ -0,0 +1,21 @@ +import type { Complete } from '../../src/t.js'; +import { + getPackageJsonScripts, + getPackageJsonDependencies, +} from '../utils/package-json-utils.js'; + +// provides completions for npm scripts from package.json.. like: start,dev,build +export const packageJsonScriptCompletion = async ( + complete: Complete +): Promise => { + getPackageJsonScripts().forEach((script) => + complete(script, `Run ${script} script`) + ); +}; + +// provides completions for package dependencies from package.json.. `pnpm add ` +export const packageJsonDependencyCompletion = async ( + complete: Complete +): Promise => { + getPackageJsonDependencies().forEach((dep) => complete(dep, '')); +}; diff --git a/bin/handlers/bun-handler.ts b/bin/handlers/bun-handler.ts new file mode 100644 index 0000000..225b049 --- /dev/null +++ b/bin/handlers/bun-handler.ts @@ -0,0 +1,5 @@ +import type { PackageManagerCompletion } from '../package-manager-completion.js'; + +export async function setupBunCompletions( + completion: PackageManagerCompletion +): Promise {} diff --git a/bin/handlers/npm-handler.ts b/bin/handlers/npm-handler.ts new file mode 100644 index 0000000..e4528e9 --- /dev/null +++ b/bin/handlers/npm-handler.ts @@ -0,0 +1,5 @@ +import type { PackageManagerCompletion } from '../package-manager-completion.js'; + +export async function setupNpmCompletions( + completion: PackageManagerCompletion +): Promise {} diff --git a/bin/handlers/pnpm-handler.ts b/bin/handlers/pnpm-handler.ts new file mode 100644 index 0000000..e9b01fa --- /dev/null +++ b/bin/handlers/pnpm-handler.ts @@ -0,0 +1,217 @@ +import { execFile, execFileSync } from 'child_process'; +import { promisify } from 'util'; +import type { PackageManagerCompletion } from '../package-manager-completion.js'; +import { + packageJsonScriptCompletion, + packageJsonDependencyCompletion, +} from '../completions/completion-producers.js'; +import { + stripAnsiEscapes, + measureIndent, + parseAliasList, + COMMAND_ROW_RE, + OPTION_ROW_RE, + OPTION_HEAD_RE, + type ParsedOption, +} from '../utils/text-utils.js'; + +const execFileP = promisify(execFile); + +// we parse the pnpm help text to extract commands and their descriptions! +export function parsePnpmHelp(helpText: string): Record { + const helpLines = stripAnsiEscapes(helpText).split(/\r?\n/); + + // we find the earliest description column across command rows. + let descColumnIndex = Number.POSITIVE_INFINITY; + for (const line of helpLines) { + const rowMatch = line.match(COMMAND_ROW_RE); + if (!rowMatch) continue; + const descColumnIndexOnThisLine = line.indexOf(rowMatch[2]); + if ( + descColumnIndexOnThisLine >= 0 && + descColumnIndexOnThisLine < descColumnIndex + ) { + descColumnIndex = descColumnIndexOnThisLine; + } + } + if (!Number.isFinite(descColumnIndex)) return {}; + + // we fold rows, and join continuation lines aligned to descColumnIndex or deeper. + type PendingRow = { names: string[]; desc: string } | null; + let pendingRow: PendingRow = null; + + const commandMap = new Map(); + const flushPendingRow = () => { + if (!pendingRow) return; + const desc = pendingRow.desc.trim(); + for (const name of pendingRow.names) commandMap.set(name, desc); + pendingRow = null; + }; + + for (const line of helpLines) { + if (/^\s*Options:/i.test(line)) break; // we stop at options + + // we match the command row + const rowMatch = line.match(COMMAND_ROW_RE); + if (rowMatch) { + flushPendingRow(); + pendingRow = { + names: parseAliasList(rowMatch[1]), + desc: rowMatch[2].trim(), + }; + continue; + } + + // we join continuation lines aligned to descColumnIndex or deeper + if (pendingRow) { + const indentWidth = measureIndent(line); + if (indentWidth >= descColumnIndex && line.trim()) { + pendingRow.desc += ' ' + line.trim(); + } + } + } + // we flush the pending row and return the command map + flushPendingRow(); + + return Object.fromEntries(commandMap); +} + +// now we get the pnpm commands from the main help output +export async function getPnpmCommandsFromMainHelp(): Promise< + Record +> { + try { + const { stdout } = await execFileP('pnpm', ['--help'], { + encoding: 'utf8', + timeout: 500, + maxBuffer: 4 * 1024 * 1024, + }); + return parsePnpmHelp(stdout); + } catch { + return {}; + } +} + +// here we parse the pnpm options from the help text +export function parsePnpmOptions( + helpText: string, + { flagsOnly = true }: { flagsOnly?: boolean } = {} +): ParsedOption[] { + // we strip the ANSI escapes from the help text + const helpLines = stripAnsiEscapes(helpText).split(/\r?\n/); + + // we find the earliest description column among option rows we care about + let descColumnIndex = Number.POSITIVE_INFINITY; + for (const line of helpLines) { + const optionMatch = line.match(OPTION_ROW_RE); + if (!optionMatch) continue; + if (flagsOnly && optionMatch.groups?.val) continue; // skip value-taking options, we will add them manually with their value + const descColumnIndexOnThisLine = line.indexOf(optionMatch.groups!.desc); + if ( + descColumnIndexOnThisLine >= 0 && + descColumnIndexOnThisLine < descColumnIndex + ) { + descColumnIndex = descColumnIndexOnThisLine; + } + } + if (!Number.isFinite(descColumnIndex)) return []; + + // we fold the option rows and join the continuations + const optionsOut: ParsedOption[] = []; + let pendingOption: ParsedOption | null = null; + + const flushPendingOption = () => { + if (!pendingOption) return; + pendingOption.desc = pendingOption.desc.trim(); + optionsOut.push(pendingOption); + pendingOption = null; + }; + + // we match the option row + for (const line of helpLines) { + const optionMatch = line.match(OPTION_ROW_RE); + if (optionMatch) { + if (flagsOnly && optionMatch.groups?.val) continue; + flushPendingOption(); + pendingOption = { + short: optionMatch.groups?.short || undefined, + long: optionMatch.groups!.long, + desc: optionMatch.groups!.desc.trim(), + }; + continue; + } + + // we join the continuations + if (pendingOption) { + const indentWidth = measureIndent(line); + const startsNewOption = OPTION_HEAD_RE.test(line); + if (indentWidth >= descColumnIndex && line.trim() && !startsNewOption) { + pendingOption.desc += ' ' + line.trim(); + } + } + } + // we flush the pending option + flushPendingOption(); + + return optionsOut; +} + +// we load the dynamic options synchronously when requested ( separated from the command loading ) +export function loadDynamicOptionsSync(cmd: any, command: string): void { + try { + const stdout = execFileSync('pnpm', [command, '--help'], { + encoding: 'utf8', + timeout: 500, + }); + + const parsedOptions = parsePnpmOptions(stdout, { flagsOnly: true }); + + for (const { long, short, desc } of parsedOptions) { + const alreadyDefined = cmd.optionsRaw?.get?.(long); + if (!alreadyDefined) cmd.option(long, desc, short); + } + } catch (_err) {} +} + +// we setup the lazy option loading for a command +function setupLazyOptionLoading(cmd: any, command: string): void { + cmd._lazyCommand = command; + cmd._optionsLoaded = false; + + const optionsStore = cmd.options; + cmd.optionsRaw = optionsStore; + + Object.defineProperty(cmd, 'options', { + get() { + if (!this._optionsLoaded) { + this._optionsLoaded = true; + loadDynamicOptionsSync(this, this._lazyCommand); // block until filled + } + return optionsStore; + }, + configurable: true, + }); +} + +export async function setupPnpmCompletions( + completion: PackageManagerCompletion +): Promise { + try { + const commandsWithDescriptions = await getPnpmCommandsFromMainHelp(); + + for (const [command, description] of Object.entries( + commandsWithDescriptions + )) { + const cmd = completion.command(command, description); + + if (['remove', 'rm', 'update', 'up'].includes(command)) { + cmd.argument('package', packageJsonDependencyCompletion); + } + if (command === 'run') { + cmd.argument('script', packageJsonScriptCompletion, true); + } + + setupLazyOptionLoading(cmd, command); + } + } catch (_err) {} +} diff --git a/bin/handlers/yarn-handler.ts b/bin/handlers/yarn-handler.ts new file mode 100644 index 0000000..5827efe --- /dev/null +++ b/bin/handlers/yarn-handler.ts @@ -0,0 +1,5 @@ +import type { PackageManagerCompletion } from '../package-manager-completion.js'; + +export async function setupYarnCompletions( + completion: PackageManagerCompletion +): Promise {} diff --git a/bin/utils/package-json-utils.ts b/bin/utils/package-json-utils.ts new file mode 100644 index 0000000..094d8e1 --- /dev/null +++ b/bin/utils/package-json-utils.ts @@ -0,0 +1,25 @@ +import { readFileSync } from 'fs'; + +export function getPackageJsonScripts(): string[] { + try { + const packageJson = JSON.parse(readFileSync('package.json', 'utf8')); + return Object.keys(packageJson.scripts || {}); + } catch { + return []; + } +} + +export function getPackageJsonDependencies(): string[] { + try { + const packageJson = JSON.parse(readFileSync('package.json', 'utf8')); + const deps = { + ...packageJson.dependencies, + ...packageJson.devDependencies, + ...packageJson.peerDependencies, + ...packageJson.optionalDependencies, + }; + return Object.keys(deps); + } catch { + return []; + } +} diff --git a/bin/utils/text-utils.ts b/bin/utils/text-utils.ts new file mode 100644 index 0000000..6c4c929 --- /dev/null +++ b/bin/utils/text-utils.ts @@ -0,0 +1,35 @@ +// regex for parsing help text +export const ANSI_ESCAPE_RE = /\x1B(?:[@-Z\\-_]|\[[0-?]*[ -/]*[@-~])/g; + +// Command row: <>=2 spaces> +// e.g. " install, i Install all dependencies" +export const COMMAND_ROW_RE = /^\s+([a-z][a-z\s,-]*?)\s{2,}(\S.*)$/i; + +// Option row (optional value part captured in (?)): +// [indent][-x, ]--long[ | [value]] <>=2 spaces> +export const OPTION_ROW_RE = + /^\s*(?:-(?[A-Za-z]),\s*)?--(?[a-z0-9-]+)(?\s+(?:<[^>]+>|\[[^\]]+\]))?\s{2,}(?\S.*)$/i; + +// we detect the start of a new option head (used to stop continuation) +export const OPTION_HEAD_RE = /^\s*(?:-[A-Za-z],\s*)?--[a-z0-9-]+/i; + +// we remove the ANSI escape sequences from a string +export const stripAnsiEscapes = (s: string): string => + s.replace(ANSI_ESCAPE_RE, ''); + +// measure the indentation level of a string +export const measureIndent = (s: string): number => + (s.match(/^\s*/) || [''])[0].length; + +// parse a comma-separated list of aliases +export const parseAliasList = (s: string): string[] => + s + .split(',') + .map((t) => t.trim()) + .filter(Boolean); + +export type ParsedOption = { + long: string; + short?: string; + desc: string; +}; diff --git a/completion-debug.log b/completion-debug.log new file mode 100644 index 0000000..7314464 --- /dev/null +++ b/completion-debug.log @@ -0,0 +1,3524 @@ + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install -- +Truncated words[*]: pnpm install --, +lastParam: --, lastChar: - +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install -- +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install -- +Truncated words[*]: pnpm install --, +lastParam: --, lastChar: - +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install -- +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install -- +Truncated words[*]: pnpm install --, +lastParam: --, lastChar: - +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install -- +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm +Truncated words[*]: pnpm , +lastParam: , lastChar: +Adding extra empty parameter +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- '' '' +completion output: add Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency +import Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file +i Install all dependencies for a project +install Install all dependencies for a project +it Runs a pnpm install followed immediately by a pnpm test +install-test Runs a pnpm install followed immediately by a pnpm test +ln Connect the local project to another one +link Connect the local project to another one +prune Removes extraneous packages +rb Rebuild a package +rebuild Rebuild a package +rm Removes packages from node_modules and from the project's package.json +remove Removes packages from node_modules and from the project's package.json +unlink Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link +up Updates packages to their latest version based on the specified range +update Updates packages to their latest version based on the specified range +audit Checks for known security issues with the installed packages +licenses Check licenses in consumed packages +ls Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +list Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +outdated Check for outdated packages +exec Executes a shell command in scope of a project +run Runs a defined package script +start Runs an arbitrary command specified in the package's "start" property of its "scripts" object +t Runs a package's "test" script, if one was provided +test Runs a package's "test" script, if one was provided +cat-file Prints the contents of a file based on the hash value stored in the index file +cat-index Prints the index file of a specific package from the store +find-hash Experimental! Lists the packages that include the file with the specified hash. +pack Create a tarball from a package +publish Publishes a package to the registry +root Prints the effective modules directory +store Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store +:4 +last line: :4 +directive: 4 +completions: add Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency +import Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file +i Install all dependencies for a project +install Install all dependencies for a project +it Runs a pnpm install followed immediately by a pnpm test +install-test Runs a pnpm install followed immediately by a pnpm test +ln Connect the local project to another one +link Connect the local project to another one +prune Removes extraneous packages +rb Rebuild a package +rebuild Rebuild a package +rm Removes packages from node_modules and from the project's package.json +remove Removes packages from node_modules and from the project's package.json +unlink Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link +up Updates packages to their latest version based on the specified range +update Updates packages to their latest version based on the specified range +audit Checks for known security issues with the installed packages +licenses Check licenses in consumed packages +ls Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +list Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +outdated Check for outdated packages +exec Executes a shell command in scope of a project +run Runs a defined package script +start Runs an arbitrary command specified in the package's "start" property of its "scripts" object +t Runs a package's "test" script, if one was provided +test Runs a package's "test" script, if one was provided +cat-file Prints the contents of a file based on the hash value stored in the index file +cat-index Prints the index file of a specific package from the store +find-hash Experimental! Lists the packages that include the file with the specified hash. +pack Create a tarball from a package +publish Publishes a package to the registry +root Prints the effective modules directory +store Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store +flagPrefix: +Adding completion: add:Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency +Adding completion: import:Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file +Adding completion: i:Install all dependencies for a project +Adding completion: install:Install all dependencies for a project +Adding completion: it:Runs a pnpm install followed immediately by a pnpm test +Adding completion: install-test:Runs a pnpm install followed immediately by a pnpm test +Adding completion: ln:Connect the local project to another one +Adding completion: link:Connect the local project to another one +Adding completion: prune:Removes extraneous packages +Adding completion: rb:Rebuild a package +Adding completion: rebuild:Rebuild a package +Adding completion: rm:Removes packages from node_modules and from the project's package.json +Adding completion: remove:Removes packages from node_modules and from the project's package.json +Adding completion: unlink:Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link +Adding completion: up:Updates packages to their latest version based on the specified range +Adding completion: update:Updates packages to their latest version based on the specified range +Adding completion: audit:Checks for known security issues with the installed packages +Adding completion: licenses:Check licenses in consumed packages +Adding completion: ls:Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +Adding completion: list:Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +Adding completion: outdated:Check for outdated packages +Adding completion: exec:Executes a shell command in scope of a project +Adding completion: run:Runs a defined package script +Adding completion: start:Runs an arbitrary command specified in the package's "start" property of its "scripts" object +Adding completion: t:Runs a package's "test" script, if one was provided +Adding completion: test:Runs a package's "test" script, if one was provided +Adding completion: cat-file:Prints the contents of a file based on the hash value stored in the index file +Adding completion: cat-index:Prints the index file of a specific package from the store +Adding completion: find-hash:Experimental! Lists the packages that include the file with the specified hash. +Adding completion: pack:Create a tarball from a package +Adding completion: publish:Publishes a package to the registry +Adding completion: root:Prints the effective modules directory +Adding completion: store:Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store +Calling _describe +_describe found some completions + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm +Truncated words[*]: pnpm , +lastParam: , lastChar: +Adding extra empty parameter +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- '' '' +completion output: add Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency +import Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file +i Install all dependencies for a project +install Install all dependencies for a project +it Runs a pnpm install followed immediately by a pnpm test +install-test Runs a pnpm install followed immediately by a pnpm test +ln Connect the local project to another one +link Connect the local project to another one +prune Removes extraneous packages +rb Rebuild a package +rebuild Rebuild a package +rm Removes packages from node_modules and from the project's package.json +remove Removes packages from node_modules and from the project's package.json +unlink Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link +up Updates packages to their latest version based on the specified range +update Updates packages to their latest version based on the specified range +audit Checks for known security issues with the installed packages +licenses Check licenses in consumed packages +ls Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +list Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +outdated Check for outdated packages +exec Executes a shell command in scope of a project +run Runs a defined package script +start Runs an arbitrary command specified in the package's "start" property of its "scripts" object +t Runs a package's "test" script, if one was provided +test Runs a package's "test" script, if one was provided +cat-file Prints the contents of a file based on the hash value stored in the index file +cat-index Prints the index file of a specific package from the store +find-hash Experimental! Lists the packages that include the file with the specified hash. +pack Create a tarball from a package +publish Publishes a package to the registry +root Prints the effective modules directory +store Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store +:4 +last line: :4 +directive: 4 +completions: add Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency +import Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file +i Install all dependencies for a project +install Install all dependencies for a project +it Runs a pnpm install followed immediately by a pnpm test +install-test Runs a pnpm install followed immediately by a pnpm test +ln Connect the local project to another one +link Connect the local project to another one +prune Removes extraneous packages +rb Rebuild a package +rebuild Rebuild a package +rm Removes packages from node_modules and from the project's package.json +remove Removes packages from node_modules and from the project's package.json +unlink Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link +up Updates packages to their latest version based on the specified range +update Updates packages to their latest version based on the specified range +audit Checks for known security issues with the installed packages +licenses Check licenses in consumed packages +ls Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +list Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +outdated Check for outdated packages +exec Executes a shell command in scope of a project +run Runs a defined package script +start Runs an arbitrary command specified in the package's "start" property of its "scripts" object +t Runs a package's "test" script, if one was provided +test Runs a package's "test" script, if one was provided +cat-file Prints the contents of a file based on the hash value stored in the index file +cat-index Prints the index file of a specific package from the store +find-hash Experimental! Lists the packages that include the file with the specified hash. +pack Create a tarball from a package +publish Publishes a package to the registry +root Prints the effective modules directory +store Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store +flagPrefix: +Adding completion: add:Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency +Adding completion: import:Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file +Adding completion: i:Install all dependencies for a project +Adding completion: install:Install all dependencies for a project +Adding completion: it:Runs a pnpm install followed immediately by a pnpm test +Adding completion: install-test:Runs a pnpm install followed immediately by a pnpm test +Adding completion: ln:Connect the local project to another one +Adding completion: link:Connect the local project to another one +Adding completion: prune:Removes extraneous packages +Adding completion: rb:Rebuild a package +Adding completion: rebuild:Rebuild a package +Adding completion: rm:Removes packages from node_modules and from the project's package.json +Adding completion: remove:Removes packages from node_modules and from the project's package.json +Adding completion: unlink:Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link +Adding completion: up:Updates packages to their latest version based on the specified range +Adding completion: update:Updates packages to their latest version based on the specified range +Adding completion: audit:Checks for known security issues with the installed packages +Adding completion: licenses:Check licenses in consumed packages +Adding completion: ls:Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +Adding completion: list:Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +Adding completion: outdated:Check for outdated packages +Adding completion: exec:Executes a shell command in scope of a project +Adding completion: run:Runs a defined package script +Adding completion: start:Runs an arbitrary command specified in the package's "start" property of its "scripts" object +Adding completion: t:Runs a package's "test" script, if one was provided +Adding completion: test:Runs a package's "test" script, if one was provided +Adding completion: cat-file:Prints the contents of a file based on the hash value stored in the index file +Adding completion: cat-index:Prints the index file of a specific package from the store +Adding completion: find-hash:Experimental! Lists the packages that include the file with the specified hash. +Adding completion: pack:Create a tarball from a package +Adding completion: publish:Publishes a package to the registry +Adding completion: root:Prints the effective modules directory +Adding completion: store:Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store +Calling _describe +_describe found some completions + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install -- +Truncated words[*]: pnpm install --, +lastParam: --, lastChar: - +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install -- +completion output: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules +--dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) +--fix-lockfile Fix broken lockfile entries automatically +--force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) +--global-dir Specify a custom directory to store global packages +--help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules +--ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs +--ignore-scripts Don't run lifecycle scripts +--ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. +--lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. +--merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests +--no-hoist Dependencies inside the modules directory will have access only to their listed dependencies +--no-lockfile Don't read or generate a `pnpm-lock.yaml` file +--no-optional `optionalDependencies` are not installed +--offline Trigger an error if any required dependencies are not available in local store +--optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store +--prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation +--prefer-offline Skip staleness checks for cached data, but request missing data from the server +--prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory +--recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" +--resolution-only Re-runs resolution: useful for printing out peer dependency issues +--shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them +--side-effects-cache Use or cache the results of (pre/post)install hooks +--side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk +--stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. +--strict-peer-dependencies Fail on missing or invalid peer dependencies +--use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail +--use-stderr Divert all output to stderr +--use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory +--workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build +--fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm +:4 +last line: :4 +directive: 4 +completions: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules +--dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) +--fix-lockfile Fix broken lockfile entries automatically +--force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) +--global-dir Specify a custom directory to store global packages +--help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules +--ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs +--ignore-scripts Don't run lifecycle scripts +--ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. +--lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. +--merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests +--no-hoist Dependencies inside the modules directory will have access only to their listed dependencies +--no-lockfile Don't read or generate a `pnpm-lock.yaml` file +--no-optional `optionalDependencies` are not installed +--offline Trigger an error if any required dependencies are not available in local store +--optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store +--prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation +--prefer-offline Skip staleness checks for cached data, but request missing data from the server +--prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory +--recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" +--resolution-only Re-runs resolution: useful for printing out peer dependency issues +--shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them +--side-effects-cache Use or cache the results of (pre/post)install hooks +--side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk +--stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. +--strict-peer-dependencies Fail on missing or invalid peer dependencies +--use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail +--use-stderr Divert all output to stderr +--use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory +--workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build +--fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm +flagPrefix: +Adding completion: --aggregate-output:Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules +Adding completion: --dev:Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) +Adding completion: --fix-lockfile:Fix broken lockfile entries automatically +Adding completion: --force:Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) +Adding completion: --global-dir:Specify a custom directory to store global packages +Adding completion: --help:Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules +Adding completion: --ignore-pnpmfile:Disable pnpm hooks defined in .pnpmfile.cjs +Adding completion: --ignore-scripts:Don't run lifecycle scripts +Adding completion: --ignore-workspace:Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. +Adding completion: --lockfile-only:Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. +Adding completion: --merge-git-branch-lockfiles:Merge lockfiles were generated on git branch be installed (instead of node_modules) requests +Adding completion: --no-hoist:Dependencies inside the modules directory will have access only to their listed dependencies +Adding completion: --no-lockfile:Don't read or generate a `pnpm-lock.yaml` file +Adding completion: --no-optional:`optionalDependencies` are not installed +Adding completion: --offline:Trigger an error if any required dependencies are not available in local store +Adding completion: --optimistic-repeat-install:Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store +Adding completion: --prefer-frozen-lockfile:If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation +Adding completion: --prefer-offline:Skip staleness checks for cached data, but request missing data from the server +Adding completion: --prod:Packages in `devDependencies` won't be installed pattern to the root of the modules directory +Adding completion: --recursive:Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" +Adding completion: --resolution-only:Re-runs resolution: useful for printing out peer dependency issues +Adding completion: --shamefully-hoist:All the subdeps will be hoisted into the root node_modules. Your code will have access to them +Adding completion: --side-effects-cache:Use or cache the results of (pre/post)install hooks +Adding completion: --side-effects-cache-readonly:Only use the side effects cache if present, do not create it for new packages are saved on the disk +Adding completion: --stream:Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. +Adding completion: --strict-peer-dependencies:Fail on missing or invalid peer dependencies +Adding completion: --use-running-store-server:Only allows installation with a store server. If no store server is running, installation will fail +Adding completion: --use-stderr:Divert all output to stderr +Adding completion: --use-store-server:Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory +Adding completion: --workspace-root:Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build +Adding completion: --fail-if-no-match:If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm +Calling _describe +_describe found some completions + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install -- +Truncated words[*]: pnpm install --, +lastParam: --, lastChar: - +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install -- +completion output: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules +--dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) +--fix-lockfile Fix broken lockfile entries automatically +--force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) +--global-dir Specify a custom directory to store global packages +--help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules +--ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs +--ignore-scripts Don't run lifecycle scripts +--ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. +--lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. +--merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests +--no-hoist Dependencies inside the modules directory will have access only to their listed dependencies +--no-lockfile Don't read or generate a `pnpm-lock.yaml` file +--no-optional `optionalDependencies` are not installed +--offline Trigger an error if any required dependencies are not available in local store +--optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store +--prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation +--prefer-offline Skip staleness checks for cached data, but request missing data from the server +--prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory +--recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" +--resolution-only Re-runs resolution: useful for printing out peer dependency issues +--shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them +--side-effects-cache Use or cache the results of (pre/post)install hooks +--side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk +--stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. +--strict-peer-dependencies Fail on missing or invalid peer dependencies +--use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail +--use-stderr Divert all output to stderr +--use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory +--workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build +--fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm +:4 +last line: :4 +directive: 4 +completions: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules +--dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) +--fix-lockfile Fix broken lockfile entries automatically +--force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) +--global-dir Specify a custom directory to store global packages +--help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules +--ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs +--ignore-scripts Don't run lifecycle scripts +--ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. +--lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. +--merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests +--no-hoist Dependencies inside the modules directory will have access only to their listed dependencies +--no-lockfile Don't read or generate a `pnpm-lock.yaml` file +--no-optional `optionalDependencies` are not installed +--offline Trigger an error if any required dependencies are not available in local store +--optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store +--prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation +--prefer-offline Skip staleness checks for cached data, but request missing data from the server +--prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory +--recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" +--resolution-only Re-runs resolution: useful for printing out peer dependency issues +--shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them +--side-effects-cache Use or cache the results of (pre/post)install hooks +--side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk +--stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. +--strict-peer-dependencies Fail on missing or invalid peer dependencies +--use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail +--use-stderr Divert all output to stderr +--use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory +--workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build +--fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm +flagPrefix: +Adding completion: --aggregate-output:Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules +Adding completion: --dev:Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) +Adding completion: --fix-lockfile:Fix broken lockfile entries automatically +Adding completion: --force:Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) +Adding completion: --global-dir:Specify a custom directory to store global packages +Adding completion: --help:Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules +Adding completion: --ignore-pnpmfile:Disable pnpm hooks defined in .pnpmfile.cjs +Adding completion: --ignore-scripts:Don't run lifecycle scripts +Adding completion: --ignore-workspace:Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. +Adding completion: --lockfile-only:Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. +Adding completion: --merge-git-branch-lockfiles:Merge lockfiles were generated on git branch be installed (instead of node_modules) requests +Adding completion: --no-hoist:Dependencies inside the modules directory will have access only to their listed dependencies +Adding completion: --no-lockfile:Don't read or generate a `pnpm-lock.yaml` file +Adding completion: --no-optional:`optionalDependencies` are not installed +Adding completion: --offline:Trigger an error if any required dependencies are not available in local store +Adding completion: --optimistic-repeat-install:Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store +Adding completion: --prefer-frozen-lockfile:If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation +Adding completion: --prefer-offline:Skip staleness checks for cached data, but request missing data from the server +Adding completion: --prod:Packages in `devDependencies` won't be installed pattern to the root of the modules directory +Adding completion: --recursive:Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" +Adding completion: --resolution-only:Re-runs resolution: useful for printing out peer dependency issues +Adding completion: --shamefully-hoist:All the subdeps will be hoisted into the root node_modules. Your code will have access to them +Adding completion: --side-effects-cache:Use or cache the results of (pre/post)install hooks +Adding completion: --side-effects-cache-readonly:Only use the side effects cache if present, do not create it for new packages are saved on the disk +Adding completion: --stream:Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. +Adding completion: --strict-peer-dependencies:Fail on missing or invalid peer dependencies +Adding completion: --use-running-store-server:Only allows installation with a store server. If no store server is running, installation will fail +Adding completion: --use-stderr:Divert all output to stderr +Adding completion: --use-store-server:Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory +Adding completion: --workspace-root:Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build +Adding completion: --fail-if-no-match:If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm +Calling _describe +_describe found some completions + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install --d +Truncated words[*]: pnpm install --d, +lastParam: --d, lastChar: d +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --d +completion output: --dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) +:4 +last line: :4 +directive: 4 +completions: --dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) +flagPrefix: +Adding completion: --dev:Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) +Calling _describe +_describe found some completions + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install -- +Truncated words[*]: pnpm install --, +lastParam: --, lastChar: - +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install -- +completion output: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules +--dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) +--fix-lockfile Fix broken lockfile entries automatically +--force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) +--global-dir Specify a custom directory to store global packages +--help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules +--ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs +--ignore-scripts Don't run lifecycle scripts +--ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. +--lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. +--merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests +--no-hoist Dependencies inside the modules directory will have access only to their listed dependencies +--no-lockfile Don't read or generate a `pnpm-lock.yaml` file +--no-optional `optionalDependencies` are not installed +--offline Trigger an error if any required dependencies are not available in local store +--optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store +--prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation +--prefer-offline Skip staleness checks for cached data, but request missing data from the server +--prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory +--recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" +--resolution-only Re-runs resolution: useful for printing out peer dependency issues +--shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them +--side-effects-cache Use or cache the results of (pre/post)install hooks +--side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk +--stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. +--strict-peer-dependencies Fail on missing or invalid peer dependencies +--use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail +--use-stderr Divert all output to stderr +--use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory +--workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build +--fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm +:4 +last line: :4 +directive: 4 +completions: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules +--dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) +--fix-lockfile Fix broken lockfile entries automatically +--force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) +--global-dir Specify a custom directory to store global packages +--help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules +--ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs +--ignore-scripts Don't run lifecycle scripts +--ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. +--lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. +--merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests +--no-hoist Dependencies inside the modules directory will have access only to their listed dependencies +--no-lockfile Don't read or generate a `pnpm-lock.yaml` file +--no-optional `optionalDependencies` are not installed +--offline Trigger an error if any required dependencies are not available in local store +--optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store +--prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation +--prefer-offline Skip staleness checks for cached data, but request missing data from the server +--prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory +--recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" +--resolution-only Re-runs resolution: useful for printing out peer dependency issues +--shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them +--side-effects-cache Use or cache the results of (pre/post)install hooks +--side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk +--stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. +--strict-peer-dependencies Fail on missing or invalid peer dependencies +--use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail +--use-stderr Divert all output to stderr +--use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory +--workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build +--fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm +flagPrefix: +Adding completion: --aggregate-output:Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules +Adding completion: --dev:Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) +Adding completion: --fix-lockfile:Fix broken lockfile entries automatically +Adding completion: --force:Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) +Adding completion: --global-dir:Specify a custom directory to store global packages +Adding completion: --help:Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules +Adding completion: --ignore-pnpmfile:Disable pnpm hooks defined in .pnpmfile.cjs +Adding completion: --ignore-scripts:Don't run lifecycle scripts +Adding completion: --ignore-workspace:Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. +Adding completion: --lockfile-only:Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. +Adding completion: --merge-git-branch-lockfiles:Merge lockfiles were generated on git branch be installed (instead of node_modules) requests +Adding completion: --no-hoist:Dependencies inside the modules directory will have access only to their listed dependencies +Adding completion: --no-lockfile:Don't read or generate a `pnpm-lock.yaml` file +Adding completion: --no-optional:`optionalDependencies` are not installed +Adding completion: --offline:Trigger an error if any required dependencies are not available in local store +Adding completion: --optimistic-repeat-install:Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store +Adding completion: --prefer-frozen-lockfile:If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation +Adding completion: --prefer-offline:Skip staleness checks for cached data, but request missing data from the server +Adding completion: --prod:Packages in `devDependencies` won't be installed pattern to the root of the modules directory +Adding completion: --recursive:Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" +Adding completion: --resolution-only:Re-runs resolution: useful for printing out peer dependency issues +Adding completion: --shamefully-hoist:All the subdeps will be hoisted into the root node_modules. Your code will have access to them +Adding completion: --side-effects-cache:Use or cache the results of (pre/post)install hooks +Adding completion: --side-effects-cache-readonly:Only use the side effects cache if present, do not create it for new packages are saved on the disk +Adding completion: --stream:Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. +Adding completion: --strict-peer-dependencies:Fail on missing or invalid peer dependencies +Adding completion: --use-running-store-server:Only allows installation with a store server. If no store server is running, installation will fail +Adding completion: --use-stderr:Divert all output to stderr +Adding completion: --use-store-server:Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory +Adding completion: --workspace-root:Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build +Adding completion: --fail-if-no-match:If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm +Calling _describe +_describe found some completions + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install -- +Truncated words[*]: pnpm install --, +lastParam: --, lastChar: - +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install -- +completion output: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules +--dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) +--fix-lockfile Fix broken lockfile entries automatically +--force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) +--global-dir Specify a custom directory to store global packages +--help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules +--ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs +--ignore-scripts Don't run lifecycle scripts +--ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. +--lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. +--merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests +--no-hoist Dependencies inside the modules directory will have access only to their listed dependencies +--no-lockfile Don't read or generate a `pnpm-lock.yaml` file +--no-optional `optionalDependencies` are not installed +--offline Trigger an error if any required dependencies are not available in local store +--optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store +--prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation +--prefer-offline Skip staleness checks for cached data, but request missing data from the server +--prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory +--recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" +--resolution-only Re-runs resolution: useful for printing out peer dependency issues +--shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them +--side-effects-cache Use or cache the results of (pre/post)install hooks +--side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk +--stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. +--strict-peer-dependencies Fail on missing or invalid peer dependencies +--use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail +--use-stderr Divert all output to stderr +--use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory +--workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build +--fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm +:4 +last line: :4 +directive: 4 +completions: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules +--dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) +--fix-lockfile Fix broken lockfile entries automatically +--force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) +--global-dir Specify a custom directory to store global packages +--help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules +--ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs +--ignore-scripts Don't run lifecycle scripts +--ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. +--lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. +--merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests +--no-hoist Dependencies inside the modules directory will have access only to their listed dependencies +--no-lockfile Don't read or generate a `pnpm-lock.yaml` file +--no-optional `optionalDependencies` are not installed +--offline Trigger an error if any required dependencies are not available in local store +--optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store +--prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation +--prefer-offline Skip staleness checks for cached data, but request missing data from the server +--prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory +--recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" +--resolution-only Re-runs resolution: useful for printing out peer dependency issues +--shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them +--side-effects-cache Use or cache the results of (pre/post)install hooks +--side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk +--stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. +--strict-peer-dependencies Fail on missing or invalid peer dependencies +--use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail +--use-stderr Divert all output to stderr +--use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory +--workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build +--fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm +flagPrefix: +Adding completion: --aggregate-output:Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules +Adding completion: --dev:Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) +Adding completion: --fix-lockfile:Fix broken lockfile entries automatically +Adding completion: --force:Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) +Adding completion: --global-dir:Specify a custom directory to store global packages +Adding completion: --help:Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules +Adding completion: --ignore-pnpmfile:Disable pnpm hooks defined in .pnpmfile.cjs +Adding completion: --ignore-scripts:Don't run lifecycle scripts +Adding completion: --ignore-workspace:Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. +Adding completion: --lockfile-only:Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. +Adding completion: --merge-git-branch-lockfiles:Merge lockfiles were generated on git branch be installed (instead of node_modules) requests +Adding completion: --no-hoist:Dependencies inside the modules directory will have access only to their listed dependencies +Adding completion: --no-lockfile:Don't read or generate a `pnpm-lock.yaml` file +Adding completion: --no-optional:`optionalDependencies` are not installed +Adding completion: --offline:Trigger an error if any required dependencies are not available in local store +Adding completion: --optimistic-repeat-install:Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store +Adding completion: --prefer-frozen-lockfile:If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation +Adding completion: --prefer-offline:Skip staleness checks for cached data, but request missing data from the server +Adding completion: --prod:Packages in `devDependencies` won't be installed pattern to the root of the modules directory +Adding completion: --recursive:Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" +Adding completion: --resolution-only:Re-runs resolution: useful for printing out peer dependency issues +Adding completion: --shamefully-hoist:All the subdeps will be hoisted into the root node_modules. Your code will have access to them +Adding completion: --side-effects-cache:Use or cache the results of (pre/post)install hooks +Adding completion: --side-effects-cache-readonly:Only use the side effects cache if present, do not create it for new packages are saved on the disk +Adding completion: --stream:Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. +Adding completion: --strict-peer-dependencies:Fail on missing or invalid peer dependencies +Adding completion: --use-running-store-server:Only allows installation with a store server. If no store server is running, installation will fail +Adding completion: --use-stderr:Divert all output to stderr +Adding completion: --use-store-server:Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory +Adding completion: --workspace-root:Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build +Adding completion: --fail-if-no-match:If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm +Calling _describe +_describe found some completions + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm +Truncated words[*]: pnpm , +lastParam: , lastChar: +Adding extra empty parameter +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- '' '' +completion output: add Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency +import Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file +i Install all dependencies for a project +install Install all dependencies for a project +it Runs a pnpm install followed immediately by a pnpm test +install-test Runs a pnpm install followed immediately by a pnpm test +ln Connect the local project to another one +link Connect the local project to another one +prune Removes extraneous packages +rb Rebuild a package +rebuild Rebuild a package +rm Removes packages from node_modules and from the project's package.json +remove Removes packages from node_modules and from the project's package.json +unlink Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link +up Updates packages to their latest version based on the specified range +update Updates packages to their latest version based on the specified range +audit Checks for known security issues with the installed packages +licenses Check licenses in consumed packages +ls Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +list Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +outdated Check for outdated packages +exec Executes a shell command in scope of a project +run Runs a defined package script +start Runs an arbitrary command specified in the package's "start" property of its "scripts" object +t Runs a package's "test" script, if one was provided +test Runs a package's "test" script, if one was provided +cat-file Prints the contents of a file based on the hash value stored in the index file +cat-index Prints the index file of a specific package from the store +find-hash Experimental! Lists the packages that include the file with the specified hash. +pack Create a tarball from a package +publish Publishes a package to the registry +root Prints the effective modules directory +store Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store +:4 +last line: :4 +directive: 4 +completions: add Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency +import Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file +i Install all dependencies for a project +install Install all dependencies for a project +it Runs a pnpm install followed immediately by a pnpm test +install-test Runs a pnpm install followed immediately by a pnpm test +ln Connect the local project to another one +link Connect the local project to another one +prune Removes extraneous packages +rb Rebuild a package +rebuild Rebuild a package +rm Removes packages from node_modules and from the project's package.json +remove Removes packages from node_modules and from the project's package.json +unlink Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link +up Updates packages to their latest version based on the specified range +update Updates packages to their latest version based on the specified range +audit Checks for known security issues with the installed packages +licenses Check licenses in consumed packages +ls Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +list Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +outdated Check for outdated packages +exec Executes a shell command in scope of a project +run Runs a defined package script +start Runs an arbitrary command specified in the package's "start" property of its "scripts" object +t Runs a package's "test" script, if one was provided +test Runs a package's "test" script, if one was provided +cat-file Prints the contents of a file based on the hash value stored in the index file +cat-index Prints the index file of a specific package from the store +find-hash Experimental! Lists the packages that include the file with the specified hash. +pack Create a tarball from a package +publish Publishes a package to the registry +root Prints the effective modules directory +store Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store +flagPrefix: +Adding completion: add:Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency +Adding completion: import:Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file +Adding completion: i:Install all dependencies for a project +Adding completion: install:Install all dependencies for a project +Adding completion: it:Runs a pnpm install followed immediately by a pnpm test +Adding completion: install-test:Runs a pnpm install followed immediately by a pnpm test +Adding completion: ln:Connect the local project to another one +Adding completion: link:Connect the local project to another one +Adding completion: prune:Removes extraneous packages +Adding completion: rb:Rebuild a package +Adding completion: rebuild:Rebuild a package +Adding completion: rm:Removes packages from node_modules and from the project's package.json +Adding completion: remove:Removes packages from node_modules and from the project's package.json +Adding completion: unlink:Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link +Adding completion: up:Updates packages to their latest version based on the specified range +Adding completion: update:Updates packages to their latest version based on the specified range +Adding completion: audit:Checks for known security issues with the installed packages +Adding completion: licenses:Check licenses in consumed packages +Adding completion: ls:Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +Adding completion: list:Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +Adding completion: outdated:Check for outdated packages +Adding completion: exec:Executes a shell command in scope of a project +Adding completion: run:Runs a defined package script +Adding completion: start:Runs an arbitrary command specified in the package's "start" property of its "scripts" object +Adding completion: t:Runs a package's "test" script, if one was provided +Adding completion: test:Runs a package's "test" script, if one was provided +Adding completion: cat-file:Prints the contents of a file based on the hash value stored in the index file +Adding completion: cat-index:Prints the index file of a specific package from the store +Adding completion: find-hash:Experimental! Lists the packages that include the file with the specified hash. +Adding completion: pack:Create a tarball from a package +Adding completion: publish:Publishes a package to the registry +Adding completion: root:Prints the effective modules directory +Adding completion: store:Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store +Calling _describe +_describe found some completions + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm in +Truncated words[*]: pnpm in, +lastParam: in, lastChar: n +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- in +completion output: install Install all dependencies for a project +install-test Runs a pnpm install followed immediately by a pnpm test +:4 +last line: :4 +directive: 4 +completions: install Install all dependencies for a project +install-test Runs a pnpm install followed immediately by a pnpm test +flagPrefix: +Adding completion: install:Install all dependencies for a project +Adding completion: install-test:Runs a pnpm install followed immediately by a pnpm test +Calling _describe +_describe found some completions + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm install-- +Truncated words[*]: pnpm install--, +lastParam: install--, lastChar: - +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install-- +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm install-- +Truncated words[*]: pnpm install--, +lastParam: install--, lastChar: - +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install-- +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm install-- +Truncated words[*]: pnpm install--, +lastParam: install--, lastChar: - +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install-- +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm install--d +Truncated words[*]: pnpm install--d, +lastParam: install--d, lastChar: d +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install--d +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm install--d +Truncated words[*]: pnpm install--d, +lastParam: install--d, lastChar: d +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install--d +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm install--d +Truncated words[*]: pnpm install--d, +lastParam: install--d, lastChar: d +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install--d +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install --d +Truncated words[*]: pnpm install --d, +lastParam: --d, lastChar: d +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --d +completion output: --dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) +:4 +last line: :4 +directive: 4 +completions: --dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) +flagPrefix: +Adding completion: --dev:Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) +Calling _describe +_describe found some completions + +========= starting completion logic ========== +CURRENT: 4, words[*]: pnpm install --dev +Truncated words[*]: pnpm install --dev , +lastParam: , lastChar: +Adding extra empty parameter +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 4, words[*]: pnpm install --dev +Truncated words[*]: pnpm install --dev , +lastParam: , lastChar: +Adding extra empty parameter +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 4, words[*]: pnpm install --dev +Truncated words[*]: pnpm install --dev , +lastParam: , lastChar: +Adding extra empty parameter +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 4, words[*]: pnpm install --dev +Truncated words[*]: pnpm install --dev , +lastParam: , lastChar: +Adding extra empty parameter +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 4, words[*]: pnpm install --dev +Truncated words[*]: pnpm install --dev , +lastParam: , lastChar: +Adding extra empty parameter +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 4, words[*]: pnpm install --dev +Truncated words[*]: pnpm install --dev , +lastParam: , lastChar: +Adding extra empty parameter +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 4, words[*]: pnpm install --dev +Truncated words[*]: pnpm install --dev , +lastParam: , lastChar: +Adding extra empty parameter +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 4, words[*]: pnpm install --dev +Truncated words[*]: pnpm install --dev , +lastParam: , lastChar: +Adding extra empty parameter +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 4, words[*]: pnpm install --dev +Truncated words[*]: pnpm install --dev , +lastParam: , lastChar: +Adding extra empty parameter +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 4, words[*]: pnpm install --dev +Truncated words[*]: pnpm install --dev , +lastParam: , lastChar: +Adding extra empty parameter +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 4, words[*]: pnpm install --dev +Truncated words[*]: pnpm install --dev , +lastParam: , lastChar: +Adding extra empty parameter +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 4, words[*]: pnpm install --dev +Truncated words[*]: pnpm install --dev , +lastParam: , lastChar: +Adding extra empty parameter +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 4, words[*]: pnpm install --dev +Truncated words[*]: pnpm install --dev , +lastParam: , lastChar: +Adding extra empty parameter +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 4, words[*]: pnpm install --dev +Truncated words[*]: pnpm install --dev , +lastParam: , lastChar: +Adding extra empty parameter +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 4, words[*]: pnpm install --dev +Truncated words[*]: pnpm install --dev , +lastParam: , lastChar: +Adding extra empty parameter +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 4, words[*]: pnpm install --dev +Truncated words[*]: pnpm install --dev , +lastParam: , lastChar: +Adding extra empty parameter +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 4, words[*]: pnpm install --dev +Truncated words[*]: pnpm install --dev , +lastParam: , lastChar: +Adding extra empty parameter +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 4, words[*]: pnpm install --dev +Truncated words[*]: pnpm install --dev , +lastParam: , lastChar: +Adding extra empty parameter +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 4, words[*]: pnpm install --dev +Truncated words[*]: pnpm install --dev , +lastParam: , lastChar: +Adding extra empty parameter +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 4, words[*]: pnpm install --dev +Truncated words[*]: pnpm install --dev , +lastParam: , lastChar: +Adding extra empty parameter +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 4, words[*]: pnpm install --dev +Truncated words[*]: pnpm install --dev , +lastParam: , lastChar: +Adding extra empty parameter +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 4, words[*]: pnpm install --dev +Truncated words[*]: pnpm install --dev , +lastParam: , lastChar: +Adding extra empty parameter +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 4, words[*]: pnpm install --dev +Truncated words[*]: pnpm install --dev , +lastParam: , lastChar: +Adding extra empty parameter +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 4, words[*]: pnpm install --dev +Truncated words[*]: pnpm install --dev , +lastParam: , lastChar: +Adding extra empty parameter +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm ins +Truncated words[*]: pnpm ins, +lastParam: ins, lastChar: s +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- ins +completion output: install Install all dependencies for a project +install-test Runs a pnpm install followed immediately by a pnpm test +:4 +last line: :4 +directive: 4 +completions: install Install all dependencies for a project +install-test Runs a pnpm install followed immediately by a pnpm test +flagPrefix: +Adding completion: install:Install all dependencies for a project +Adding completion: install-test:Runs a pnpm install followed immediately by a pnpm test +Calling _describe +_describe found some completions + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm install +Truncated words[*]: pnpm install, +lastParam: install, lastChar: l +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install +completion output: install Install all dependencies for a project +install-test Runs a pnpm install followed immediately by a pnpm test +:4 +last line: :4 +directive: 4 +completions: install Install all dependencies for a project +install-test Runs a pnpm install followed immediately by a pnpm test +flagPrefix: +Adding completion: install:Install all dependencies for a project +Adding completion: install-test:Runs a pnpm install followed immediately by a pnpm test +Calling _describe +_describe found some completions + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm install +Truncated words[*]: pnpm install, +lastParam: install, lastChar: l +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install +completion output: install Install all dependencies for a project +install-test Runs a pnpm install followed immediately by a pnpm test +:4 +last line: :4 +directive: 4 +completions: install Install all dependencies for a project +install-test Runs a pnpm install followed immediately by a pnpm test +flagPrefix: +Adding completion: install:Install all dependencies for a project +Adding completion: install-test:Runs a pnpm install followed immediately by a pnpm test +Calling _describe +_describe found some completions + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install --f +Truncated words[*]: pnpm install --f, +lastParam: --f, lastChar: f +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --f +completion output: --fix-lockfile Fix broken lockfile entries automatically +--force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) +--fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm +:4 +last line: :4 +directive: 4 +completions: --fix-lockfile Fix broken lockfile entries automatically +--force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) +--fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm +flagPrefix: +Adding completion: --fix-lockfile:Fix broken lockfile entries automatically +Adding completion: --force:Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) +Adding completion: --fail-if-no-match:If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm +Calling _describe +_describe found some completions + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install --f +Truncated words[*]: pnpm install --f, +lastParam: --f, lastChar: f +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --f +completion output: --fix-lockfile Fix broken lockfile entries automatically +--force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) +--fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm +:4 +last line: :4 +directive: 4 +completions: --fix-lockfile Fix broken lockfile entries automatically +--force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) +--fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm +flagPrefix: +Adding completion: --fix-lockfile:Fix broken lockfile entries automatically +Adding completion: --force:Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) +Adding completion: --fail-if-no-match:If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm +Calling _describe +_describe found some completions + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install --ff +Truncated words[*]: pnpm install --ff, +lastParam: --ff, lastChar: f +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --ff +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install --ff +Truncated words[*]: pnpm install --ff, +lastParam: --ff, lastChar: f +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --ff +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install --ff +Truncated words[*]: pnpm install --ff, +lastParam: --ff, lastChar: f +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --ff +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install --ff +Truncated words[*]: pnpm install --ff, +lastParam: --ff, lastChar: f +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --ff +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install --ff +Truncated words[*]: pnpm install --ff, +lastParam: --ff, lastChar: f +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --ff +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install --ff +Truncated words[*]: pnpm install --ff, +lastParam: --ff, lastChar: f +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --ff +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install --ff +Truncated words[*]: pnpm install --ff, +lastParam: --ff, lastChar: f +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --ff +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install --ff +Truncated words[*]: pnpm install --ff, +lastParam: --ff, lastChar: f +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --ff +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install --ff +Truncated words[*]: pnpm install --ff, +lastParam: --ff, lastChar: f +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --ff +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install --ff +Truncated words[*]: pnpm install --ff, +lastParam: --ff, lastChar: f +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --ff +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install --ff +Truncated words[*]: pnpm install --ff, +lastParam: --ff, lastChar: f +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --ff +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install --ff +Truncated words[*]: pnpm install --ff, +lastParam: --ff, lastChar: f +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --ff +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install --ff +Truncated words[*]: pnpm install --ff, +lastParam: --ff, lastChar: f +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --ff +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install --ff +Truncated words[*]: pnpm install --ff, +lastParam: --ff, lastChar: f +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --ff +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install --ff +Truncated words[*]: pnpm install --ff, +lastParam: --ff, lastChar: f +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --ff +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm iii +Truncated words[*]: pnpm iii, +lastParam: iii, lastChar: i +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- iii +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm iii +Truncated words[*]: pnpm iii, +lastParam: iii, lastChar: i +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- iii +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm iii +Truncated words[*]: pnpm iii, +lastParam: iii, lastChar: i +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- iii +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm iii +Truncated words[*]: pnpm iii, +lastParam: iii, lastChar: i +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- iii +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm iii +Truncated words[*]: pnpm iii, +lastParam: iii, lastChar: i +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- iii +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm iii +Truncated words[*]: pnpm iii, +lastParam: iii, lastChar: i +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- iii +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm iii +Truncated words[*]: pnpm iii, +lastParam: iii, lastChar: i +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- iii +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm iii +Truncated words[*]: pnpm iii, +lastParam: iii, lastChar: i +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- iii +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm iii +Truncated words[*]: pnpm iii, +lastParam: iii, lastChar: i +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- iii +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm iii +Truncated words[*]: pnpm iii, +lastParam: iii, lastChar: i +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- iii +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm iii +Truncated words[*]: pnpm iii, +lastParam: iii, lastChar: i +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- iii +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm iii +Truncated words[*]: pnpm iii, +lastParam: iii, lastChar: i +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- iii +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm iii +Truncated words[*]: pnpm iii, +lastParam: iii, lastChar: i +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- iii +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm iii +Truncated words[*]: pnpm iii, +lastParam: iii, lastChar: i +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- iii +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm iii +Truncated words[*]: pnpm iii, +lastParam: iii, lastChar: i +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- iii +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm iii +Truncated words[*]: pnpm iii, +lastParam: iii, lastChar: i +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- iii +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm iii +Truncated words[*]: pnpm iii, +lastParam: iii, lastChar: i +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- iii +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm iii +Truncated words[*]: pnpm iii, +lastParam: iii, lastChar: i +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- iii +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm +Truncated words[*]: pnpm , +lastParam: , lastChar: +Adding extra empty parameter +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- '' '' +completion output: add Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency +import Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file +i Install all dependencies for a project +install Install all dependencies for a project +it Runs a pnpm install followed immediately by a pnpm test +install-test Runs a pnpm install followed immediately by a pnpm test +ln Connect the local project to another one +link Connect the local project to another one +prune Removes extraneous packages +rb Rebuild a package +rebuild Rebuild a package +rm Removes packages from node_modules and from the project's package.json +remove Removes packages from node_modules and from the project's package.json +unlink Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link +up Updates packages to their latest version based on the specified range +update Updates packages to their latest version based on the specified range +audit Checks for known security issues with the installed packages +licenses Check licenses in consumed packages +ls Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +list Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +outdated Check for outdated packages +exec Executes a shell command in scope of a project +run Runs a defined package script +start Runs an arbitrary command specified in the package's "start" property of its "scripts" object +t Runs a package's "test" script, if one was provided +test Runs a package's "test" script, if one was provided +cat-file Prints the contents of a file based on the hash value stored in the index file +cat-index Prints the index file of a specific package from the store +find-hash Experimental! Lists the packages that include the file with the specified hash. +pack Create a tarball from a package +publish Publishes a package to the registry +root Prints the effective modules directory +store Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store +:4 +last line: :4 +directive: 4 +completions: add Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency +import Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file +i Install all dependencies for a project +install Install all dependencies for a project +it Runs a pnpm install followed immediately by a pnpm test +install-test Runs a pnpm install followed immediately by a pnpm test +ln Connect the local project to another one +link Connect the local project to another one +prune Removes extraneous packages +rb Rebuild a package +rebuild Rebuild a package +rm Removes packages from node_modules and from the project's package.json +remove Removes packages from node_modules and from the project's package.json +unlink Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link +up Updates packages to their latest version based on the specified range +update Updates packages to their latest version based on the specified range +audit Checks for known security issues with the installed packages +licenses Check licenses in consumed packages +ls Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +list Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +outdated Check for outdated packages +exec Executes a shell command in scope of a project +run Runs a defined package script +start Runs an arbitrary command specified in the package's "start" property of its "scripts" object +t Runs a package's "test" script, if one was provided +test Runs a package's "test" script, if one was provided +cat-file Prints the contents of a file based on the hash value stored in the index file +cat-index Prints the index file of a specific package from the store +find-hash Experimental! Lists the packages that include the file with the specified hash. +pack Create a tarball from a package +publish Publishes a package to the registry +root Prints the effective modules directory +store Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store +flagPrefix: +Adding completion: add:Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency +Adding completion: import:Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file +Adding completion: i:Install all dependencies for a project +Adding completion: install:Install all dependencies for a project +Adding completion: it:Runs a pnpm install followed immediately by a pnpm test +Adding completion: install-test:Runs a pnpm install followed immediately by a pnpm test +Adding completion: ln:Connect the local project to another one +Adding completion: link:Connect the local project to another one +Adding completion: prune:Removes extraneous packages +Adding completion: rb:Rebuild a package +Adding completion: rebuild:Rebuild a package +Adding completion: rm:Removes packages from node_modules and from the project's package.json +Adding completion: remove:Removes packages from node_modules and from the project's package.json +Adding completion: unlink:Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link +Adding completion: up:Updates packages to their latest version based on the specified range +Adding completion: update:Updates packages to their latest version based on the specified range +Adding completion: audit:Checks for known security issues with the installed packages +Adding completion: licenses:Check licenses in consumed packages +Adding completion: ls:Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +Adding completion: list:Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +Adding completion: outdated:Check for outdated packages +Adding completion: exec:Executes a shell command in scope of a project +Adding completion: run:Runs a defined package script +Adding completion: start:Runs an arbitrary command specified in the package's "start" property of its "scripts" object +Adding completion: t:Runs a package's "test" script, if one was provided +Adding completion: test:Runs a package's "test" script, if one was provided +Adding completion: cat-file:Prints the contents of a file based on the hash value stored in the index file +Adding completion: cat-index:Prints the index file of a specific package from the store +Adding completion: find-hash:Experimental! Lists the packages that include the file with the specified hash. +Adding completion: pack:Create a tarball from a package +Adding completion: publish:Publishes a package to the registry +Adding completion: root:Prints the effective modules directory +Adding completion: store:Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store +Calling _describe +_describe found some completions + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm +Truncated words[*]: pnpm , +lastParam: , lastChar: +Adding extra empty parameter +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- '' '' +completion output: add Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency +import Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file +i Install all dependencies for a project +install Install all dependencies for a project +it Runs a pnpm install followed immediately by a pnpm test +install-test Runs a pnpm install followed immediately by a pnpm test +ln Connect the local project to another one +link Connect the local project to another one +prune Removes extraneous packages +rb Rebuild a package +rebuild Rebuild a package +rm Removes packages from node_modules and from the project's package.json +remove Removes packages from node_modules and from the project's package.json +unlink Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link +up Updates packages to their latest version based on the specified range +update Updates packages to their latest version based on the specified range +audit Checks for known security issues with the installed packages +licenses Check licenses in consumed packages +ls Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +list Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +outdated Check for outdated packages +exec Executes a shell command in scope of a project +run Runs a defined package script +start Runs an arbitrary command specified in the package's "start" property of its "scripts" object +t Runs a package's "test" script, if one was provided +test Runs a package's "test" script, if one was provided +cat-file Prints the contents of a file based on the hash value stored in the index file +cat-index Prints the index file of a specific package from the store +find-hash Experimental! Lists the packages that include the file with the specified hash. +pack Create a tarball from a package +publish Publishes a package to the registry +root Prints the effective modules directory +store Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store +:4 +last line: :4 +directive: 4 +completions: add Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency +import Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file +i Install all dependencies for a project +install Install all dependencies for a project +it Runs a pnpm install followed immediately by a pnpm test +install-test Runs a pnpm install followed immediately by a pnpm test +ln Connect the local project to another one +link Connect the local project to another one +prune Removes extraneous packages +rb Rebuild a package +rebuild Rebuild a package +rm Removes packages from node_modules and from the project's package.json +remove Removes packages from node_modules and from the project's package.json +unlink Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link +up Updates packages to their latest version based on the specified range +update Updates packages to their latest version based on the specified range +audit Checks for known security issues with the installed packages +licenses Check licenses in consumed packages +ls Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +list Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +outdated Check for outdated packages +exec Executes a shell command in scope of a project +run Runs a defined package script +start Runs an arbitrary command specified in the package's "start" property of its "scripts" object +t Runs a package's "test" script, if one was provided +test Runs a package's "test" script, if one was provided +cat-file Prints the contents of a file based on the hash value stored in the index file +cat-index Prints the index file of a specific package from the store +find-hash Experimental! Lists the packages that include the file with the specified hash. +pack Create a tarball from a package +publish Publishes a package to the registry +root Prints the effective modules directory +store Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store +flagPrefix: +Adding completion: add:Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency +Adding completion: import:Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file +Adding completion: i:Install all dependencies for a project +Adding completion: install:Install all dependencies for a project +Adding completion: it:Runs a pnpm install followed immediately by a pnpm test +Adding completion: install-test:Runs a pnpm install followed immediately by a pnpm test +Adding completion: ln:Connect the local project to another one +Adding completion: link:Connect the local project to another one +Adding completion: prune:Removes extraneous packages +Adding completion: rb:Rebuild a package +Adding completion: rebuild:Rebuild a package +Adding completion: rm:Removes packages from node_modules and from the project's package.json +Adding completion: remove:Removes packages from node_modules and from the project's package.json +Adding completion: unlink:Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link +Adding completion: up:Updates packages to their latest version based on the specified range +Adding completion: update:Updates packages to their latest version based on the specified range +Adding completion: audit:Checks for known security issues with the installed packages +Adding completion: licenses:Check licenses in consumed packages +Adding completion: ls:Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +Adding completion: list:Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +Adding completion: outdated:Check for outdated packages +Adding completion: exec:Executes a shell command in scope of a project +Adding completion: run:Runs a defined package script +Adding completion: start:Runs an arbitrary command specified in the package's "start" property of its "scripts" object +Adding completion: t:Runs a package's "test" script, if one was provided +Adding completion: test:Runs a package's "test" script, if one was provided +Adding completion: cat-file:Prints the contents of a file based on the hash value stored in the index file +Adding completion: cat-index:Prints the index file of a specific package from the store +Adding completion: find-hash:Experimental! Lists the packages that include the file with the specified hash. +Adding completion: pack:Create a tarball from a package +Adding completion: publish:Publishes a package to the registry +Adding completion: root:Prints the effective modules directory +Adding completion: store:Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store +Calling _describe +_describe found some completions + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm in +Truncated words[*]: pnpm in, +lastParam: in, lastChar: n +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- in +completion output: install Install all dependencies for a project +install-test Runs a pnpm install followed immediately by a pnpm test +:4 +last line: :4 +directive: 4 +completions: install Install all dependencies for a project +install-test Runs a pnpm install followed immediately by a pnpm test +flagPrefix: +Adding completion: install:Install all dependencies for a project +Adding completion: install-test:Runs a pnpm install followed immediately by a pnpm test +Calling _describe +_describe found some completions + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install -- +Truncated words[*]: pnpm install --, +lastParam: --, lastChar: - +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install -- +completion output: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules +--dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) +--fix-lockfile Fix broken lockfile entries automatically +--force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) +--global-dir Specify a custom directory to store global packages +--help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules +--ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs +--ignore-scripts Don't run lifecycle scripts +--ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. +--lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. +--merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests +--no-hoist Dependencies inside the modules directory will have access only to their listed dependencies +--no-lockfile Don't read or generate a `pnpm-lock.yaml` file +--no-optional `optionalDependencies` are not installed +--offline Trigger an error if any required dependencies are not available in local store +--optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store +--prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation +--prefer-offline Skip staleness checks for cached data, but request missing data from the server +--prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory +--recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" +--resolution-only Re-runs resolution: useful for printing out peer dependency issues +--shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them +--side-effects-cache Use or cache the results of (pre/post)install hooks +--side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk +--stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. +--strict-peer-dependencies Fail on missing or invalid peer dependencies +--use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail +--use-stderr Divert all output to stderr +--use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory +--workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build +--fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm +:4 +last line: :4 +directive: 4 +completions: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules +--dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) +--fix-lockfile Fix broken lockfile entries automatically +--force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) +--global-dir Specify a custom directory to store global packages +--help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules +--ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs +--ignore-scripts Don't run lifecycle scripts +--ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. +--lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. +--merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests +--no-hoist Dependencies inside the modules directory will have access only to their listed dependencies +--no-lockfile Don't read or generate a `pnpm-lock.yaml` file +--no-optional `optionalDependencies` are not installed +--offline Trigger an error if any required dependencies are not available in local store +--optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store +--prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation +--prefer-offline Skip staleness checks for cached data, but request missing data from the server +--prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory +--recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" +--resolution-only Re-runs resolution: useful for printing out peer dependency issues +--shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them +--side-effects-cache Use or cache the results of (pre/post)install hooks +--side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk +--stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. +--strict-peer-dependencies Fail on missing or invalid peer dependencies +--use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail +--use-stderr Divert all output to stderr +--use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory +--workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build +--fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm +flagPrefix: +Adding completion: --aggregate-output:Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules +Adding completion: --dev:Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) +Adding completion: --fix-lockfile:Fix broken lockfile entries automatically +Adding completion: --force:Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) +Adding completion: --global-dir:Specify a custom directory to store global packages +Adding completion: --help:Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules +Adding completion: --ignore-pnpmfile:Disable pnpm hooks defined in .pnpmfile.cjs +Adding completion: --ignore-scripts:Don't run lifecycle scripts +Adding completion: --ignore-workspace:Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. +Adding completion: --lockfile-only:Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. +Adding completion: --merge-git-branch-lockfiles:Merge lockfiles were generated on git branch be installed (instead of node_modules) requests +Adding completion: --no-hoist:Dependencies inside the modules directory will have access only to their listed dependencies +Adding completion: --no-lockfile:Don't read or generate a `pnpm-lock.yaml` file +Adding completion: --no-optional:`optionalDependencies` are not installed +Adding completion: --offline:Trigger an error if any required dependencies are not available in local store +Adding completion: --optimistic-repeat-install:Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store +Adding completion: --prefer-frozen-lockfile:If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation +Adding completion: --prefer-offline:Skip staleness checks for cached data, but request missing data from the server +Adding completion: --prod:Packages in `devDependencies` won't be installed pattern to the root of the modules directory +Adding completion: --recursive:Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" +Adding completion: --resolution-only:Re-runs resolution: useful for printing out peer dependency issues +Adding completion: --shamefully-hoist:All the subdeps will be hoisted into the root node_modules. Your code will have access to them +Adding completion: --side-effects-cache:Use or cache the results of (pre/post)install hooks +Adding completion: --side-effects-cache-readonly:Only use the side effects cache if present, do not create it for new packages are saved on the disk +Adding completion: --stream:Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. +Adding completion: --strict-peer-dependencies:Fail on missing or invalid peer dependencies +Adding completion: --use-running-store-server:Only allows installation with a store server. If no store server is running, installation will fail +Adding completion: --use-stderr:Divert all output to stderr +Adding completion: --use-store-server:Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory +Adding completion: --workspace-root:Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build +Adding completion: --fail-if-no-match:If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm +Calling _describe +_describe found some completions + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install -- +Truncated words[*]: pnpm install --, +lastParam: --, lastChar: - +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install -- +completion output: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules +--dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) +--fix-lockfile Fix broken lockfile entries automatically +--force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) +--global-dir Specify a custom directory to store global packages +--help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules +--ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs +--ignore-scripts Don't run lifecycle scripts +--ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. +--lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. +--merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests +--no-hoist Dependencies inside the modules directory will have access only to their listed dependencies +--no-lockfile Don't read or generate a `pnpm-lock.yaml` file +--no-optional `optionalDependencies` are not installed +--offline Trigger an error if any required dependencies are not available in local store +--optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store +--prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation +--prefer-offline Skip staleness checks for cached data, but request missing data from the server +--prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory +--recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" +--resolution-only Re-runs resolution: useful for printing out peer dependency issues +--shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them +--side-effects-cache Use or cache the results of (pre/post)install hooks +--side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk +--stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. +--strict-peer-dependencies Fail on missing or invalid peer dependencies +--use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail +--use-stderr Divert all output to stderr +--use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory +--workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build +--fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm +:4 +last line: :4 +directive: 4 +completions: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules +--dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) +--fix-lockfile Fix broken lockfile entries automatically +--force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) +--global-dir Specify a custom directory to store global packages +--help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules +--ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs +--ignore-scripts Don't run lifecycle scripts +--ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. +--lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. +--merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests +--no-hoist Dependencies inside the modules directory will have access only to their listed dependencies +--no-lockfile Don't read or generate a `pnpm-lock.yaml` file +--no-optional `optionalDependencies` are not installed +--offline Trigger an error if any required dependencies are not available in local store +--optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store +--prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation +--prefer-offline Skip staleness checks for cached data, but request missing data from the server +--prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory +--recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" +--resolution-only Re-runs resolution: useful for printing out peer dependency issues +--shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them +--side-effects-cache Use or cache the results of (pre/post)install hooks +--side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk +--stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. +--strict-peer-dependencies Fail on missing or invalid peer dependencies +--use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail +--use-stderr Divert all output to stderr +--use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory +--workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build +--fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm +flagPrefix: +Adding completion: --aggregate-output:Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules +Adding completion: --dev:Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) +Adding completion: --fix-lockfile:Fix broken lockfile entries automatically +Adding completion: --force:Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) +Adding completion: --global-dir:Specify a custom directory to store global packages +Adding completion: --help:Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules +Adding completion: --ignore-pnpmfile:Disable pnpm hooks defined in .pnpmfile.cjs +Adding completion: --ignore-scripts:Don't run lifecycle scripts +Adding completion: --ignore-workspace:Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. +Adding completion: --lockfile-only:Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. +Adding completion: --merge-git-branch-lockfiles:Merge lockfiles were generated on git branch be installed (instead of node_modules) requests +Adding completion: --no-hoist:Dependencies inside the modules directory will have access only to their listed dependencies +Adding completion: --no-lockfile:Don't read or generate a `pnpm-lock.yaml` file +Adding completion: --no-optional:`optionalDependencies` are not installed +Adding completion: --offline:Trigger an error if any required dependencies are not available in local store +Adding completion: --optimistic-repeat-install:Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store +Adding completion: --prefer-frozen-lockfile:If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation +Adding completion: --prefer-offline:Skip staleness checks for cached data, but request missing data from the server +Adding completion: --prod:Packages in `devDependencies` won't be installed pattern to the root of the modules directory +Adding completion: --recursive:Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" +Adding completion: --resolution-only:Re-runs resolution: useful for printing out peer dependency issues +Adding completion: --shamefully-hoist:All the subdeps will be hoisted into the root node_modules. Your code will have access to them +Adding completion: --side-effects-cache:Use or cache the results of (pre/post)install hooks +Adding completion: --side-effects-cache-readonly:Only use the side effects cache if present, do not create it for new packages are saved on the disk +Adding completion: --stream:Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. +Adding completion: --strict-peer-dependencies:Fail on missing or invalid peer dependencies +Adding completion: --use-running-store-server:Only allows installation with a store server. If no store server is running, installation will fail +Adding completion: --use-stderr:Divert all output to stderr +Adding completion: --use-store-server:Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory +Adding completion: --workspace-root:Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build +Adding completion: --fail-if-no-match:If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm +Calling _describe +_describe found some completions + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install --dd +Truncated words[*]: pnpm install --dd, +lastParam: --dd, lastChar: d +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dd +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install --dd +Truncated words[*]: pnpm install --dd, +lastParam: --dd, lastChar: d +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dd +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install --dd +Truncated words[*]: pnpm install --dd, +lastParam: --dd, lastChar: d +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dd +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install --dd +Truncated words[*]: pnpm install --dd, +lastParam: --dd, lastChar: d +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dd +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install --dd +Truncated words[*]: pnpm install --dd, +lastParam: --dd, lastChar: d +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dd +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install --dd +Truncated words[*]: pnpm install --dd, +lastParam: --dd, lastChar: d +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dd +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install --dd +Truncated words[*]: pnpm install --dd, +lastParam: --dd, lastChar: d +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dd +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install --dd +Truncated words[*]: pnpm install --dd, +lastParam: --dd, lastChar: d +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dd +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install --dd +Truncated words[*]: pnpm install --dd, +lastParam: --dd, lastChar: d +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dd +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install --dd +Truncated words[*]: pnpm install --dd, +lastParam: --dd, lastChar: d +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dd +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install --dd +Truncated words[*]: pnpm install --dd, +lastParam: --dd, lastChar: d +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dd +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install --dd +Truncated words[*]: pnpm install --dd, +lastParam: --dd, lastChar: d +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dd +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install --dd +Truncated words[*]: pnpm install --dd, +lastParam: --dd, lastChar: d +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dd +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install --dd +Truncated words[*]: pnpm install --dd, +lastParam: --dd, lastChar: d +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dd +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install --dd +Truncated words[*]: pnpm install --dd, +lastParam: --dd, lastChar: d +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dd +completion output: :4 +last line: :4 +directive: 4 +completions: +flagPrefix: +Calling _describe +_describe did not find completions. +Checking if we should do file completion. +deactivating file completion + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm +Truncated words[*]: pnpm , +lastParam: , lastChar: +Adding extra empty parameter +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- '' '' +completion output: add Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency +import Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file +i Install all dependencies for a project +install Install all dependencies for a project +it Runs a pnpm install followed immediately by a pnpm test +install-test Runs a pnpm install followed immediately by a pnpm test +ln Connect the local project to another one +link Connect the local project to another one +prune Removes extraneous packages +rb Rebuild a package +rebuild Rebuild a package +rm Removes packages from node_modules and from the project's package.json +remove Removes packages from node_modules and from the project's package.json +unlink Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link +up Updates packages to their latest version based on the specified range +update Updates packages to their latest version based on the specified range +audit Checks for known security issues with the installed packages +licenses Check licenses in consumed packages +ls Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +list Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +outdated Check for outdated packages +exec Executes a shell command in scope of a project +run Runs a defined package script +start Runs an arbitrary command specified in the package's "start" property of its "scripts" object +t Runs a package's "test" script, if one was provided +test Runs a package's "test" script, if one was provided +cat-file Prints the contents of a file based on the hash value stored in the index file +cat-index Prints the index file of a specific package from the store +find-hash Experimental! Lists the packages that include the file with the specified hash. +pack Create a tarball from a package +publish Publishes a package to the registry +root Prints the effective modules directory +store Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store +:4 +last line: :4 +directive: 4 +completions: add Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency +import Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file +i Install all dependencies for a project +install Install all dependencies for a project +it Runs a pnpm install followed immediately by a pnpm test +install-test Runs a pnpm install followed immediately by a pnpm test +ln Connect the local project to another one +link Connect the local project to another one +prune Removes extraneous packages +rb Rebuild a package +rebuild Rebuild a package +rm Removes packages from node_modules and from the project's package.json +remove Removes packages from node_modules and from the project's package.json +unlink Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link +up Updates packages to their latest version based on the specified range +update Updates packages to their latest version based on the specified range +audit Checks for known security issues with the installed packages +licenses Check licenses in consumed packages +ls Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +list Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +outdated Check for outdated packages +exec Executes a shell command in scope of a project +run Runs a defined package script +start Runs an arbitrary command specified in the package's "start" property of its "scripts" object +t Runs a package's "test" script, if one was provided +test Runs a package's "test" script, if one was provided +cat-file Prints the contents of a file based on the hash value stored in the index file +cat-index Prints the index file of a specific package from the store +find-hash Experimental! Lists the packages that include the file with the specified hash. +pack Create a tarball from a package +publish Publishes a package to the registry +root Prints the effective modules directory +store Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store +flagPrefix: +Adding completion: add:Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency +Adding completion: import:Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file +Adding completion: i:Install all dependencies for a project +Adding completion: install:Install all dependencies for a project +Adding completion: it:Runs a pnpm install followed immediately by a pnpm test +Adding completion: install-test:Runs a pnpm install followed immediately by a pnpm test +Adding completion: ln:Connect the local project to another one +Adding completion: link:Connect the local project to another one +Adding completion: prune:Removes extraneous packages +Adding completion: rb:Rebuild a package +Adding completion: rebuild:Rebuild a package +Adding completion: rm:Removes packages from node_modules and from the project's package.json +Adding completion: remove:Removes packages from node_modules and from the project's package.json +Adding completion: unlink:Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link +Adding completion: up:Updates packages to their latest version based on the specified range +Adding completion: update:Updates packages to their latest version based on the specified range +Adding completion: audit:Checks for known security issues with the installed packages +Adding completion: licenses:Check licenses in consumed packages +Adding completion: ls:Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +Adding completion: list:Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +Adding completion: outdated:Check for outdated packages +Adding completion: exec:Executes a shell command in scope of a project +Adding completion: run:Runs a defined package script +Adding completion: start:Runs an arbitrary command specified in the package's "start" property of its "scripts" object +Adding completion: t:Runs a package's "test" script, if one was provided +Adding completion: test:Runs a package's "test" script, if one was provided +Adding completion: cat-file:Prints the contents of a file based on the hash value stored in the index file +Adding completion: cat-index:Prints the index file of a specific package from the store +Adding completion: find-hash:Experimental! Lists the packages that include the file with the specified hash. +Adding completion: pack:Create a tarball from a package +Adding completion: publish:Publishes a package to the registry +Adding completion: root:Prints the effective modules directory +Adding completion: store:Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store +Calling _describe +_describe found some completions + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm ins +Truncated words[*]: pnpm ins, +lastParam: ins, lastChar: s +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- ins +completion output: install Install all dependencies for a project +install-test Runs a pnpm install followed immediately by a pnpm test +:4 +last line: :4 +directive: 4 +completions: install Install all dependencies for a project +install-test Runs a pnpm install followed immediately by a pnpm test +flagPrefix: +Adding completion: install:Install all dependencies for a project +Adding completion: install-test:Runs a pnpm install followed immediately by a pnpm test +Calling _describe +_describe found some completions + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install -- +Truncated words[*]: pnpm install --, +lastParam: --, lastChar: - +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install -- +completion output: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules +--dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) +--fix-lockfile Fix broken lockfile entries automatically +--force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) +--global-dir Specify a custom directory to store global packages +--help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules +--ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs +--ignore-scripts Don't run lifecycle scripts +--ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. +--lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. +--merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests +--no-hoist Dependencies inside the modules directory will have access only to their listed dependencies +--no-lockfile Don't read or generate a `pnpm-lock.yaml` file +--no-optional `optionalDependencies` are not installed +--offline Trigger an error if any required dependencies are not available in local store +--optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store +--prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation +--prefer-offline Skip staleness checks for cached data, but request missing data from the server +--prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory +--recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" +--resolution-only Re-runs resolution: useful for printing out peer dependency issues +--shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them +--side-effects-cache Use or cache the results of (pre/post)install hooks +--side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk +--stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. +--strict-peer-dependencies Fail on missing or invalid peer dependencies +--use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail +--use-stderr Divert all output to stderr +--use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory +--workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build +--fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm +:4 +last line: :4 +directive: 4 +completions: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules +--dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) +--fix-lockfile Fix broken lockfile entries automatically +--force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) +--global-dir Specify a custom directory to store global packages +--help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules +--ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs +--ignore-scripts Don't run lifecycle scripts +--ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. +--lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. +--merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests +--no-hoist Dependencies inside the modules directory will have access only to their listed dependencies +--no-lockfile Don't read or generate a `pnpm-lock.yaml` file +--no-optional `optionalDependencies` are not installed +--offline Trigger an error if any required dependencies are not available in local store +--optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store +--prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation +--prefer-offline Skip staleness checks for cached data, but request missing data from the server +--prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory +--recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" +--resolution-only Re-runs resolution: useful for printing out peer dependency issues +--shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them +--side-effects-cache Use or cache the results of (pre/post)install hooks +--side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk +--stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. +--strict-peer-dependencies Fail on missing or invalid peer dependencies +--use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail +--use-stderr Divert all output to stderr +--use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory +--workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build +--fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm +flagPrefix: +Adding completion: --aggregate-output:Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules +Adding completion: --dev:Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) +Adding completion: --fix-lockfile:Fix broken lockfile entries automatically +Adding completion: --force:Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) +Adding completion: --global-dir:Specify a custom directory to store global packages +Adding completion: --help:Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules +Adding completion: --ignore-pnpmfile:Disable pnpm hooks defined in .pnpmfile.cjs +Adding completion: --ignore-scripts:Don't run lifecycle scripts +Adding completion: --ignore-workspace:Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. +Adding completion: --lockfile-only:Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. +Adding completion: --merge-git-branch-lockfiles:Merge lockfiles were generated on git branch be installed (instead of node_modules) requests +Adding completion: --no-hoist:Dependencies inside the modules directory will have access only to their listed dependencies +Adding completion: --no-lockfile:Don't read or generate a `pnpm-lock.yaml` file +Adding completion: --no-optional:`optionalDependencies` are not installed +Adding completion: --offline:Trigger an error if any required dependencies are not available in local store +Adding completion: --optimistic-repeat-install:Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store +Adding completion: --prefer-frozen-lockfile:If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation +Adding completion: --prefer-offline:Skip staleness checks for cached data, but request missing data from the server +Adding completion: --prod:Packages in `devDependencies` won't be installed pattern to the root of the modules directory +Adding completion: --recursive:Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" +Adding completion: --resolution-only:Re-runs resolution: useful for printing out peer dependency issues +Adding completion: --shamefully-hoist:All the subdeps will be hoisted into the root node_modules. Your code will have access to them +Adding completion: --side-effects-cache:Use or cache the results of (pre/post)install hooks +Adding completion: --side-effects-cache-readonly:Only use the side effects cache if present, do not create it for new packages are saved on the disk +Adding completion: --stream:Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. +Adding completion: --strict-peer-dependencies:Fail on missing or invalid peer dependencies +Adding completion: --use-running-store-server:Only allows installation with a store server. If no store server is running, installation will fail +Adding completion: --use-stderr:Divert all output to stderr +Adding completion: --use-store-server:Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory +Adding completion: --workspace-root:Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build +Adding completion: --fail-if-no-match:If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm +Calling _describe +_describe found some completions + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install -- +Truncated words[*]: pnpm install --, +lastParam: --, lastChar: - +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install -- +completion output: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules +--dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) +--fix-lockfile Fix broken lockfile entries automatically +--force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) +--global-dir Specify a custom directory to store global packages +--help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules +--ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs +--ignore-scripts Don't run lifecycle scripts +--ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. +--lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. +--merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests +--no-hoist Dependencies inside the modules directory will have access only to their listed dependencies +--no-lockfile Don't read or generate a `pnpm-lock.yaml` file +--no-optional `optionalDependencies` are not installed +--offline Trigger an error if any required dependencies are not available in local store +--optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store +--prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation +--prefer-offline Skip staleness checks for cached data, but request missing data from the server +--prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory +--recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" +--resolution-only Re-runs resolution: useful for printing out peer dependency issues +--shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them +--side-effects-cache Use or cache the results of (pre/post)install hooks +--side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk +--stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. +--strict-peer-dependencies Fail on missing or invalid peer dependencies +--use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail +--use-stderr Divert all output to stderr +--use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory +--workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build +--fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm +:4 +last line: :4 +directive: 4 +completions: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules +--dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) +--fix-lockfile Fix broken lockfile entries automatically +--force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) +--global-dir Specify a custom directory to store global packages +--help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules +--ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs +--ignore-scripts Don't run lifecycle scripts +--ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. +--lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. +--merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests +--no-hoist Dependencies inside the modules directory will have access only to their listed dependencies +--no-lockfile Don't read or generate a `pnpm-lock.yaml` file +--no-optional `optionalDependencies` are not installed +--offline Trigger an error if any required dependencies are not available in local store +--optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store +--prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation +--prefer-offline Skip staleness checks for cached data, but request missing data from the server +--prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory +--recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" +--resolution-only Re-runs resolution: useful for printing out peer dependency issues +--shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them +--side-effects-cache Use or cache the results of (pre/post)install hooks +--side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk +--stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. +--strict-peer-dependencies Fail on missing or invalid peer dependencies +--use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail +--use-stderr Divert all output to stderr +--use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory +--workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build +--fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm +flagPrefix: +Adding completion: --aggregate-output:Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules +Adding completion: --dev:Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) +Adding completion: --fix-lockfile:Fix broken lockfile entries automatically +Adding completion: --force:Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) +Adding completion: --global-dir:Specify a custom directory to store global packages +Adding completion: --help:Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules +Adding completion: --ignore-pnpmfile:Disable pnpm hooks defined in .pnpmfile.cjs +Adding completion: --ignore-scripts:Don't run lifecycle scripts +Adding completion: --ignore-workspace:Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. +Adding completion: --lockfile-only:Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. +Adding completion: --merge-git-branch-lockfiles:Merge lockfiles were generated on git branch be installed (instead of node_modules) requests +Adding completion: --no-hoist:Dependencies inside the modules directory will have access only to their listed dependencies +Adding completion: --no-lockfile:Don't read or generate a `pnpm-lock.yaml` file +Adding completion: --no-optional:`optionalDependencies` are not installed +Adding completion: --offline:Trigger an error if any required dependencies are not available in local store +Adding completion: --optimistic-repeat-install:Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store +Adding completion: --prefer-frozen-lockfile:If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation +Adding completion: --prefer-offline:Skip staleness checks for cached data, but request missing data from the server +Adding completion: --prod:Packages in `devDependencies` won't be installed pattern to the root of the modules directory +Adding completion: --recursive:Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" +Adding completion: --resolution-only:Re-runs resolution: useful for printing out peer dependency issues +Adding completion: --shamefully-hoist:All the subdeps will be hoisted into the root node_modules. Your code will have access to them +Adding completion: --side-effects-cache:Use or cache the results of (pre/post)install hooks +Adding completion: --side-effects-cache-readonly:Only use the side effects cache if present, do not create it for new packages are saved on the disk +Adding completion: --stream:Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. +Adding completion: --strict-peer-dependencies:Fail on missing or invalid peer dependencies +Adding completion: --use-running-store-server:Only allows installation with a store server. If no store server is running, installation will fail +Adding completion: --use-stderr:Divert all output to stderr +Adding completion: --use-store-server:Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory +Adding completion: --workspace-root:Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build +Adding completion: --fail-if-no-match:If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm +Calling _describe +_describe found some completions + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm ins +Truncated words[*]: pnpm ins, +lastParam: ins, lastChar: s +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- ins +completion output: install Install all dependencies for a project +install-test Runs a pnpm install followed immediately by a pnpm test +:4 +last line: :4 +directive: 4 +completions: install Install all dependencies for a project +install-test Runs a pnpm install followed immediately by a pnpm test +flagPrefix: +Adding completion: install:Install all dependencies for a project +Adding completion: install-test:Runs a pnpm install followed immediately by a pnpm test +Calling _describe +_describe found some completions + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install -- +Truncated words[*]: pnpm install --, +lastParam: --, lastChar: - +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install -- +completion output: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules +--dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) +--fix-lockfile Fix broken lockfile entries automatically +--force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) +--global-dir Specify a custom directory to store global packages +--help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules +--ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs +--ignore-scripts Don't run lifecycle scripts +--ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. +--lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. +--merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests +--no-hoist Dependencies inside the modules directory will have access only to their listed dependencies +--no-lockfile Don't read or generate a `pnpm-lock.yaml` file +--no-optional `optionalDependencies` are not installed +--offline Trigger an error if any required dependencies are not available in local store +--optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store +--prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation +--prefer-offline Skip staleness checks for cached data, but request missing data from the server +--prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory +--recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" +--resolution-only Re-runs resolution: useful for printing out peer dependency issues +--shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them +--side-effects-cache Use or cache the results of (pre/post)install hooks +--side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk +--stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. +--strict-peer-dependencies Fail on missing or invalid peer dependencies +--use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail +--use-stderr Divert all output to stderr +--use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory +--workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build +--fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm +:4 +last line: :4 +directive: 4 +completions: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules +--dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) +--fix-lockfile Fix broken lockfile entries automatically +--force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) +--global-dir Specify a custom directory to store global packages +--help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules +--ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs +--ignore-scripts Don't run lifecycle scripts +--ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. +--lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. +--merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests +--no-hoist Dependencies inside the modules directory will have access only to their listed dependencies +--no-lockfile Don't read or generate a `pnpm-lock.yaml` file +--no-optional `optionalDependencies` are not installed +--offline Trigger an error if any required dependencies are not available in local store +--optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store +--prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation +--prefer-offline Skip staleness checks for cached data, but request missing data from the server +--prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory +--recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" +--resolution-only Re-runs resolution: useful for printing out peer dependency issues +--shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them +--side-effects-cache Use or cache the results of (pre/post)install hooks +--side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk +--stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. +--strict-peer-dependencies Fail on missing or invalid peer dependencies +--use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail +--use-stderr Divert all output to stderr +--use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory +--workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build +--fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm +flagPrefix: +Adding completion: --aggregate-output:Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules +Adding completion: --dev:Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) +Adding completion: --fix-lockfile:Fix broken lockfile entries automatically +Adding completion: --force:Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) +Adding completion: --global-dir:Specify a custom directory to store global packages +Adding completion: --help:Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules +Adding completion: --ignore-pnpmfile:Disable pnpm hooks defined in .pnpmfile.cjs +Adding completion: --ignore-scripts:Don't run lifecycle scripts +Adding completion: --ignore-workspace:Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. +Adding completion: --lockfile-only:Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. +Adding completion: --merge-git-branch-lockfiles:Merge lockfiles were generated on git branch be installed (instead of node_modules) requests +Adding completion: --no-hoist:Dependencies inside the modules directory will have access only to their listed dependencies +Adding completion: --no-lockfile:Don't read or generate a `pnpm-lock.yaml` file +Adding completion: --no-optional:`optionalDependencies` are not installed +Adding completion: --offline:Trigger an error if any required dependencies are not available in local store +Adding completion: --optimistic-repeat-install:Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store +Adding completion: --prefer-frozen-lockfile:If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation +Adding completion: --prefer-offline:Skip staleness checks for cached data, but request missing data from the server +Adding completion: --prod:Packages in `devDependencies` won't be installed pattern to the root of the modules directory +Adding completion: --recursive:Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" +Adding completion: --resolution-only:Re-runs resolution: useful for printing out peer dependency issues +Adding completion: --shamefully-hoist:All the subdeps will be hoisted into the root node_modules. Your code will have access to them +Adding completion: --side-effects-cache:Use or cache the results of (pre/post)install hooks +Adding completion: --side-effects-cache-readonly:Only use the side effects cache if present, do not create it for new packages are saved on the disk +Adding completion: --stream:Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. +Adding completion: --strict-peer-dependencies:Fail on missing or invalid peer dependencies +Adding completion: --use-running-store-server:Only allows installation with a store server. If no store server is running, installation will fail +Adding completion: --use-stderr:Divert all output to stderr +Adding completion: --use-store-server:Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory +Adding completion: --workspace-root:Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build +Adding completion: --fail-if-no-match:If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm +Calling _describe +_describe found some completions + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm insta +Truncated words[*]: pnpm insta, +lastParam: insta, lastChar: a +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- insta +completion output: install Install all dependencies for a project +install-test Runs a pnpm install followed immediately by a pnpm test +:4 +last line: :4 +directive: 4 +completions: install Install all dependencies for a project +install-test Runs a pnpm install followed immediately by a pnpm test +flagPrefix: +Adding completion: install:Install all dependencies for a project +Adding completion: install-test:Runs a pnpm install followed immediately by a pnpm test +Calling _describe +_describe found some completions + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install -- +Truncated words[*]: pnpm install --, +lastParam: --, lastChar: - +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install -- +completion output: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules +--dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) +--fix-lockfile Fix broken lockfile entries automatically +--force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) +--global-dir Specify a custom directory to store global packages +--help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules +--ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs +--ignore-scripts Don't run lifecycle scripts +--ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. +--lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. +--merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests +--no-hoist Dependencies inside the modules directory will have access only to their listed dependencies +--no-lockfile Don't read or generate a `pnpm-lock.yaml` file +--no-optional `optionalDependencies` are not installed +--offline Trigger an error if any required dependencies are not available in local store +--optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store +--prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation +--prefer-offline Skip staleness checks for cached data, but request missing data from the server +--prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory +--recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" +--resolution-only Re-runs resolution: useful for printing out peer dependency issues +--shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them +--side-effects-cache Use or cache the results of (pre/post)install hooks +--side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk +--stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. +--strict-peer-dependencies Fail on missing or invalid peer dependencies +--use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail +--use-stderr Divert all output to stderr +--use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory +--workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build +--fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm +:4 +last line: :4 +directive: 4 +completions: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules +--dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) +--fix-lockfile Fix broken lockfile entries automatically +--force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) +--global-dir Specify a custom directory to store global packages +--help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules +--ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs +--ignore-scripts Don't run lifecycle scripts +--ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. +--lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. +--merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests +--no-hoist Dependencies inside the modules directory will have access only to their listed dependencies +--no-lockfile Don't read or generate a `pnpm-lock.yaml` file +--no-optional `optionalDependencies` are not installed +--offline Trigger an error if any required dependencies are not available in local store +--optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store +--prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation +--prefer-offline Skip staleness checks for cached data, but request missing data from the server +--prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory +--recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" +--resolution-only Re-runs resolution: useful for printing out peer dependency issues +--shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them +--side-effects-cache Use or cache the results of (pre/post)install hooks +--side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk +--stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. +--strict-peer-dependencies Fail on missing or invalid peer dependencies +--use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail +--use-stderr Divert all output to stderr +--use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory +--workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build +--fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm +flagPrefix: +Adding completion: --aggregate-output:Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules +Adding completion: --dev:Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) +Adding completion: --fix-lockfile:Fix broken lockfile entries automatically +Adding completion: --force:Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) +Adding completion: --global-dir:Specify a custom directory to store global packages +Adding completion: --help:Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules +Adding completion: --ignore-pnpmfile:Disable pnpm hooks defined in .pnpmfile.cjs +Adding completion: --ignore-scripts:Don't run lifecycle scripts +Adding completion: --ignore-workspace:Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. +Adding completion: --lockfile-only:Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. +Adding completion: --merge-git-branch-lockfiles:Merge lockfiles were generated on git branch be installed (instead of node_modules) requests +Adding completion: --no-hoist:Dependencies inside the modules directory will have access only to their listed dependencies +Adding completion: --no-lockfile:Don't read or generate a `pnpm-lock.yaml` file +Adding completion: --no-optional:`optionalDependencies` are not installed +Adding completion: --offline:Trigger an error if any required dependencies are not available in local store +Adding completion: --optimistic-repeat-install:Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store +Adding completion: --prefer-frozen-lockfile:If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation +Adding completion: --prefer-offline:Skip staleness checks for cached data, but request missing data from the server +Adding completion: --prod:Packages in `devDependencies` won't be installed pattern to the root of the modules directory +Adding completion: --recursive:Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" +Adding completion: --resolution-only:Re-runs resolution: useful for printing out peer dependency issues +Adding completion: --shamefully-hoist:All the subdeps will be hoisted into the root node_modules. Your code will have access to them +Adding completion: --side-effects-cache:Use or cache the results of (pre/post)install hooks +Adding completion: --side-effects-cache-readonly:Only use the side effects cache if present, do not create it for new packages are saved on the disk +Adding completion: --stream:Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. +Adding completion: --strict-peer-dependencies:Fail on missing or invalid peer dependencies +Adding completion: --use-running-store-server:Only allows installation with a store server. If no store server is running, installation will fail +Adding completion: --use-stderr:Divert all output to stderr +Adding completion: --use-store-server:Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory +Adding completion: --workspace-root:Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build +Adding completion: --fail-if-no-match:If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm +Calling _describe +_describe found some completions + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm +Truncated words[*]: pnpm , +lastParam: , lastChar: +Adding extra empty parameter +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- '' '' +completion output: add Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency +import Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file +i Install all dependencies for a project +install Install all dependencies for a project +it Runs a pnpm install followed immediately by a pnpm test +install-test Runs a pnpm install followed immediately by a pnpm test +ln Connect the local project to another one +link Connect the local project to another one +prune Removes extraneous packages +rb Rebuild a package +rebuild Rebuild a package +rm Removes packages from node_modules and from the project's package.json +remove Removes packages from node_modules and from the project's package.json +unlink Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link +up Updates packages to their latest version based on the specified range +update Updates packages to their latest version based on the specified range +audit Checks for known security issues with the installed packages +licenses Check licenses in consumed packages +ls Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +list Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +outdated Check for outdated packages +exec Executes a shell command in scope of a project +run Runs a defined package script +start Runs an arbitrary command specified in the package's "start" property of its "scripts" object +t Runs a package's "test" script, if one was provided +test Runs a package's "test" script, if one was provided +cat-file Prints the contents of a file based on the hash value stored in the index file +cat-index Prints the index file of a specific package from the store +find-hash Experimental! Lists the packages that include the file with the specified hash. +pack Create a tarball from a package +publish Publishes a package to the registry +root Prints the effective modules directory +store Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store +:4 +last line: :4 +directive: 4 +completions: add Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency +import Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file +i Install all dependencies for a project +install Install all dependencies for a project +it Runs a pnpm install followed immediately by a pnpm test +install-test Runs a pnpm install followed immediately by a pnpm test +ln Connect the local project to another one +link Connect the local project to another one +prune Removes extraneous packages +rb Rebuild a package +rebuild Rebuild a package +rm Removes packages from node_modules and from the project's package.json +remove Removes packages from node_modules and from the project's package.json +unlink Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link +up Updates packages to their latest version based on the specified range +update Updates packages to their latest version based on the specified range +audit Checks for known security issues with the installed packages +licenses Check licenses in consumed packages +ls Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +list Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +outdated Check for outdated packages +exec Executes a shell command in scope of a project +run Runs a defined package script +start Runs an arbitrary command specified in the package's "start" property of its "scripts" object +t Runs a package's "test" script, if one was provided +test Runs a package's "test" script, if one was provided +cat-file Prints the contents of a file based on the hash value stored in the index file +cat-index Prints the index file of a specific package from the store +find-hash Experimental! Lists the packages that include the file with the specified hash. +pack Create a tarball from a package +publish Publishes a package to the registry +root Prints the effective modules directory +store Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store +flagPrefix: +Adding completion: add:Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency +Adding completion: import:Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file +Adding completion: i:Install all dependencies for a project +Adding completion: install:Install all dependencies for a project +Adding completion: it:Runs a pnpm install followed immediately by a pnpm test +Adding completion: install-test:Runs a pnpm install followed immediately by a pnpm test +Adding completion: ln:Connect the local project to another one +Adding completion: link:Connect the local project to another one +Adding completion: prune:Removes extraneous packages +Adding completion: rb:Rebuild a package +Adding completion: rebuild:Rebuild a package +Adding completion: rm:Removes packages from node_modules and from the project's package.json +Adding completion: remove:Removes packages from node_modules and from the project's package.json +Adding completion: unlink:Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link +Adding completion: up:Updates packages to their latest version based on the specified range +Adding completion: update:Updates packages to their latest version based on the specified range +Adding completion: audit:Checks for known security issues with the installed packages +Adding completion: licenses:Check licenses in consumed packages +Adding completion: ls:Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +Adding completion: list:Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +Adding completion: outdated:Check for outdated packages +Adding completion: exec:Executes a shell command in scope of a project +Adding completion: run:Runs a defined package script +Adding completion: start:Runs an arbitrary command specified in the package's "start" property of its "scripts" object +Adding completion: t:Runs a package's "test" script, if one was provided +Adding completion: test:Runs a package's "test" script, if one was provided +Adding completion: cat-file:Prints the contents of a file based on the hash value stored in the index file +Adding completion: cat-index:Prints the index file of a specific package from the store +Adding completion: find-hash:Experimental! Lists the packages that include the file with the specified hash. +Adding completion: pack:Create a tarball from a package +Adding completion: publish:Publishes a package to the registry +Adding completion: root:Prints the effective modules directory +Adding completion: store:Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store +Calling _describe +_describe found some completions + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm +Truncated words[*]: pnpm , +lastParam: , lastChar: +Adding extra empty parameter +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- '' '' +completion output: add Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency +import Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file +i Install all dependencies for a project +install Install all dependencies for a project +it Runs a pnpm install followed immediately by a pnpm test +install-test Runs a pnpm install followed immediately by a pnpm test +ln Connect the local project to another one +link Connect the local project to another one +prune Removes extraneous packages +rb Rebuild a package +rebuild Rebuild a package +rm Removes packages from node_modules and from the project's package.json +remove Removes packages from node_modules and from the project's package.json +unlink Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link +up Updates packages to their latest version based on the specified range +update Updates packages to their latest version based on the specified range +audit Checks for known security issues with the installed packages +licenses Check licenses in consumed packages +ls Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +list Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +outdated Check for outdated packages +exec Executes a shell command in scope of a project +run Runs a defined package script +start Runs an arbitrary command specified in the package's "start" property of its "scripts" object +t Runs a package's "test" script, if one was provided +test Runs a package's "test" script, if one was provided +cat-file Prints the contents of a file based on the hash value stored in the index file +cat-index Prints the index file of a specific package from the store +find-hash Experimental! Lists the packages that include the file with the specified hash. +pack Create a tarball from a package +publish Publishes a package to the registry +root Prints the effective modules directory +store Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store +:4 +last line: :4 +directive: 4 +completions: add Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency +import Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file +i Install all dependencies for a project +install Install all dependencies for a project +it Runs a pnpm install followed immediately by a pnpm test +install-test Runs a pnpm install followed immediately by a pnpm test +ln Connect the local project to another one +link Connect the local project to another one +prune Removes extraneous packages +rb Rebuild a package +rebuild Rebuild a package +rm Removes packages from node_modules and from the project's package.json +remove Removes packages from node_modules and from the project's package.json +unlink Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link +up Updates packages to their latest version based on the specified range +update Updates packages to their latest version based on the specified range +audit Checks for known security issues with the installed packages +licenses Check licenses in consumed packages +ls Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +list Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +outdated Check for outdated packages +exec Executes a shell command in scope of a project +run Runs a defined package script +start Runs an arbitrary command specified in the package's "start" property of its "scripts" object +t Runs a package's "test" script, if one was provided +test Runs a package's "test" script, if one was provided +cat-file Prints the contents of a file based on the hash value stored in the index file +cat-index Prints the index file of a specific package from the store +find-hash Experimental! Lists the packages that include the file with the specified hash. +pack Create a tarball from a package +publish Publishes a package to the registry +root Prints the effective modules directory +store Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store +flagPrefix: +Adding completion: add:Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency +Adding completion: import:Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file +Adding completion: i:Install all dependencies for a project +Adding completion: install:Install all dependencies for a project +Adding completion: it:Runs a pnpm install followed immediately by a pnpm test +Adding completion: install-test:Runs a pnpm install followed immediately by a pnpm test +Adding completion: ln:Connect the local project to another one +Adding completion: link:Connect the local project to another one +Adding completion: prune:Removes extraneous packages +Adding completion: rb:Rebuild a package +Adding completion: rebuild:Rebuild a package +Adding completion: rm:Removes packages from node_modules and from the project's package.json +Adding completion: remove:Removes packages from node_modules and from the project's package.json +Adding completion: unlink:Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link +Adding completion: up:Updates packages to their latest version based on the specified range +Adding completion: update:Updates packages to their latest version based on the specified range +Adding completion: audit:Checks for known security issues with the installed packages +Adding completion: licenses:Check licenses in consumed packages +Adding completion: ls:Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +Adding completion: list:Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure +Adding completion: outdated:Check for outdated packages +Adding completion: exec:Executes a shell command in scope of a project +Adding completion: run:Runs a defined package script +Adding completion: start:Runs an arbitrary command specified in the package's "start" property of its "scripts" object +Adding completion: t:Runs a package's "test" script, if one was provided +Adding completion: test:Runs a package's "test" script, if one was provided +Adding completion: cat-file:Prints the contents of a file based on the hash value stored in the index file +Adding completion: cat-index:Prints the index file of a specific package from the store +Adding completion: find-hash:Experimental! Lists the packages that include the file with the specified hash. +Adding completion: pack:Create a tarball from a package +Adding completion: publish:Publishes a package to the registry +Adding completion: root:Prints the effective modules directory +Adding completion: store:Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store +Calling _describe +_describe found some completions + +========= starting completion logic ========== +CURRENT: 2, words[*]: pnpm ins +Truncated words[*]: pnpm ins, +lastParam: ins, lastChar: s +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- ins +completion output: install Install all dependencies for a project +install-test Runs a pnpm install followed immediately by a pnpm test +:4 +last line: :4 +directive: 4 +completions: install Install all dependencies for a project +install-test Runs a pnpm install followed immediately by a pnpm test +flagPrefix: +Adding completion: install:Install all dependencies for a project +Adding completion: install-test:Runs a pnpm install followed immediately by a pnpm test +Calling _describe +_describe found some completions + +========= starting completion logic ========== +CURRENT: 3, words[*]: pnpm install -- +Truncated words[*]: pnpm install --, +lastParam: --, lastChar: - +About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install -- +completion output: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules +--dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) +--fix-lockfile Fix broken lockfile entries automatically +--force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) +--global-dir Specify a custom directory to store global packages +--help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules +--ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs +--ignore-scripts Don't run lifecycle scripts +--ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. +--lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. +--merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests +--no-hoist Dependencies inside the modules directory will have access only to their listed dependencies +--no-lockfile Don't read or generate a `pnpm-lock.yaml` file +--no-optional `optionalDependencies` are not installed +--offline Trigger an error if any required dependencies are not available in local store +--optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store +--prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation +--prefer-offline Skip staleness checks for cached data, but request missing data from the server +--prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory +--recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" +--resolution-only Re-runs resolution: useful for printing out peer dependency issues +--shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them +--side-effects-cache Use or cache the results of (pre/post)install hooks +--side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk +--stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. +--strict-peer-dependencies Fail on missing or invalid peer dependencies +--use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail +--use-stderr Divert all output to stderr +--use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory +--workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build +--fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm +:4 +last line: :4 +directive: 4 +completions: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules +--dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) +--fix-lockfile Fix broken lockfile entries automatically +--force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) +--global-dir Specify a custom directory to store global packages +--help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules +--ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs +--ignore-scripts Don't run lifecycle scripts +--ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. +--lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. +--merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests +--no-hoist Dependencies inside the modules directory will have access only to their listed dependencies +--no-lockfile Don't read or generate a `pnpm-lock.yaml` file +--no-optional `optionalDependencies` are not installed +--offline Trigger an error if any required dependencies are not available in local store +--optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store +--prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation +--prefer-offline Skip staleness checks for cached data, but request missing data from the server +--prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory +--recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" +--resolution-only Re-runs resolution: useful for printing out peer dependency issues +--shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them +--side-effects-cache Use or cache the results of (pre/post)install hooks +--side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk +--stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. +--strict-peer-dependencies Fail on missing or invalid peer dependencies +--use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail +--use-stderr Divert all output to stderr +--use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory +--workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build +--fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm +flagPrefix: +Adding completion: --aggregate-output:Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules +Adding completion: --dev:Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) +Adding completion: --fix-lockfile:Fix broken lockfile entries automatically +Adding completion: --force:Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) +Adding completion: --global-dir:Specify a custom directory to store global packages +Adding completion: --help:Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules +Adding completion: --ignore-pnpmfile:Disable pnpm hooks defined in .pnpmfile.cjs +Adding completion: --ignore-scripts:Don't run lifecycle scripts +Adding completion: --ignore-workspace:Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. +Adding completion: --lockfile-only:Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. +Adding completion: --merge-git-branch-lockfiles:Merge lockfiles were generated on git branch be installed (instead of node_modules) requests +Adding completion: --no-hoist:Dependencies inside the modules directory will have access only to their listed dependencies +Adding completion: --no-lockfile:Don't read or generate a `pnpm-lock.yaml` file +Adding completion: --no-optional:`optionalDependencies` are not installed +Adding completion: --offline:Trigger an error if any required dependencies are not available in local store +Adding completion: --optimistic-repeat-install:Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store +Adding completion: --prefer-frozen-lockfile:If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation +Adding completion: --prefer-offline:Skip staleness checks for cached data, but request missing data from the server +Adding completion: --prod:Packages in `devDependencies` won't be installed pattern to the root of the modules directory +Adding completion: --recursive:Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" +Adding completion: --resolution-only:Re-runs resolution: useful for printing out peer dependency issues +Adding completion: --shamefully-hoist:All the subdeps will be hoisted into the root node_modules. Your code will have access to them +Adding completion: --side-effects-cache:Use or cache the results of (pre/post)install hooks +Adding completion: --side-effects-cache-readonly:Only use the side effects cache if present, do not create it for new packages are saved on the disk +Adding completion: --stream:Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. +Adding completion: --strict-peer-dependencies:Fail on missing or invalid peer dependencies +Adding completion: --use-running-store-server:Only allows installation with a store server. If no store server is running, installation will fail +Adding completion: --use-stderr:Divert all output to stderr +Adding completion: --use-store-server:Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory +Adding completion: --workspace-root:Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build +Adding completion: --fail-if-no-match:If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm +Calling _describe +_describe found some completions From 4a26c651019868b1ec727e885579762ac9ada00c Mon Sep 17 00:00:00 2001 From: AmirSa12 Date: Sun, 7 Sep 2025 11:21:28 +0330 Subject: [PATCH 7/8] update --- bin/completions/completion-producers.ts | 2 +- bin/handlers/pnpm-handler.ts | 32 ++++++++++++++++++------- 2 files changed, 25 insertions(+), 9 deletions(-) diff --git a/bin/completions/completion-producers.ts b/bin/completions/completion-producers.ts index 4450250..cb03067 100644 --- a/bin/completions/completion-producers.ts +++ b/bin/completions/completion-producers.ts @@ -13,7 +13,7 @@ export const packageJsonScriptCompletion = async ( ); }; -// provides completions for package dependencies from package.json.. `pnpm add ` +// provides completions for package dependencies from package.json.. for commands like remove `pnpm remove ` export const packageJsonDependencyCompletion = async ( complete: Complete ): Promise => { diff --git a/bin/handlers/pnpm-handler.ts b/bin/handlers/pnpm-handler.ts index e9b01fa..22031b0 100644 --- a/bin/handlers/pnpm-handler.ts +++ b/bin/handlers/pnpm-handler.ts @@ -1,6 +1,17 @@ -import { execFile, execFileSync } from 'child_process'; -import { promisify } from 'util'; +import { promisify } from 'node:util'; +import child_process from 'node:child_process'; + +const exec = promisify(child_process.exec); +const { execSync } = child_process; import type { PackageManagerCompletion } from '../package-manager-completion.js'; +import { Command } from '../../src/t.js'; + +interface LazyCommand extends Command { + _lazyCommand?: string; + _optionsLoaded?: boolean; + optionsRaw?: Map; +} + import { packageJsonScriptCompletion, packageJsonDependencyCompletion, @@ -15,7 +26,8 @@ import { type ParsedOption, } from '../utils/text-utils.js'; -const execFileP = promisify(execFile); +// regex to detect options section in help text +const OPTIONS_SECTION_RE = /^\s*Options:/i; // we parse the pnpm help text to extract commands and their descriptions! export function parsePnpmHelp(helpText: string): Record { @@ -49,7 +61,7 @@ export function parsePnpmHelp(helpText: string): Record { }; for (const line of helpLines) { - if (/^\s*Options:/i.test(line)) break; // we stop at options + if (OPTIONS_SECTION_RE.test(line)) break; // we stop at options // we match the command row const rowMatch = line.match(COMMAND_ROW_RE); @@ -81,7 +93,7 @@ export async function getPnpmCommandsFromMainHelp(): Promise< Record > { try { - const { stdout } = await execFileP('pnpm', ['--help'], { + const { stdout } = await exec('pnpm --help', { encoding: 'utf8', timeout: 500, maxBuffer: 4 * 1024 * 1024, @@ -157,9 +169,12 @@ export function parsePnpmOptions( } // we load the dynamic options synchronously when requested ( separated from the command loading ) -export function loadDynamicOptionsSync(cmd: any, command: string): void { +export function loadDynamicOptionsSync( + cmd: LazyCommand, + command: string +): void { try { - const stdout = execFileSync('pnpm', [command, '--help'], { + const stdout = execSync(`pnpm ${command} --help`, { encoding: 'utf8', timeout: 500, }); @@ -174,7 +189,8 @@ export function loadDynamicOptionsSync(cmd: any, command: string): void { } // we setup the lazy option loading for a command -function setupLazyOptionLoading(cmd: any, command: string): void { + +function setupLazyOptionLoading(cmd: LazyCommand, command: string): void { cmd._lazyCommand = command; cmd._optionsLoaded = false; From eb86cfeef8bb92dace3b1d9cefaeb2439d5fe19b Mon Sep 17 00:00:00 2001 From: AmirSa12 Date: Mon, 8 Sep 2025 12:28:22 +0330 Subject: [PATCH 8/8] update --- bin/handlers/pnpm-handler.ts | 4 +- completion-debug.log | 3524 ---------------------------------- 2 files changed, 2 insertions(+), 3526 deletions(-) delete mode 100644 completion-debug.log diff --git a/bin/handlers/pnpm-handler.ts b/bin/handlers/pnpm-handler.ts index 22031b0..6e9ad11 100644 --- a/bin/handlers/pnpm-handler.ts +++ b/bin/handlers/pnpm-handler.ts @@ -4,12 +4,12 @@ import child_process from 'node:child_process'; const exec = promisify(child_process.exec); const { execSync } = child_process; import type { PackageManagerCompletion } from '../package-manager-completion.js'; -import { Command } from '../../src/t.js'; +import { Command, Option } from '../../src/t.js'; interface LazyCommand extends Command { _lazyCommand?: string; _optionsLoaded?: boolean; - optionsRaw?: Map; + optionsRaw?: Map; } import { diff --git a/completion-debug.log b/completion-debug.log deleted file mode 100644 index 7314464..0000000 --- a/completion-debug.log +++ /dev/null @@ -1,3524 +0,0 @@ - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install -- -Truncated words[*]: pnpm install --, -lastParam: --, lastChar: - -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install -- -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install -- -Truncated words[*]: pnpm install --, -lastParam: --, lastChar: - -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install -- -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install -- -Truncated words[*]: pnpm install --, -lastParam: --, lastChar: - -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install -- -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm -Truncated words[*]: pnpm , -lastParam: , lastChar: -Adding extra empty parameter -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- '' '' -completion output: add Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency -import Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file -i Install all dependencies for a project -install Install all dependencies for a project -it Runs a pnpm install followed immediately by a pnpm test -install-test Runs a pnpm install followed immediately by a pnpm test -ln Connect the local project to another one -link Connect the local project to another one -prune Removes extraneous packages -rb Rebuild a package -rebuild Rebuild a package -rm Removes packages from node_modules and from the project's package.json -remove Removes packages from node_modules and from the project's package.json -unlink Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link -up Updates packages to their latest version based on the specified range -update Updates packages to their latest version based on the specified range -audit Checks for known security issues with the installed packages -licenses Check licenses in consumed packages -ls Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -list Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -outdated Check for outdated packages -exec Executes a shell command in scope of a project -run Runs a defined package script -start Runs an arbitrary command specified in the package's "start" property of its "scripts" object -t Runs a package's "test" script, if one was provided -test Runs a package's "test" script, if one was provided -cat-file Prints the contents of a file based on the hash value stored in the index file -cat-index Prints the index file of a specific package from the store -find-hash Experimental! Lists the packages that include the file with the specified hash. -pack Create a tarball from a package -publish Publishes a package to the registry -root Prints the effective modules directory -store Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store -:4 -last line: :4 -directive: 4 -completions: add Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency -import Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file -i Install all dependencies for a project -install Install all dependencies for a project -it Runs a pnpm install followed immediately by a pnpm test -install-test Runs a pnpm install followed immediately by a pnpm test -ln Connect the local project to another one -link Connect the local project to another one -prune Removes extraneous packages -rb Rebuild a package -rebuild Rebuild a package -rm Removes packages from node_modules and from the project's package.json -remove Removes packages from node_modules and from the project's package.json -unlink Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link -up Updates packages to their latest version based on the specified range -update Updates packages to their latest version based on the specified range -audit Checks for known security issues with the installed packages -licenses Check licenses in consumed packages -ls Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -list Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -outdated Check for outdated packages -exec Executes a shell command in scope of a project -run Runs a defined package script -start Runs an arbitrary command specified in the package's "start" property of its "scripts" object -t Runs a package's "test" script, if one was provided -test Runs a package's "test" script, if one was provided -cat-file Prints the contents of a file based on the hash value stored in the index file -cat-index Prints the index file of a specific package from the store -find-hash Experimental! Lists the packages that include the file with the specified hash. -pack Create a tarball from a package -publish Publishes a package to the registry -root Prints the effective modules directory -store Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store -flagPrefix: -Adding completion: add:Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency -Adding completion: import:Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file -Adding completion: i:Install all dependencies for a project -Adding completion: install:Install all dependencies for a project -Adding completion: it:Runs a pnpm install followed immediately by a pnpm test -Adding completion: install-test:Runs a pnpm install followed immediately by a pnpm test -Adding completion: ln:Connect the local project to another one -Adding completion: link:Connect the local project to another one -Adding completion: prune:Removes extraneous packages -Adding completion: rb:Rebuild a package -Adding completion: rebuild:Rebuild a package -Adding completion: rm:Removes packages from node_modules and from the project's package.json -Adding completion: remove:Removes packages from node_modules and from the project's package.json -Adding completion: unlink:Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link -Adding completion: up:Updates packages to their latest version based on the specified range -Adding completion: update:Updates packages to their latest version based on the specified range -Adding completion: audit:Checks for known security issues with the installed packages -Adding completion: licenses:Check licenses in consumed packages -Adding completion: ls:Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -Adding completion: list:Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -Adding completion: outdated:Check for outdated packages -Adding completion: exec:Executes a shell command in scope of a project -Adding completion: run:Runs a defined package script -Adding completion: start:Runs an arbitrary command specified in the package's "start" property of its "scripts" object -Adding completion: t:Runs a package's "test" script, if one was provided -Adding completion: test:Runs a package's "test" script, if one was provided -Adding completion: cat-file:Prints the contents of a file based on the hash value stored in the index file -Adding completion: cat-index:Prints the index file of a specific package from the store -Adding completion: find-hash:Experimental! Lists the packages that include the file with the specified hash. -Adding completion: pack:Create a tarball from a package -Adding completion: publish:Publishes a package to the registry -Adding completion: root:Prints the effective modules directory -Adding completion: store:Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store -Calling _describe -_describe found some completions - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm -Truncated words[*]: pnpm , -lastParam: , lastChar: -Adding extra empty parameter -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- '' '' -completion output: add Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency -import Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file -i Install all dependencies for a project -install Install all dependencies for a project -it Runs a pnpm install followed immediately by a pnpm test -install-test Runs a pnpm install followed immediately by a pnpm test -ln Connect the local project to another one -link Connect the local project to another one -prune Removes extraneous packages -rb Rebuild a package -rebuild Rebuild a package -rm Removes packages from node_modules and from the project's package.json -remove Removes packages from node_modules and from the project's package.json -unlink Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link -up Updates packages to their latest version based on the specified range -update Updates packages to their latest version based on the specified range -audit Checks for known security issues with the installed packages -licenses Check licenses in consumed packages -ls Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -list Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -outdated Check for outdated packages -exec Executes a shell command in scope of a project -run Runs a defined package script -start Runs an arbitrary command specified in the package's "start" property of its "scripts" object -t Runs a package's "test" script, if one was provided -test Runs a package's "test" script, if one was provided -cat-file Prints the contents of a file based on the hash value stored in the index file -cat-index Prints the index file of a specific package from the store -find-hash Experimental! Lists the packages that include the file with the specified hash. -pack Create a tarball from a package -publish Publishes a package to the registry -root Prints the effective modules directory -store Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store -:4 -last line: :4 -directive: 4 -completions: add Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency -import Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file -i Install all dependencies for a project -install Install all dependencies for a project -it Runs a pnpm install followed immediately by a pnpm test -install-test Runs a pnpm install followed immediately by a pnpm test -ln Connect the local project to another one -link Connect the local project to another one -prune Removes extraneous packages -rb Rebuild a package -rebuild Rebuild a package -rm Removes packages from node_modules and from the project's package.json -remove Removes packages from node_modules and from the project's package.json -unlink Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link -up Updates packages to their latest version based on the specified range -update Updates packages to their latest version based on the specified range -audit Checks for known security issues with the installed packages -licenses Check licenses in consumed packages -ls Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -list Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -outdated Check for outdated packages -exec Executes a shell command in scope of a project -run Runs a defined package script -start Runs an arbitrary command specified in the package's "start" property of its "scripts" object -t Runs a package's "test" script, if one was provided -test Runs a package's "test" script, if one was provided -cat-file Prints the contents of a file based on the hash value stored in the index file -cat-index Prints the index file of a specific package from the store -find-hash Experimental! Lists the packages that include the file with the specified hash. -pack Create a tarball from a package -publish Publishes a package to the registry -root Prints the effective modules directory -store Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store -flagPrefix: -Adding completion: add:Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency -Adding completion: import:Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file -Adding completion: i:Install all dependencies for a project -Adding completion: install:Install all dependencies for a project -Adding completion: it:Runs a pnpm install followed immediately by a pnpm test -Adding completion: install-test:Runs a pnpm install followed immediately by a pnpm test -Adding completion: ln:Connect the local project to another one -Adding completion: link:Connect the local project to another one -Adding completion: prune:Removes extraneous packages -Adding completion: rb:Rebuild a package -Adding completion: rebuild:Rebuild a package -Adding completion: rm:Removes packages from node_modules and from the project's package.json -Adding completion: remove:Removes packages from node_modules and from the project's package.json -Adding completion: unlink:Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link -Adding completion: up:Updates packages to their latest version based on the specified range -Adding completion: update:Updates packages to their latest version based on the specified range -Adding completion: audit:Checks for known security issues with the installed packages -Adding completion: licenses:Check licenses in consumed packages -Adding completion: ls:Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -Adding completion: list:Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -Adding completion: outdated:Check for outdated packages -Adding completion: exec:Executes a shell command in scope of a project -Adding completion: run:Runs a defined package script -Adding completion: start:Runs an arbitrary command specified in the package's "start" property of its "scripts" object -Adding completion: t:Runs a package's "test" script, if one was provided -Adding completion: test:Runs a package's "test" script, if one was provided -Adding completion: cat-file:Prints the contents of a file based on the hash value stored in the index file -Adding completion: cat-index:Prints the index file of a specific package from the store -Adding completion: find-hash:Experimental! Lists the packages that include the file with the specified hash. -Adding completion: pack:Create a tarball from a package -Adding completion: publish:Publishes a package to the registry -Adding completion: root:Prints the effective modules directory -Adding completion: store:Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store -Calling _describe -_describe found some completions - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install -- -Truncated words[*]: pnpm install --, -lastParam: --, lastChar: - -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install -- -completion output: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules ---dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) ---fix-lockfile Fix broken lockfile entries automatically ---force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) ---global-dir Specify a custom directory to store global packages ---help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules ---ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs ---ignore-scripts Don't run lifecycle scripts ---ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. ---lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. ---merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests ---no-hoist Dependencies inside the modules directory will have access only to their listed dependencies ---no-lockfile Don't read or generate a `pnpm-lock.yaml` file ---no-optional `optionalDependencies` are not installed ---offline Trigger an error if any required dependencies are not available in local store ---optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store ---prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation ---prefer-offline Skip staleness checks for cached data, but request missing data from the server ---prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory ---recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" ---resolution-only Re-runs resolution: useful for printing out peer dependency issues ---shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them ---side-effects-cache Use or cache the results of (pre/post)install hooks ---side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk ---stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. ---strict-peer-dependencies Fail on missing or invalid peer dependencies ---use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail ---use-stderr Divert all output to stderr ---use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory ---workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build ---fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm -:4 -last line: :4 -directive: 4 -completions: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules ---dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) ---fix-lockfile Fix broken lockfile entries automatically ---force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) ---global-dir Specify a custom directory to store global packages ---help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules ---ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs ---ignore-scripts Don't run lifecycle scripts ---ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. ---lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. ---merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests ---no-hoist Dependencies inside the modules directory will have access only to their listed dependencies ---no-lockfile Don't read or generate a `pnpm-lock.yaml` file ---no-optional `optionalDependencies` are not installed ---offline Trigger an error if any required dependencies are not available in local store ---optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store ---prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation ---prefer-offline Skip staleness checks for cached data, but request missing data from the server ---prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory ---recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" ---resolution-only Re-runs resolution: useful for printing out peer dependency issues ---shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them ---side-effects-cache Use or cache the results of (pre/post)install hooks ---side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk ---stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. ---strict-peer-dependencies Fail on missing or invalid peer dependencies ---use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail ---use-stderr Divert all output to stderr ---use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory ---workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build ---fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm -flagPrefix: -Adding completion: --aggregate-output:Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules -Adding completion: --dev:Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) -Adding completion: --fix-lockfile:Fix broken lockfile entries automatically -Adding completion: --force:Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) -Adding completion: --global-dir:Specify a custom directory to store global packages -Adding completion: --help:Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules -Adding completion: --ignore-pnpmfile:Disable pnpm hooks defined in .pnpmfile.cjs -Adding completion: --ignore-scripts:Don't run lifecycle scripts -Adding completion: --ignore-workspace:Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. -Adding completion: --lockfile-only:Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. -Adding completion: --merge-git-branch-lockfiles:Merge lockfiles were generated on git branch be installed (instead of node_modules) requests -Adding completion: --no-hoist:Dependencies inside the modules directory will have access only to their listed dependencies -Adding completion: --no-lockfile:Don't read or generate a `pnpm-lock.yaml` file -Adding completion: --no-optional:`optionalDependencies` are not installed -Adding completion: --offline:Trigger an error if any required dependencies are not available in local store -Adding completion: --optimistic-repeat-install:Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store -Adding completion: --prefer-frozen-lockfile:If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation -Adding completion: --prefer-offline:Skip staleness checks for cached data, but request missing data from the server -Adding completion: --prod:Packages in `devDependencies` won't be installed pattern to the root of the modules directory -Adding completion: --recursive:Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" -Adding completion: --resolution-only:Re-runs resolution: useful for printing out peer dependency issues -Adding completion: --shamefully-hoist:All the subdeps will be hoisted into the root node_modules. Your code will have access to them -Adding completion: --side-effects-cache:Use or cache the results of (pre/post)install hooks -Adding completion: --side-effects-cache-readonly:Only use the side effects cache if present, do not create it for new packages are saved on the disk -Adding completion: --stream:Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. -Adding completion: --strict-peer-dependencies:Fail on missing or invalid peer dependencies -Adding completion: --use-running-store-server:Only allows installation with a store server. If no store server is running, installation will fail -Adding completion: --use-stderr:Divert all output to stderr -Adding completion: --use-store-server:Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory -Adding completion: --workspace-root:Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build -Adding completion: --fail-if-no-match:If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm -Calling _describe -_describe found some completions - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install -- -Truncated words[*]: pnpm install --, -lastParam: --, lastChar: - -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install -- -completion output: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules ---dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) ---fix-lockfile Fix broken lockfile entries automatically ---force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) ---global-dir Specify a custom directory to store global packages ---help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules ---ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs ---ignore-scripts Don't run lifecycle scripts ---ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. ---lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. ---merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests ---no-hoist Dependencies inside the modules directory will have access only to their listed dependencies ---no-lockfile Don't read or generate a `pnpm-lock.yaml` file ---no-optional `optionalDependencies` are not installed ---offline Trigger an error if any required dependencies are not available in local store ---optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store ---prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation ---prefer-offline Skip staleness checks for cached data, but request missing data from the server ---prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory ---recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" ---resolution-only Re-runs resolution: useful for printing out peer dependency issues ---shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them ---side-effects-cache Use or cache the results of (pre/post)install hooks ---side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk ---stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. ---strict-peer-dependencies Fail on missing or invalid peer dependencies ---use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail ---use-stderr Divert all output to stderr ---use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory ---workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build ---fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm -:4 -last line: :4 -directive: 4 -completions: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules ---dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) ---fix-lockfile Fix broken lockfile entries automatically ---force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) ---global-dir Specify a custom directory to store global packages ---help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules ---ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs ---ignore-scripts Don't run lifecycle scripts ---ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. ---lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. ---merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests ---no-hoist Dependencies inside the modules directory will have access only to their listed dependencies ---no-lockfile Don't read or generate a `pnpm-lock.yaml` file ---no-optional `optionalDependencies` are not installed ---offline Trigger an error if any required dependencies are not available in local store ---optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store ---prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation ---prefer-offline Skip staleness checks for cached data, but request missing data from the server ---prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory ---recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" ---resolution-only Re-runs resolution: useful for printing out peer dependency issues ---shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them ---side-effects-cache Use or cache the results of (pre/post)install hooks ---side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk ---stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. ---strict-peer-dependencies Fail on missing or invalid peer dependencies ---use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail ---use-stderr Divert all output to stderr ---use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory ---workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build ---fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm -flagPrefix: -Adding completion: --aggregate-output:Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules -Adding completion: --dev:Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) -Adding completion: --fix-lockfile:Fix broken lockfile entries automatically -Adding completion: --force:Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) -Adding completion: --global-dir:Specify a custom directory to store global packages -Adding completion: --help:Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules -Adding completion: --ignore-pnpmfile:Disable pnpm hooks defined in .pnpmfile.cjs -Adding completion: --ignore-scripts:Don't run lifecycle scripts -Adding completion: --ignore-workspace:Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. -Adding completion: --lockfile-only:Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. -Adding completion: --merge-git-branch-lockfiles:Merge lockfiles were generated on git branch be installed (instead of node_modules) requests -Adding completion: --no-hoist:Dependencies inside the modules directory will have access only to their listed dependencies -Adding completion: --no-lockfile:Don't read or generate a `pnpm-lock.yaml` file -Adding completion: --no-optional:`optionalDependencies` are not installed -Adding completion: --offline:Trigger an error if any required dependencies are not available in local store -Adding completion: --optimistic-repeat-install:Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store -Adding completion: --prefer-frozen-lockfile:If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation -Adding completion: --prefer-offline:Skip staleness checks for cached data, but request missing data from the server -Adding completion: --prod:Packages in `devDependencies` won't be installed pattern to the root of the modules directory -Adding completion: --recursive:Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" -Adding completion: --resolution-only:Re-runs resolution: useful for printing out peer dependency issues -Adding completion: --shamefully-hoist:All the subdeps will be hoisted into the root node_modules. Your code will have access to them -Adding completion: --side-effects-cache:Use or cache the results of (pre/post)install hooks -Adding completion: --side-effects-cache-readonly:Only use the side effects cache if present, do not create it for new packages are saved on the disk -Adding completion: --stream:Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. -Adding completion: --strict-peer-dependencies:Fail on missing or invalid peer dependencies -Adding completion: --use-running-store-server:Only allows installation with a store server. If no store server is running, installation will fail -Adding completion: --use-stderr:Divert all output to stderr -Adding completion: --use-store-server:Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory -Adding completion: --workspace-root:Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build -Adding completion: --fail-if-no-match:If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm -Calling _describe -_describe found some completions - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install --d -Truncated words[*]: pnpm install --d, -lastParam: --d, lastChar: d -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --d -completion output: --dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) -:4 -last line: :4 -directive: 4 -completions: --dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) -flagPrefix: -Adding completion: --dev:Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) -Calling _describe -_describe found some completions - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install -- -Truncated words[*]: pnpm install --, -lastParam: --, lastChar: - -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install -- -completion output: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules ---dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) ---fix-lockfile Fix broken lockfile entries automatically ---force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) ---global-dir Specify a custom directory to store global packages ---help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules ---ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs ---ignore-scripts Don't run lifecycle scripts ---ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. ---lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. ---merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests ---no-hoist Dependencies inside the modules directory will have access only to their listed dependencies ---no-lockfile Don't read or generate a `pnpm-lock.yaml` file ---no-optional `optionalDependencies` are not installed ---offline Trigger an error if any required dependencies are not available in local store ---optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store ---prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation ---prefer-offline Skip staleness checks for cached data, but request missing data from the server ---prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory ---recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" ---resolution-only Re-runs resolution: useful for printing out peer dependency issues ---shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them ---side-effects-cache Use or cache the results of (pre/post)install hooks ---side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk ---stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. ---strict-peer-dependencies Fail on missing or invalid peer dependencies ---use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail ---use-stderr Divert all output to stderr ---use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory ---workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build ---fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm -:4 -last line: :4 -directive: 4 -completions: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules ---dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) ---fix-lockfile Fix broken lockfile entries automatically ---force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) ---global-dir Specify a custom directory to store global packages ---help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules ---ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs ---ignore-scripts Don't run lifecycle scripts ---ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. ---lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. ---merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests ---no-hoist Dependencies inside the modules directory will have access only to their listed dependencies ---no-lockfile Don't read or generate a `pnpm-lock.yaml` file ---no-optional `optionalDependencies` are not installed ---offline Trigger an error if any required dependencies are not available in local store ---optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store ---prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation ---prefer-offline Skip staleness checks for cached data, but request missing data from the server ---prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory ---recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" ---resolution-only Re-runs resolution: useful for printing out peer dependency issues ---shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them ---side-effects-cache Use or cache the results of (pre/post)install hooks ---side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk ---stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. ---strict-peer-dependencies Fail on missing or invalid peer dependencies ---use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail ---use-stderr Divert all output to stderr ---use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory ---workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build ---fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm -flagPrefix: -Adding completion: --aggregate-output:Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules -Adding completion: --dev:Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) -Adding completion: --fix-lockfile:Fix broken lockfile entries automatically -Adding completion: --force:Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) -Adding completion: --global-dir:Specify a custom directory to store global packages -Adding completion: --help:Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules -Adding completion: --ignore-pnpmfile:Disable pnpm hooks defined in .pnpmfile.cjs -Adding completion: --ignore-scripts:Don't run lifecycle scripts -Adding completion: --ignore-workspace:Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. -Adding completion: --lockfile-only:Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. -Adding completion: --merge-git-branch-lockfiles:Merge lockfiles were generated on git branch be installed (instead of node_modules) requests -Adding completion: --no-hoist:Dependencies inside the modules directory will have access only to their listed dependencies -Adding completion: --no-lockfile:Don't read or generate a `pnpm-lock.yaml` file -Adding completion: --no-optional:`optionalDependencies` are not installed -Adding completion: --offline:Trigger an error if any required dependencies are not available in local store -Adding completion: --optimistic-repeat-install:Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store -Adding completion: --prefer-frozen-lockfile:If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation -Adding completion: --prefer-offline:Skip staleness checks for cached data, but request missing data from the server -Adding completion: --prod:Packages in `devDependencies` won't be installed pattern to the root of the modules directory -Adding completion: --recursive:Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" -Adding completion: --resolution-only:Re-runs resolution: useful for printing out peer dependency issues -Adding completion: --shamefully-hoist:All the subdeps will be hoisted into the root node_modules. Your code will have access to them -Adding completion: --side-effects-cache:Use or cache the results of (pre/post)install hooks -Adding completion: --side-effects-cache-readonly:Only use the side effects cache if present, do not create it for new packages are saved on the disk -Adding completion: --stream:Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. -Adding completion: --strict-peer-dependencies:Fail on missing or invalid peer dependencies -Adding completion: --use-running-store-server:Only allows installation with a store server. If no store server is running, installation will fail -Adding completion: --use-stderr:Divert all output to stderr -Adding completion: --use-store-server:Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory -Adding completion: --workspace-root:Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build -Adding completion: --fail-if-no-match:If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm -Calling _describe -_describe found some completions - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install -- -Truncated words[*]: pnpm install --, -lastParam: --, lastChar: - -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install -- -completion output: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules ---dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) ---fix-lockfile Fix broken lockfile entries automatically ---force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) ---global-dir Specify a custom directory to store global packages ---help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules ---ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs ---ignore-scripts Don't run lifecycle scripts ---ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. ---lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. ---merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests ---no-hoist Dependencies inside the modules directory will have access only to their listed dependencies ---no-lockfile Don't read or generate a `pnpm-lock.yaml` file ---no-optional `optionalDependencies` are not installed ---offline Trigger an error if any required dependencies are not available in local store ---optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store ---prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation ---prefer-offline Skip staleness checks for cached data, but request missing data from the server ---prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory ---recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" ---resolution-only Re-runs resolution: useful for printing out peer dependency issues ---shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them ---side-effects-cache Use or cache the results of (pre/post)install hooks ---side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk ---stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. ---strict-peer-dependencies Fail on missing or invalid peer dependencies ---use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail ---use-stderr Divert all output to stderr ---use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory ---workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build ---fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm -:4 -last line: :4 -directive: 4 -completions: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules ---dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) ---fix-lockfile Fix broken lockfile entries automatically ---force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) ---global-dir Specify a custom directory to store global packages ---help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules ---ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs ---ignore-scripts Don't run lifecycle scripts ---ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. ---lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. ---merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests ---no-hoist Dependencies inside the modules directory will have access only to their listed dependencies ---no-lockfile Don't read or generate a `pnpm-lock.yaml` file ---no-optional `optionalDependencies` are not installed ---offline Trigger an error if any required dependencies are not available in local store ---optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store ---prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation ---prefer-offline Skip staleness checks for cached data, but request missing data from the server ---prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory ---recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" ---resolution-only Re-runs resolution: useful for printing out peer dependency issues ---shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them ---side-effects-cache Use or cache the results of (pre/post)install hooks ---side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk ---stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. ---strict-peer-dependencies Fail on missing or invalid peer dependencies ---use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail ---use-stderr Divert all output to stderr ---use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory ---workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build ---fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm -flagPrefix: -Adding completion: --aggregate-output:Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules -Adding completion: --dev:Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) -Adding completion: --fix-lockfile:Fix broken lockfile entries automatically -Adding completion: --force:Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) -Adding completion: --global-dir:Specify a custom directory to store global packages -Adding completion: --help:Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules -Adding completion: --ignore-pnpmfile:Disable pnpm hooks defined in .pnpmfile.cjs -Adding completion: --ignore-scripts:Don't run lifecycle scripts -Adding completion: --ignore-workspace:Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. -Adding completion: --lockfile-only:Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. -Adding completion: --merge-git-branch-lockfiles:Merge lockfiles were generated on git branch be installed (instead of node_modules) requests -Adding completion: --no-hoist:Dependencies inside the modules directory will have access only to their listed dependencies -Adding completion: --no-lockfile:Don't read or generate a `pnpm-lock.yaml` file -Adding completion: --no-optional:`optionalDependencies` are not installed -Adding completion: --offline:Trigger an error if any required dependencies are not available in local store -Adding completion: --optimistic-repeat-install:Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store -Adding completion: --prefer-frozen-lockfile:If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation -Adding completion: --prefer-offline:Skip staleness checks for cached data, but request missing data from the server -Adding completion: --prod:Packages in `devDependencies` won't be installed pattern to the root of the modules directory -Adding completion: --recursive:Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" -Adding completion: --resolution-only:Re-runs resolution: useful for printing out peer dependency issues -Adding completion: --shamefully-hoist:All the subdeps will be hoisted into the root node_modules. Your code will have access to them -Adding completion: --side-effects-cache:Use or cache the results of (pre/post)install hooks -Adding completion: --side-effects-cache-readonly:Only use the side effects cache if present, do not create it for new packages are saved on the disk -Adding completion: --stream:Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. -Adding completion: --strict-peer-dependencies:Fail on missing or invalid peer dependencies -Adding completion: --use-running-store-server:Only allows installation with a store server. If no store server is running, installation will fail -Adding completion: --use-stderr:Divert all output to stderr -Adding completion: --use-store-server:Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory -Adding completion: --workspace-root:Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build -Adding completion: --fail-if-no-match:If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm -Calling _describe -_describe found some completions - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm -Truncated words[*]: pnpm , -lastParam: , lastChar: -Adding extra empty parameter -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- '' '' -completion output: add Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency -import Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file -i Install all dependencies for a project -install Install all dependencies for a project -it Runs a pnpm install followed immediately by a pnpm test -install-test Runs a pnpm install followed immediately by a pnpm test -ln Connect the local project to another one -link Connect the local project to another one -prune Removes extraneous packages -rb Rebuild a package -rebuild Rebuild a package -rm Removes packages from node_modules and from the project's package.json -remove Removes packages from node_modules and from the project's package.json -unlink Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link -up Updates packages to their latest version based on the specified range -update Updates packages to their latest version based on the specified range -audit Checks for known security issues with the installed packages -licenses Check licenses in consumed packages -ls Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -list Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -outdated Check for outdated packages -exec Executes a shell command in scope of a project -run Runs a defined package script -start Runs an arbitrary command specified in the package's "start" property of its "scripts" object -t Runs a package's "test" script, if one was provided -test Runs a package's "test" script, if one was provided -cat-file Prints the contents of a file based on the hash value stored in the index file -cat-index Prints the index file of a specific package from the store -find-hash Experimental! Lists the packages that include the file with the specified hash. -pack Create a tarball from a package -publish Publishes a package to the registry -root Prints the effective modules directory -store Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store -:4 -last line: :4 -directive: 4 -completions: add Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency -import Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file -i Install all dependencies for a project -install Install all dependencies for a project -it Runs a pnpm install followed immediately by a pnpm test -install-test Runs a pnpm install followed immediately by a pnpm test -ln Connect the local project to another one -link Connect the local project to another one -prune Removes extraneous packages -rb Rebuild a package -rebuild Rebuild a package -rm Removes packages from node_modules and from the project's package.json -remove Removes packages from node_modules and from the project's package.json -unlink Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link -up Updates packages to their latest version based on the specified range -update Updates packages to their latest version based on the specified range -audit Checks for known security issues with the installed packages -licenses Check licenses in consumed packages -ls Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -list Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -outdated Check for outdated packages -exec Executes a shell command in scope of a project -run Runs a defined package script -start Runs an arbitrary command specified in the package's "start" property of its "scripts" object -t Runs a package's "test" script, if one was provided -test Runs a package's "test" script, if one was provided -cat-file Prints the contents of a file based on the hash value stored in the index file -cat-index Prints the index file of a specific package from the store -find-hash Experimental! Lists the packages that include the file with the specified hash. -pack Create a tarball from a package -publish Publishes a package to the registry -root Prints the effective modules directory -store Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store -flagPrefix: -Adding completion: add:Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency -Adding completion: import:Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file -Adding completion: i:Install all dependencies for a project -Adding completion: install:Install all dependencies for a project -Adding completion: it:Runs a pnpm install followed immediately by a pnpm test -Adding completion: install-test:Runs a pnpm install followed immediately by a pnpm test -Adding completion: ln:Connect the local project to another one -Adding completion: link:Connect the local project to another one -Adding completion: prune:Removes extraneous packages -Adding completion: rb:Rebuild a package -Adding completion: rebuild:Rebuild a package -Adding completion: rm:Removes packages from node_modules and from the project's package.json -Adding completion: remove:Removes packages from node_modules and from the project's package.json -Adding completion: unlink:Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link -Adding completion: up:Updates packages to their latest version based on the specified range -Adding completion: update:Updates packages to their latest version based on the specified range -Adding completion: audit:Checks for known security issues with the installed packages -Adding completion: licenses:Check licenses in consumed packages -Adding completion: ls:Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -Adding completion: list:Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -Adding completion: outdated:Check for outdated packages -Adding completion: exec:Executes a shell command in scope of a project -Adding completion: run:Runs a defined package script -Adding completion: start:Runs an arbitrary command specified in the package's "start" property of its "scripts" object -Adding completion: t:Runs a package's "test" script, if one was provided -Adding completion: test:Runs a package's "test" script, if one was provided -Adding completion: cat-file:Prints the contents of a file based on the hash value stored in the index file -Adding completion: cat-index:Prints the index file of a specific package from the store -Adding completion: find-hash:Experimental! Lists the packages that include the file with the specified hash. -Adding completion: pack:Create a tarball from a package -Adding completion: publish:Publishes a package to the registry -Adding completion: root:Prints the effective modules directory -Adding completion: store:Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store -Calling _describe -_describe found some completions - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm in -Truncated words[*]: pnpm in, -lastParam: in, lastChar: n -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- in -completion output: install Install all dependencies for a project -install-test Runs a pnpm install followed immediately by a pnpm test -:4 -last line: :4 -directive: 4 -completions: install Install all dependencies for a project -install-test Runs a pnpm install followed immediately by a pnpm test -flagPrefix: -Adding completion: install:Install all dependencies for a project -Adding completion: install-test:Runs a pnpm install followed immediately by a pnpm test -Calling _describe -_describe found some completions - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm install-- -Truncated words[*]: pnpm install--, -lastParam: install--, lastChar: - -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install-- -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm install-- -Truncated words[*]: pnpm install--, -lastParam: install--, lastChar: - -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install-- -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm install-- -Truncated words[*]: pnpm install--, -lastParam: install--, lastChar: - -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install-- -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm install--d -Truncated words[*]: pnpm install--d, -lastParam: install--d, lastChar: d -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install--d -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm install--d -Truncated words[*]: pnpm install--d, -lastParam: install--d, lastChar: d -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install--d -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm install--d -Truncated words[*]: pnpm install--d, -lastParam: install--d, lastChar: d -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install--d -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install --d -Truncated words[*]: pnpm install --d, -lastParam: --d, lastChar: d -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --d -completion output: --dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) -:4 -last line: :4 -directive: 4 -completions: --dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) -flagPrefix: -Adding completion: --dev:Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) -Calling _describe -_describe found some completions - -========= starting completion logic ========== -CURRENT: 4, words[*]: pnpm install --dev -Truncated words[*]: pnpm install --dev , -lastParam: , lastChar: -Adding extra empty parameter -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 4, words[*]: pnpm install --dev -Truncated words[*]: pnpm install --dev , -lastParam: , lastChar: -Adding extra empty parameter -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 4, words[*]: pnpm install --dev -Truncated words[*]: pnpm install --dev , -lastParam: , lastChar: -Adding extra empty parameter -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 4, words[*]: pnpm install --dev -Truncated words[*]: pnpm install --dev , -lastParam: , lastChar: -Adding extra empty parameter -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 4, words[*]: pnpm install --dev -Truncated words[*]: pnpm install --dev , -lastParam: , lastChar: -Adding extra empty parameter -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 4, words[*]: pnpm install --dev -Truncated words[*]: pnpm install --dev , -lastParam: , lastChar: -Adding extra empty parameter -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 4, words[*]: pnpm install --dev -Truncated words[*]: pnpm install --dev , -lastParam: , lastChar: -Adding extra empty parameter -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 4, words[*]: pnpm install --dev -Truncated words[*]: pnpm install --dev , -lastParam: , lastChar: -Adding extra empty parameter -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 4, words[*]: pnpm install --dev -Truncated words[*]: pnpm install --dev , -lastParam: , lastChar: -Adding extra empty parameter -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 4, words[*]: pnpm install --dev -Truncated words[*]: pnpm install --dev , -lastParam: , lastChar: -Adding extra empty parameter -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 4, words[*]: pnpm install --dev -Truncated words[*]: pnpm install --dev , -lastParam: , lastChar: -Adding extra empty parameter -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 4, words[*]: pnpm install --dev -Truncated words[*]: pnpm install --dev , -lastParam: , lastChar: -Adding extra empty parameter -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 4, words[*]: pnpm install --dev -Truncated words[*]: pnpm install --dev , -lastParam: , lastChar: -Adding extra empty parameter -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 4, words[*]: pnpm install --dev -Truncated words[*]: pnpm install --dev , -lastParam: , lastChar: -Adding extra empty parameter -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 4, words[*]: pnpm install --dev -Truncated words[*]: pnpm install --dev , -lastParam: , lastChar: -Adding extra empty parameter -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 4, words[*]: pnpm install --dev -Truncated words[*]: pnpm install --dev , -lastParam: , lastChar: -Adding extra empty parameter -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 4, words[*]: pnpm install --dev -Truncated words[*]: pnpm install --dev , -lastParam: , lastChar: -Adding extra empty parameter -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 4, words[*]: pnpm install --dev -Truncated words[*]: pnpm install --dev , -lastParam: , lastChar: -Adding extra empty parameter -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 4, words[*]: pnpm install --dev -Truncated words[*]: pnpm install --dev , -lastParam: , lastChar: -Adding extra empty parameter -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 4, words[*]: pnpm install --dev -Truncated words[*]: pnpm install --dev , -lastParam: , lastChar: -Adding extra empty parameter -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 4, words[*]: pnpm install --dev -Truncated words[*]: pnpm install --dev , -lastParam: , lastChar: -Adding extra empty parameter -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 4, words[*]: pnpm install --dev -Truncated words[*]: pnpm install --dev , -lastParam: , lastChar: -Adding extra empty parameter -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 4, words[*]: pnpm install --dev -Truncated words[*]: pnpm install --dev , -lastParam: , lastChar: -Adding extra empty parameter -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 4, words[*]: pnpm install --dev -Truncated words[*]: pnpm install --dev , -lastParam: , lastChar: -Adding extra empty parameter -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dev '' '' -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm ins -Truncated words[*]: pnpm ins, -lastParam: ins, lastChar: s -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- ins -completion output: install Install all dependencies for a project -install-test Runs a pnpm install followed immediately by a pnpm test -:4 -last line: :4 -directive: 4 -completions: install Install all dependencies for a project -install-test Runs a pnpm install followed immediately by a pnpm test -flagPrefix: -Adding completion: install:Install all dependencies for a project -Adding completion: install-test:Runs a pnpm install followed immediately by a pnpm test -Calling _describe -_describe found some completions - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm install -Truncated words[*]: pnpm install, -lastParam: install, lastChar: l -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install -completion output: install Install all dependencies for a project -install-test Runs a pnpm install followed immediately by a pnpm test -:4 -last line: :4 -directive: 4 -completions: install Install all dependencies for a project -install-test Runs a pnpm install followed immediately by a pnpm test -flagPrefix: -Adding completion: install:Install all dependencies for a project -Adding completion: install-test:Runs a pnpm install followed immediately by a pnpm test -Calling _describe -_describe found some completions - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm install -Truncated words[*]: pnpm install, -lastParam: install, lastChar: l -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install -completion output: install Install all dependencies for a project -install-test Runs a pnpm install followed immediately by a pnpm test -:4 -last line: :4 -directive: 4 -completions: install Install all dependencies for a project -install-test Runs a pnpm install followed immediately by a pnpm test -flagPrefix: -Adding completion: install:Install all dependencies for a project -Adding completion: install-test:Runs a pnpm install followed immediately by a pnpm test -Calling _describe -_describe found some completions - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install --f -Truncated words[*]: pnpm install --f, -lastParam: --f, lastChar: f -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --f -completion output: --fix-lockfile Fix broken lockfile entries automatically ---force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) ---fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm -:4 -last line: :4 -directive: 4 -completions: --fix-lockfile Fix broken lockfile entries automatically ---force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) ---fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm -flagPrefix: -Adding completion: --fix-lockfile:Fix broken lockfile entries automatically -Adding completion: --force:Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) -Adding completion: --fail-if-no-match:If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm -Calling _describe -_describe found some completions - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install --f -Truncated words[*]: pnpm install --f, -lastParam: --f, lastChar: f -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --f -completion output: --fix-lockfile Fix broken lockfile entries automatically ---force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) ---fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm -:4 -last line: :4 -directive: 4 -completions: --fix-lockfile Fix broken lockfile entries automatically ---force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) ---fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm -flagPrefix: -Adding completion: --fix-lockfile:Fix broken lockfile entries automatically -Adding completion: --force:Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) -Adding completion: --fail-if-no-match:If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm -Calling _describe -_describe found some completions - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install --ff -Truncated words[*]: pnpm install --ff, -lastParam: --ff, lastChar: f -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --ff -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install --ff -Truncated words[*]: pnpm install --ff, -lastParam: --ff, lastChar: f -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --ff -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install --ff -Truncated words[*]: pnpm install --ff, -lastParam: --ff, lastChar: f -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --ff -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install --ff -Truncated words[*]: pnpm install --ff, -lastParam: --ff, lastChar: f -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --ff -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install --ff -Truncated words[*]: pnpm install --ff, -lastParam: --ff, lastChar: f -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --ff -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install --ff -Truncated words[*]: pnpm install --ff, -lastParam: --ff, lastChar: f -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --ff -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install --ff -Truncated words[*]: pnpm install --ff, -lastParam: --ff, lastChar: f -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --ff -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install --ff -Truncated words[*]: pnpm install --ff, -lastParam: --ff, lastChar: f -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --ff -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install --ff -Truncated words[*]: pnpm install --ff, -lastParam: --ff, lastChar: f -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --ff -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install --ff -Truncated words[*]: pnpm install --ff, -lastParam: --ff, lastChar: f -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --ff -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install --ff -Truncated words[*]: pnpm install --ff, -lastParam: --ff, lastChar: f -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --ff -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install --ff -Truncated words[*]: pnpm install --ff, -lastParam: --ff, lastChar: f -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --ff -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install --ff -Truncated words[*]: pnpm install --ff, -lastParam: --ff, lastChar: f -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --ff -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install --ff -Truncated words[*]: pnpm install --ff, -lastParam: --ff, lastChar: f -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --ff -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install --ff -Truncated words[*]: pnpm install --ff, -lastParam: --ff, lastChar: f -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --ff -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm iii -Truncated words[*]: pnpm iii, -lastParam: iii, lastChar: i -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- iii -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm iii -Truncated words[*]: pnpm iii, -lastParam: iii, lastChar: i -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- iii -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm iii -Truncated words[*]: pnpm iii, -lastParam: iii, lastChar: i -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- iii -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm iii -Truncated words[*]: pnpm iii, -lastParam: iii, lastChar: i -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- iii -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm iii -Truncated words[*]: pnpm iii, -lastParam: iii, lastChar: i -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- iii -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm iii -Truncated words[*]: pnpm iii, -lastParam: iii, lastChar: i -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- iii -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm iii -Truncated words[*]: pnpm iii, -lastParam: iii, lastChar: i -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- iii -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm iii -Truncated words[*]: pnpm iii, -lastParam: iii, lastChar: i -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- iii -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm iii -Truncated words[*]: pnpm iii, -lastParam: iii, lastChar: i -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- iii -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm iii -Truncated words[*]: pnpm iii, -lastParam: iii, lastChar: i -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- iii -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm iii -Truncated words[*]: pnpm iii, -lastParam: iii, lastChar: i -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- iii -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm iii -Truncated words[*]: pnpm iii, -lastParam: iii, lastChar: i -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- iii -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm iii -Truncated words[*]: pnpm iii, -lastParam: iii, lastChar: i -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- iii -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm iii -Truncated words[*]: pnpm iii, -lastParam: iii, lastChar: i -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- iii -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm iii -Truncated words[*]: pnpm iii, -lastParam: iii, lastChar: i -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- iii -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm iii -Truncated words[*]: pnpm iii, -lastParam: iii, lastChar: i -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- iii -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm iii -Truncated words[*]: pnpm iii, -lastParam: iii, lastChar: i -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- iii -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm iii -Truncated words[*]: pnpm iii, -lastParam: iii, lastChar: i -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- iii -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm -Truncated words[*]: pnpm , -lastParam: , lastChar: -Adding extra empty parameter -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- '' '' -completion output: add Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency -import Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file -i Install all dependencies for a project -install Install all dependencies for a project -it Runs a pnpm install followed immediately by a pnpm test -install-test Runs a pnpm install followed immediately by a pnpm test -ln Connect the local project to another one -link Connect the local project to another one -prune Removes extraneous packages -rb Rebuild a package -rebuild Rebuild a package -rm Removes packages from node_modules and from the project's package.json -remove Removes packages from node_modules and from the project's package.json -unlink Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link -up Updates packages to their latest version based on the specified range -update Updates packages to their latest version based on the specified range -audit Checks for known security issues with the installed packages -licenses Check licenses in consumed packages -ls Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -list Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -outdated Check for outdated packages -exec Executes a shell command in scope of a project -run Runs a defined package script -start Runs an arbitrary command specified in the package's "start" property of its "scripts" object -t Runs a package's "test" script, if one was provided -test Runs a package's "test" script, if one was provided -cat-file Prints the contents of a file based on the hash value stored in the index file -cat-index Prints the index file of a specific package from the store -find-hash Experimental! Lists the packages that include the file with the specified hash. -pack Create a tarball from a package -publish Publishes a package to the registry -root Prints the effective modules directory -store Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store -:4 -last line: :4 -directive: 4 -completions: add Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency -import Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file -i Install all dependencies for a project -install Install all dependencies for a project -it Runs a pnpm install followed immediately by a pnpm test -install-test Runs a pnpm install followed immediately by a pnpm test -ln Connect the local project to another one -link Connect the local project to another one -prune Removes extraneous packages -rb Rebuild a package -rebuild Rebuild a package -rm Removes packages from node_modules and from the project's package.json -remove Removes packages from node_modules and from the project's package.json -unlink Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link -up Updates packages to their latest version based on the specified range -update Updates packages to their latest version based on the specified range -audit Checks for known security issues with the installed packages -licenses Check licenses in consumed packages -ls Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -list Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -outdated Check for outdated packages -exec Executes a shell command in scope of a project -run Runs a defined package script -start Runs an arbitrary command specified in the package's "start" property of its "scripts" object -t Runs a package's "test" script, if one was provided -test Runs a package's "test" script, if one was provided -cat-file Prints the contents of a file based on the hash value stored in the index file -cat-index Prints the index file of a specific package from the store -find-hash Experimental! Lists the packages that include the file with the specified hash. -pack Create a tarball from a package -publish Publishes a package to the registry -root Prints the effective modules directory -store Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store -flagPrefix: -Adding completion: add:Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency -Adding completion: import:Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file -Adding completion: i:Install all dependencies for a project -Adding completion: install:Install all dependencies for a project -Adding completion: it:Runs a pnpm install followed immediately by a pnpm test -Adding completion: install-test:Runs a pnpm install followed immediately by a pnpm test -Adding completion: ln:Connect the local project to another one -Adding completion: link:Connect the local project to another one -Adding completion: prune:Removes extraneous packages -Adding completion: rb:Rebuild a package -Adding completion: rebuild:Rebuild a package -Adding completion: rm:Removes packages from node_modules and from the project's package.json -Adding completion: remove:Removes packages from node_modules and from the project's package.json -Adding completion: unlink:Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link -Adding completion: up:Updates packages to their latest version based on the specified range -Adding completion: update:Updates packages to their latest version based on the specified range -Adding completion: audit:Checks for known security issues with the installed packages -Adding completion: licenses:Check licenses in consumed packages -Adding completion: ls:Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -Adding completion: list:Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -Adding completion: outdated:Check for outdated packages -Adding completion: exec:Executes a shell command in scope of a project -Adding completion: run:Runs a defined package script -Adding completion: start:Runs an arbitrary command specified in the package's "start" property of its "scripts" object -Adding completion: t:Runs a package's "test" script, if one was provided -Adding completion: test:Runs a package's "test" script, if one was provided -Adding completion: cat-file:Prints the contents of a file based on the hash value stored in the index file -Adding completion: cat-index:Prints the index file of a specific package from the store -Adding completion: find-hash:Experimental! Lists the packages that include the file with the specified hash. -Adding completion: pack:Create a tarball from a package -Adding completion: publish:Publishes a package to the registry -Adding completion: root:Prints the effective modules directory -Adding completion: store:Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store -Calling _describe -_describe found some completions - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm -Truncated words[*]: pnpm , -lastParam: , lastChar: -Adding extra empty parameter -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- '' '' -completion output: add Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency -import Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file -i Install all dependencies for a project -install Install all dependencies for a project -it Runs a pnpm install followed immediately by a pnpm test -install-test Runs a pnpm install followed immediately by a pnpm test -ln Connect the local project to another one -link Connect the local project to another one -prune Removes extraneous packages -rb Rebuild a package -rebuild Rebuild a package -rm Removes packages from node_modules and from the project's package.json -remove Removes packages from node_modules and from the project's package.json -unlink Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link -up Updates packages to their latest version based on the specified range -update Updates packages to their latest version based on the specified range -audit Checks for known security issues with the installed packages -licenses Check licenses in consumed packages -ls Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -list Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -outdated Check for outdated packages -exec Executes a shell command in scope of a project -run Runs a defined package script -start Runs an arbitrary command specified in the package's "start" property of its "scripts" object -t Runs a package's "test" script, if one was provided -test Runs a package's "test" script, if one was provided -cat-file Prints the contents of a file based on the hash value stored in the index file -cat-index Prints the index file of a specific package from the store -find-hash Experimental! Lists the packages that include the file with the specified hash. -pack Create a tarball from a package -publish Publishes a package to the registry -root Prints the effective modules directory -store Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store -:4 -last line: :4 -directive: 4 -completions: add Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency -import Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file -i Install all dependencies for a project -install Install all dependencies for a project -it Runs a pnpm install followed immediately by a pnpm test -install-test Runs a pnpm install followed immediately by a pnpm test -ln Connect the local project to another one -link Connect the local project to another one -prune Removes extraneous packages -rb Rebuild a package -rebuild Rebuild a package -rm Removes packages from node_modules and from the project's package.json -remove Removes packages from node_modules and from the project's package.json -unlink Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link -up Updates packages to their latest version based on the specified range -update Updates packages to their latest version based on the specified range -audit Checks for known security issues with the installed packages -licenses Check licenses in consumed packages -ls Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -list Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -outdated Check for outdated packages -exec Executes a shell command in scope of a project -run Runs a defined package script -start Runs an arbitrary command specified in the package's "start" property of its "scripts" object -t Runs a package's "test" script, if one was provided -test Runs a package's "test" script, if one was provided -cat-file Prints the contents of a file based on the hash value stored in the index file -cat-index Prints the index file of a specific package from the store -find-hash Experimental! Lists the packages that include the file with the specified hash. -pack Create a tarball from a package -publish Publishes a package to the registry -root Prints the effective modules directory -store Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store -flagPrefix: -Adding completion: add:Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency -Adding completion: import:Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file -Adding completion: i:Install all dependencies for a project -Adding completion: install:Install all dependencies for a project -Adding completion: it:Runs a pnpm install followed immediately by a pnpm test -Adding completion: install-test:Runs a pnpm install followed immediately by a pnpm test -Adding completion: ln:Connect the local project to another one -Adding completion: link:Connect the local project to another one -Adding completion: prune:Removes extraneous packages -Adding completion: rb:Rebuild a package -Adding completion: rebuild:Rebuild a package -Adding completion: rm:Removes packages from node_modules and from the project's package.json -Adding completion: remove:Removes packages from node_modules and from the project's package.json -Adding completion: unlink:Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link -Adding completion: up:Updates packages to their latest version based on the specified range -Adding completion: update:Updates packages to their latest version based on the specified range -Adding completion: audit:Checks for known security issues with the installed packages -Adding completion: licenses:Check licenses in consumed packages -Adding completion: ls:Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -Adding completion: list:Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -Adding completion: outdated:Check for outdated packages -Adding completion: exec:Executes a shell command in scope of a project -Adding completion: run:Runs a defined package script -Adding completion: start:Runs an arbitrary command specified in the package's "start" property of its "scripts" object -Adding completion: t:Runs a package's "test" script, if one was provided -Adding completion: test:Runs a package's "test" script, if one was provided -Adding completion: cat-file:Prints the contents of a file based on the hash value stored in the index file -Adding completion: cat-index:Prints the index file of a specific package from the store -Adding completion: find-hash:Experimental! Lists the packages that include the file with the specified hash. -Adding completion: pack:Create a tarball from a package -Adding completion: publish:Publishes a package to the registry -Adding completion: root:Prints the effective modules directory -Adding completion: store:Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store -Calling _describe -_describe found some completions - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm in -Truncated words[*]: pnpm in, -lastParam: in, lastChar: n -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- in -completion output: install Install all dependencies for a project -install-test Runs a pnpm install followed immediately by a pnpm test -:4 -last line: :4 -directive: 4 -completions: install Install all dependencies for a project -install-test Runs a pnpm install followed immediately by a pnpm test -flagPrefix: -Adding completion: install:Install all dependencies for a project -Adding completion: install-test:Runs a pnpm install followed immediately by a pnpm test -Calling _describe -_describe found some completions - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install -- -Truncated words[*]: pnpm install --, -lastParam: --, lastChar: - -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install -- -completion output: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules ---dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) ---fix-lockfile Fix broken lockfile entries automatically ---force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) ---global-dir Specify a custom directory to store global packages ---help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules ---ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs ---ignore-scripts Don't run lifecycle scripts ---ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. ---lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. ---merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests ---no-hoist Dependencies inside the modules directory will have access only to their listed dependencies ---no-lockfile Don't read or generate a `pnpm-lock.yaml` file ---no-optional `optionalDependencies` are not installed ---offline Trigger an error if any required dependencies are not available in local store ---optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store ---prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation ---prefer-offline Skip staleness checks for cached data, but request missing data from the server ---prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory ---recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" ---resolution-only Re-runs resolution: useful for printing out peer dependency issues ---shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them ---side-effects-cache Use or cache the results of (pre/post)install hooks ---side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk ---stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. ---strict-peer-dependencies Fail on missing or invalid peer dependencies ---use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail ---use-stderr Divert all output to stderr ---use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory ---workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build ---fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm -:4 -last line: :4 -directive: 4 -completions: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules ---dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) ---fix-lockfile Fix broken lockfile entries automatically ---force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) ---global-dir Specify a custom directory to store global packages ---help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules ---ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs ---ignore-scripts Don't run lifecycle scripts ---ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. ---lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. ---merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests ---no-hoist Dependencies inside the modules directory will have access only to their listed dependencies ---no-lockfile Don't read or generate a `pnpm-lock.yaml` file ---no-optional `optionalDependencies` are not installed ---offline Trigger an error if any required dependencies are not available in local store ---optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store ---prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation ---prefer-offline Skip staleness checks for cached data, but request missing data from the server ---prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory ---recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" ---resolution-only Re-runs resolution: useful for printing out peer dependency issues ---shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them ---side-effects-cache Use or cache the results of (pre/post)install hooks ---side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk ---stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. ---strict-peer-dependencies Fail on missing or invalid peer dependencies ---use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail ---use-stderr Divert all output to stderr ---use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory ---workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build ---fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm -flagPrefix: -Adding completion: --aggregate-output:Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules -Adding completion: --dev:Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) -Adding completion: --fix-lockfile:Fix broken lockfile entries automatically -Adding completion: --force:Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) -Adding completion: --global-dir:Specify a custom directory to store global packages -Adding completion: --help:Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules -Adding completion: --ignore-pnpmfile:Disable pnpm hooks defined in .pnpmfile.cjs -Adding completion: --ignore-scripts:Don't run lifecycle scripts -Adding completion: --ignore-workspace:Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. -Adding completion: --lockfile-only:Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. -Adding completion: --merge-git-branch-lockfiles:Merge lockfiles were generated on git branch be installed (instead of node_modules) requests -Adding completion: --no-hoist:Dependencies inside the modules directory will have access only to their listed dependencies -Adding completion: --no-lockfile:Don't read or generate a `pnpm-lock.yaml` file -Adding completion: --no-optional:`optionalDependencies` are not installed -Adding completion: --offline:Trigger an error if any required dependencies are not available in local store -Adding completion: --optimistic-repeat-install:Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store -Adding completion: --prefer-frozen-lockfile:If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation -Adding completion: --prefer-offline:Skip staleness checks for cached data, but request missing data from the server -Adding completion: --prod:Packages in `devDependencies` won't be installed pattern to the root of the modules directory -Adding completion: --recursive:Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" -Adding completion: --resolution-only:Re-runs resolution: useful for printing out peer dependency issues -Adding completion: --shamefully-hoist:All the subdeps will be hoisted into the root node_modules. Your code will have access to them -Adding completion: --side-effects-cache:Use or cache the results of (pre/post)install hooks -Adding completion: --side-effects-cache-readonly:Only use the side effects cache if present, do not create it for new packages are saved on the disk -Adding completion: --stream:Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. -Adding completion: --strict-peer-dependencies:Fail on missing or invalid peer dependencies -Adding completion: --use-running-store-server:Only allows installation with a store server. If no store server is running, installation will fail -Adding completion: --use-stderr:Divert all output to stderr -Adding completion: --use-store-server:Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory -Adding completion: --workspace-root:Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build -Adding completion: --fail-if-no-match:If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm -Calling _describe -_describe found some completions - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install -- -Truncated words[*]: pnpm install --, -lastParam: --, lastChar: - -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install -- -completion output: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules ---dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) ---fix-lockfile Fix broken lockfile entries automatically ---force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) ---global-dir Specify a custom directory to store global packages ---help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules ---ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs ---ignore-scripts Don't run lifecycle scripts ---ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. ---lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. ---merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests ---no-hoist Dependencies inside the modules directory will have access only to their listed dependencies ---no-lockfile Don't read or generate a `pnpm-lock.yaml` file ---no-optional `optionalDependencies` are not installed ---offline Trigger an error if any required dependencies are not available in local store ---optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store ---prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation ---prefer-offline Skip staleness checks for cached data, but request missing data from the server ---prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory ---recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" ---resolution-only Re-runs resolution: useful for printing out peer dependency issues ---shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them ---side-effects-cache Use or cache the results of (pre/post)install hooks ---side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk ---stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. ---strict-peer-dependencies Fail on missing or invalid peer dependencies ---use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail ---use-stderr Divert all output to stderr ---use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory ---workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build ---fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm -:4 -last line: :4 -directive: 4 -completions: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules ---dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) ---fix-lockfile Fix broken lockfile entries automatically ---force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) ---global-dir Specify a custom directory to store global packages ---help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules ---ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs ---ignore-scripts Don't run lifecycle scripts ---ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. ---lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. ---merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests ---no-hoist Dependencies inside the modules directory will have access only to their listed dependencies ---no-lockfile Don't read or generate a `pnpm-lock.yaml` file ---no-optional `optionalDependencies` are not installed ---offline Trigger an error if any required dependencies are not available in local store ---optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store ---prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation ---prefer-offline Skip staleness checks for cached data, but request missing data from the server ---prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory ---recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" ---resolution-only Re-runs resolution: useful for printing out peer dependency issues ---shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them ---side-effects-cache Use or cache the results of (pre/post)install hooks ---side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk ---stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. ---strict-peer-dependencies Fail on missing or invalid peer dependencies ---use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail ---use-stderr Divert all output to stderr ---use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory ---workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build ---fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm -flagPrefix: -Adding completion: --aggregate-output:Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules -Adding completion: --dev:Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) -Adding completion: --fix-lockfile:Fix broken lockfile entries automatically -Adding completion: --force:Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) -Adding completion: --global-dir:Specify a custom directory to store global packages -Adding completion: --help:Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules -Adding completion: --ignore-pnpmfile:Disable pnpm hooks defined in .pnpmfile.cjs -Adding completion: --ignore-scripts:Don't run lifecycle scripts -Adding completion: --ignore-workspace:Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. -Adding completion: --lockfile-only:Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. -Adding completion: --merge-git-branch-lockfiles:Merge lockfiles were generated on git branch be installed (instead of node_modules) requests -Adding completion: --no-hoist:Dependencies inside the modules directory will have access only to their listed dependencies -Adding completion: --no-lockfile:Don't read or generate a `pnpm-lock.yaml` file -Adding completion: --no-optional:`optionalDependencies` are not installed -Adding completion: --offline:Trigger an error if any required dependencies are not available in local store -Adding completion: --optimistic-repeat-install:Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store -Adding completion: --prefer-frozen-lockfile:If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation -Adding completion: --prefer-offline:Skip staleness checks for cached data, but request missing data from the server -Adding completion: --prod:Packages in `devDependencies` won't be installed pattern to the root of the modules directory -Adding completion: --recursive:Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" -Adding completion: --resolution-only:Re-runs resolution: useful for printing out peer dependency issues -Adding completion: --shamefully-hoist:All the subdeps will be hoisted into the root node_modules. Your code will have access to them -Adding completion: --side-effects-cache:Use or cache the results of (pre/post)install hooks -Adding completion: --side-effects-cache-readonly:Only use the side effects cache if present, do not create it for new packages are saved on the disk -Adding completion: --stream:Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. -Adding completion: --strict-peer-dependencies:Fail on missing or invalid peer dependencies -Adding completion: --use-running-store-server:Only allows installation with a store server. If no store server is running, installation will fail -Adding completion: --use-stderr:Divert all output to stderr -Adding completion: --use-store-server:Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory -Adding completion: --workspace-root:Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build -Adding completion: --fail-if-no-match:If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm -Calling _describe -_describe found some completions - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install --dd -Truncated words[*]: pnpm install --dd, -lastParam: --dd, lastChar: d -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dd -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install --dd -Truncated words[*]: pnpm install --dd, -lastParam: --dd, lastChar: d -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dd -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install --dd -Truncated words[*]: pnpm install --dd, -lastParam: --dd, lastChar: d -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dd -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install --dd -Truncated words[*]: pnpm install --dd, -lastParam: --dd, lastChar: d -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dd -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install --dd -Truncated words[*]: pnpm install --dd, -lastParam: --dd, lastChar: d -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dd -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install --dd -Truncated words[*]: pnpm install --dd, -lastParam: --dd, lastChar: d -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dd -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install --dd -Truncated words[*]: pnpm install --dd, -lastParam: --dd, lastChar: d -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dd -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install --dd -Truncated words[*]: pnpm install --dd, -lastParam: --dd, lastChar: d -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dd -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install --dd -Truncated words[*]: pnpm install --dd, -lastParam: --dd, lastChar: d -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dd -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install --dd -Truncated words[*]: pnpm install --dd, -lastParam: --dd, lastChar: d -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dd -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install --dd -Truncated words[*]: pnpm install --dd, -lastParam: --dd, lastChar: d -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dd -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install --dd -Truncated words[*]: pnpm install --dd, -lastParam: --dd, lastChar: d -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dd -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install --dd -Truncated words[*]: pnpm install --dd, -lastParam: --dd, lastChar: d -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dd -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install --dd -Truncated words[*]: pnpm install --dd, -lastParam: --dd, lastChar: d -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dd -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install --dd -Truncated words[*]: pnpm install --dd, -lastParam: --dd, lastChar: d -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install --dd -completion output: :4 -last line: :4 -directive: 4 -completions: -flagPrefix: -Calling _describe -_describe did not find completions. -Checking if we should do file completion. -deactivating file completion - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm -Truncated words[*]: pnpm , -lastParam: , lastChar: -Adding extra empty parameter -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- '' '' -completion output: add Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency -import Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file -i Install all dependencies for a project -install Install all dependencies for a project -it Runs a pnpm install followed immediately by a pnpm test -install-test Runs a pnpm install followed immediately by a pnpm test -ln Connect the local project to another one -link Connect the local project to another one -prune Removes extraneous packages -rb Rebuild a package -rebuild Rebuild a package -rm Removes packages from node_modules and from the project's package.json -remove Removes packages from node_modules and from the project's package.json -unlink Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link -up Updates packages to their latest version based on the specified range -update Updates packages to their latest version based on the specified range -audit Checks for known security issues with the installed packages -licenses Check licenses in consumed packages -ls Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -list Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -outdated Check for outdated packages -exec Executes a shell command in scope of a project -run Runs a defined package script -start Runs an arbitrary command specified in the package's "start" property of its "scripts" object -t Runs a package's "test" script, if one was provided -test Runs a package's "test" script, if one was provided -cat-file Prints the contents of a file based on the hash value stored in the index file -cat-index Prints the index file of a specific package from the store -find-hash Experimental! Lists the packages that include the file with the specified hash. -pack Create a tarball from a package -publish Publishes a package to the registry -root Prints the effective modules directory -store Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store -:4 -last line: :4 -directive: 4 -completions: add Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency -import Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file -i Install all dependencies for a project -install Install all dependencies for a project -it Runs a pnpm install followed immediately by a pnpm test -install-test Runs a pnpm install followed immediately by a pnpm test -ln Connect the local project to another one -link Connect the local project to another one -prune Removes extraneous packages -rb Rebuild a package -rebuild Rebuild a package -rm Removes packages from node_modules and from the project's package.json -remove Removes packages from node_modules and from the project's package.json -unlink Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link -up Updates packages to their latest version based on the specified range -update Updates packages to their latest version based on the specified range -audit Checks for known security issues with the installed packages -licenses Check licenses in consumed packages -ls Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -list Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -outdated Check for outdated packages -exec Executes a shell command in scope of a project -run Runs a defined package script -start Runs an arbitrary command specified in the package's "start" property of its "scripts" object -t Runs a package's "test" script, if one was provided -test Runs a package's "test" script, if one was provided -cat-file Prints the contents of a file based on the hash value stored in the index file -cat-index Prints the index file of a specific package from the store -find-hash Experimental! Lists the packages that include the file with the specified hash. -pack Create a tarball from a package -publish Publishes a package to the registry -root Prints the effective modules directory -store Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store -flagPrefix: -Adding completion: add:Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency -Adding completion: import:Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file -Adding completion: i:Install all dependencies for a project -Adding completion: install:Install all dependencies for a project -Adding completion: it:Runs a pnpm install followed immediately by a pnpm test -Adding completion: install-test:Runs a pnpm install followed immediately by a pnpm test -Adding completion: ln:Connect the local project to another one -Adding completion: link:Connect the local project to another one -Adding completion: prune:Removes extraneous packages -Adding completion: rb:Rebuild a package -Adding completion: rebuild:Rebuild a package -Adding completion: rm:Removes packages from node_modules and from the project's package.json -Adding completion: remove:Removes packages from node_modules and from the project's package.json -Adding completion: unlink:Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link -Adding completion: up:Updates packages to their latest version based on the specified range -Adding completion: update:Updates packages to their latest version based on the specified range -Adding completion: audit:Checks for known security issues with the installed packages -Adding completion: licenses:Check licenses in consumed packages -Adding completion: ls:Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -Adding completion: list:Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -Adding completion: outdated:Check for outdated packages -Adding completion: exec:Executes a shell command in scope of a project -Adding completion: run:Runs a defined package script -Adding completion: start:Runs an arbitrary command specified in the package's "start" property of its "scripts" object -Adding completion: t:Runs a package's "test" script, if one was provided -Adding completion: test:Runs a package's "test" script, if one was provided -Adding completion: cat-file:Prints the contents of a file based on the hash value stored in the index file -Adding completion: cat-index:Prints the index file of a specific package from the store -Adding completion: find-hash:Experimental! Lists the packages that include the file with the specified hash. -Adding completion: pack:Create a tarball from a package -Adding completion: publish:Publishes a package to the registry -Adding completion: root:Prints the effective modules directory -Adding completion: store:Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store -Calling _describe -_describe found some completions - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm ins -Truncated words[*]: pnpm ins, -lastParam: ins, lastChar: s -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- ins -completion output: install Install all dependencies for a project -install-test Runs a pnpm install followed immediately by a pnpm test -:4 -last line: :4 -directive: 4 -completions: install Install all dependencies for a project -install-test Runs a pnpm install followed immediately by a pnpm test -flagPrefix: -Adding completion: install:Install all dependencies for a project -Adding completion: install-test:Runs a pnpm install followed immediately by a pnpm test -Calling _describe -_describe found some completions - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install -- -Truncated words[*]: pnpm install --, -lastParam: --, lastChar: - -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install -- -completion output: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules ---dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) ---fix-lockfile Fix broken lockfile entries automatically ---force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) ---global-dir Specify a custom directory to store global packages ---help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules ---ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs ---ignore-scripts Don't run lifecycle scripts ---ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. ---lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. ---merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests ---no-hoist Dependencies inside the modules directory will have access only to their listed dependencies ---no-lockfile Don't read or generate a `pnpm-lock.yaml` file ---no-optional `optionalDependencies` are not installed ---offline Trigger an error if any required dependencies are not available in local store ---optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store ---prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation ---prefer-offline Skip staleness checks for cached data, but request missing data from the server ---prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory ---recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" ---resolution-only Re-runs resolution: useful for printing out peer dependency issues ---shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them ---side-effects-cache Use or cache the results of (pre/post)install hooks ---side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk ---stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. ---strict-peer-dependencies Fail on missing or invalid peer dependencies ---use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail ---use-stderr Divert all output to stderr ---use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory ---workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build ---fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm -:4 -last line: :4 -directive: 4 -completions: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules ---dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) ---fix-lockfile Fix broken lockfile entries automatically ---force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) ---global-dir Specify a custom directory to store global packages ---help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules ---ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs ---ignore-scripts Don't run lifecycle scripts ---ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. ---lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. ---merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests ---no-hoist Dependencies inside the modules directory will have access only to their listed dependencies ---no-lockfile Don't read or generate a `pnpm-lock.yaml` file ---no-optional `optionalDependencies` are not installed ---offline Trigger an error if any required dependencies are not available in local store ---optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store ---prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation ---prefer-offline Skip staleness checks for cached data, but request missing data from the server ---prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory ---recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" ---resolution-only Re-runs resolution: useful for printing out peer dependency issues ---shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them ---side-effects-cache Use or cache the results of (pre/post)install hooks ---side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk ---stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. ---strict-peer-dependencies Fail on missing or invalid peer dependencies ---use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail ---use-stderr Divert all output to stderr ---use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory ---workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build ---fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm -flagPrefix: -Adding completion: --aggregate-output:Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules -Adding completion: --dev:Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) -Adding completion: --fix-lockfile:Fix broken lockfile entries automatically -Adding completion: --force:Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) -Adding completion: --global-dir:Specify a custom directory to store global packages -Adding completion: --help:Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules -Adding completion: --ignore-pnpmfile:Disable pnpm hooks defined in .pnpmfile.cjs -Adding completion: --ignore-scripts:Don't run lifecycle scripts -Adding completion: --ignore-workspace:Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. -Adding completion: --lockfile-only:Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. -Adding completion: --merge-git-branch-lockfiles:Merge lockfiles were generated on git branch be installed (instead of node_modules) requests -Adding completion: --no-hoist:Dependencies inside the modules directory will have access only to their listed dependencies -Adding completion: --no-lockfile:Don't read or generate a `pnpm-lock.yaml` file -Adding completion: --no-optional:`optionalDependencies` are not installed -Adding completion: --offline:Trigger an error if any required dependencies are not available in local store -Adding completion: --optimistic-repeat-install:Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store -Adding completion: --prefer-frozen-lockfile:If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation -Adding completion: --prefer-offline:Skip staleness checks for cached data, but request missing data from the server -Adding completion: --prod:Packages in `devDependencies` won't be installed pattern to the root of the modules directory -Adding completion: --recursive:Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" -Adding completion: --resolution-only:Re-runs resolution: useful for printing out peer dependency issues -Adding completion: --shamefully-hoist:All the subdeps will be hoisted into the root node_modules. Your code will have access to them -Adding completion: --side-effects-cache:Use or cache the results of (pre/post)install hooks -Adding completion: --side-effects-cache-readonly:Only use the side effects cache if present, do not create it for new packages are saved on the disk -Adding completion: --stream:Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. -Adding completion: --strict-peer-dependencies:Fail on missing or invalid peer dependencies -Adding completion: --use-running-store-server:Only allows installation with a store server. If no store server is running, installation will fail -Adding completion: --use-stderr:Divert all output to stderr -Adding completion: --use-store-server:Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory -Adding completion: --workspace-root:Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build -Adding completion: --fail-if-no-match:If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm -Calling _describe -_describe found some completions - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install -- -Truncated words[*]: pnpm install --, -lastParam: --, lastChar: - -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install -- -completion output: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules ---dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) ---fix-lockfile Fix broken lockfile entries automatically ---force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) ---global-dir Specify a custom directory to store global packages ---help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules ---ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs ---ignore-scripts Don't run lifecycle scripts ---ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. ---lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. ---merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests ---no-hoist Dependencies inside the modules directory will have access only to their listed dependencies ---no-lockfile Don't read or generate a `pnpm-lock.yaml` file ---no-optional `optionalDependencies` are not installed ---offline Trigger an error if any required dependencies are not available in local store ---optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store ---prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation ---prefer-offline Skip staleness checks for cached data, but request missing data from the server ---prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory ---recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" ---resolution-only Re-runs resolution: useful for printing out peer dependency issues ---shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them ---side-effects-cache Use or cache the results of (pre/post)install hooks ---side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk ---stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. ---strict-peer-dependencies Fail on missing or invalid peer dependencies ---use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail ---use-stderr Divert all output to stderr ---use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory ---workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build ---fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm -:4 -last line: :4 -directive: 4 -completions: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules ---dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) ---fix-lockfile Fix broken lockfile entries automatically ---force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) ---global-dir Specify a custom directory to store global packages ---help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules ---ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs ---ignore-scripts Don't run lifecycle scripts ---ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. ---lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. ---merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests ---no-hoist Dependencies inside the modules directory will have access only to their listed dependencies ---no-lockfile Don't read or generate a `pnpm-lock.yaml` file ---no-optional `optionalDependencies` are not installed ---offline Trigger an error if any required dependencies are not available in local store ---optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store ---prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation ---prefer-offline Skip staleness checks for cached data, but request missing data from the server ---prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory ---recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" ---resolution-only Re-runs resolution: useful for printing out peer dependency issues ---shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them ---side-effects-cache Use or cache the results of (pre/post)install hooks ---side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk ---stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. ---strict-peer-dependencies Fail on missing or invalid peer dependencies ---use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail ---use-stderr Divert all output to stderr ---use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory ---workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build ---fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm -flagPrefix: -Adding completion: --aggregate-output:Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules -Adding completion: --dev:Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) -Adding completion: --fix-lockfile:Fix broken lockfile entries automatically -Adding completion: --force:Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) -Adding completion: --global-dir:Specify a custom directory to store global packages -Adding completion: --help:Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules -Adding completion: --ignore-pnpmfile:Disable pnpm hooks defined in .pnpmfile.cjs -Adding completion: --ignore-scripts:Don't run lifecycle scripts -Adding completion: --ignore-workspace:Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. -Adding completion: --lockfile-only:Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. -Adding completion: --merge-git-branch-lockfiles:Merge lockfiles were generated on git branch be installed (instead of node_modules) requests -Adding completion: --no-hoist:Dependencies inside the modules directory will have access only to their listed dependencies -Adding completion: --no-lockfile:Don't read or generate a `pnpm-lock.yaml` file -Adding completion: --no-optional:`optionalDependencies` are not installed -Adding completion: --offline:Trigger an error if any required dependencies are not available in local store -Adding completion: --optimistic-repeat-install:Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store -Adding completion: --prefer-frozen-lockfile:If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation -Adding completion: --prefer-offline:Skip staleness checks for cached data, but request missing data from the server -Adding completion: --prod:Packages in `devDependencies` won't be installed pattern to the root of the modules directory -Adding completion: --recursive:Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" -Adding completion: --resolution-only:Re-runs resolution: useful for printing out peer dependency issues -Adding completion: --shamefully-hoist:All the subdeps will be hoisted into the root node_modules. Your code will have access to them -Adding completion: --side-effects-cache:Use or cache the results of (pre/post)install hooks -Adding completion: --side-effects-cache-readonly:Only use the side effects cache if present, do not create it for new packages are saved on the disk -Adding completion: --stream:Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. -Adding completion: --strict-peer-dependencies:Fail on missing or invalid peer dependencies -Adding completion: --use-running-store-server:Only allows installation with a store server. If no store server is running, installation will fail -Adding completion: --use-stderr:Divert all output to stderr -Adding completion: --use-store-server:Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory -Adding completion: --workspace-root:Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build -Adding completion: --fail-if-no-match:If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm -Calling _describe -_describe found some completions - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm ins -Truncated words[*]: pnpm ins, -lastParam: ins, lastChar: s -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- ins -completion output: install Install all dependencies for a project -install-test Runs a pnpm install followed immediately by a pnpm test -:4 -last line: :4 -directive: 4 -completions: install Install all dependencies for a project -install-test Runs a pnpm install followed immediately by a pnpm test -flagPrefix: -Adding completion: install:Install all dependencies for a project -Adding completion: install-test:Runs a pnpm install followed immediately by a pnpm test -Calling _describe -_describe found some completions - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install -- -Truncated words[*]: pnpm install --, -lastParam: --, lastChar: - -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install -- -completion output: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules ---dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) ---fix-lockfile Fix broken lockfile entries automatically ---force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) ---global-dir Specify a custom directory to store global packages ---help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules ---ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs ---ignore-scripts Don't run lifecycle scripts ---ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. ---lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. ---merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests ---no-hoist Dependencies inside the modules directory will have access only to their listed dependencies ---no-lockfile Don't read or generate a `pnpm-lock.yaml` file ---no-optional `optionalDependencies` are not installed ---offline Trigger an error if any required dependencies are not available in local store ---optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store ---prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation ---prefer-offline Skip staleness checks for cached data, but request missing data from the server ---prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory ---recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" ---resolution-only Re-runs resolution: useful for printing out peer dependency issues ---shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them ---side-effects-cache Use or cache the results of (pre/post)install hooks ---side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk ---stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. ---strict-peer-dependencies Fail on missing or invalid peer dependencies ---use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail ---use-stderr Divert all output to stderr ---use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory ---workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build ---fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm -:4 -last line: :4 -directive: 4 -completions: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules ---dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) ---fix-lockfile Fix broken lockfile entries automatically ---force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) ---global-dir Specify a custom directory to store global packages ---help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules ---ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs ---ignore-scripts Don't run lifecycle scripts ---ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. ---lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. ---merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests ---no-hoist Dependencies inside the modules directory will have access only to their listed dependencies ---no-lockfile Don't read or generate a `pnpm-lock.yaml` file ---no-optional `optionalDependencies` are not installed ---offline Trigger an error if any required dependencies are not available in local store ---optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store ---prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation ---prefer-offline Skip staleness checks for cached data, but request missing data from the server ---prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory ---recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" ---resolution-only Re-runs resolution: useful for printing out peer dependency issues ---shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them ---side-effects-cache Use or cache the results of (pre/post)install hooks ---side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk ---stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. ---strict-peer-dependencies Fail on missing or invalid peer dependencies ---use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail ---use-stderr Divert all output to stderr ---use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory ---workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build ---fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm -flagPrefix: -Adding completion: --aggregate-output:Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules -Adding completion: --dev:Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) -Adding completion: --fix-lockfile:Fix broken lockfile entries automatically -Adding completion: --force:Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) -Adding completion: --global-dir:Specify a custom directory to store global packages -Adding completion: --help:Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules -Adding completion: --ignore-pnpmfile:Disable pnpm hooks defined in .pnpmfile.cjs -Adding completion: --ignore-scripts:Don't run lifecycle scripts -Adding completion: --ignore-workspace:Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. -Adding completion: --lockfile-only:Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. -Adding completion: --merge-git-branch-lockfiles:Merge lockfiles were generated on git branch be installed (instead of node_modules) requests -Adding completion: --no-hoist:Dependencies inside the modules directory will have access only to their listed dependencies -Adding completion: --no-lockfile:Don't read or generate a `pnpm-lock.yaml` file -Adding completion: --no-optional:`optionalDependencies` are not installed -Adding completion: --offline:Trigger an error if any required dependencies are not available in local store -Adding completion: --optimistic-repeat-install:Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store -Adding completion: --prefer-frozen-lockfile:If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation -Adding completion: --prefer-offline:Skip staleness checks for cached data, but request missing data from the server -Adding completion: --prod:Packages in `devDependencies` won't be installed pattern to the root of the modules directory -Adding completion: --recursive:Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" -Adding completion: --resolution-only:Re-runs resolution: useful for printing out peer dependency issues -Adding completion: --shamefully-hoist:All the subdeps will be hoisted into the root node_modules. Your code will have access to them -Adding completion: --side-effects-cache:Use or cache the results of (pre/post)install hooks -Adding completion: --side-effects-cache-readonly:Only use the side effects cache if present, do not create it for new packages are saved on the disk -Adding completion: --stream:Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. -Adding completion: --strict-peer-dependencies:Fail on missing or invalid peer dependencies -Adding completion: --use-running-store-server:Only allows installation with a store server. If no store server is running, installation will fail -Adding completion: --use-stderr:Divert all output to stderr -Adding completion: --use-store-server:Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory -Adding completion: --workspace-root:Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build -Adding completion: --fail-if-no-match:If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm -Calling _describe -_describe found some completions - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm insta -Truncated words[*]: pnpm insta, -lastParam: insta, lastChar: a -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- insta -completion output: install Install all dependencies for a project -install-test Runs a pnpm install followed immediately by a pnpm test -:4 -last line: :4 -directive: 4 -completions: install Install all dependencies for a project -install-test Runs a pnpm install followed immediately by a pnpm test -flagPrefix: -Adding completion: install:Install all dependencies for a project -Adding completion: install-test:Runs a pnpm install followed immediately by a pnpm test -Calling _describe -_describe found some completions - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install -- -Truncated words[*]: pnpm install --, -lastParam: --, lastChar: - -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install -- -completion output: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules ---dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) ---fix-lockfile Fix broken lockfile entries automatically ---force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) ---global-dir Specify a custom directory to store global packages ---help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules ---ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs ---ignore-scripts Don't run lifecycle scripts ---ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. ---lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. ---merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests ---no-hoist Dependencies inside the modules directory will have access only to their listed dependencies ---no-lockfile Don't read or generate a `pnpm-lock.yaml` file ---no-optional `optionalDependencies` are not installed ---offline Trigger an error if any required dependencies are not available in local store ---optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store ---prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation ---prefer-offline Skip staleness checks for cached data, but request missing data from the server ---prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory ---recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" ---resolution-only Re-runs resolution: useful for printing out peer dependency issues ---shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them ---side-effects-cache Use or cache the results of (pre/post)install hooks ---side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk ---stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. ---strict-peer-dependencies Fail on missing or invalid peer dependencies ---use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail ---use-stderr Divert all output to stderr ---use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory ---workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build ---fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm -:4 -last line: :4 -directive: 4 -completions: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules ---dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) ---fix-lockfile Fix broken lockfile entries automatically ---force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) ---global-dir Specify a custom directory to store global packages ---help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules ---ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs ---ignore-scripts Don't run lifecycle scripts ---ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. ---lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. ---merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests ---no-hoist Dependencies inside the modules directory will have access only to their listed dependencies ---no-lockfile Don't read or generate a `pnpm-lock.yaml` file ---no-optional `optionalDependencies` are not installed ---offline Trigger an error if any required dependencies are not available in local store ---optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store ---prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation ---prefer-offline Skip staleness checks for cached data, but request missing data from the server ---prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory ---recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" ---resolution-only Re-runs resolution: useful for printing out peer dependency issues ---shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them ---side-effects-cache Use or cache the results of (pre/post)install hooks ---side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk ---stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. ---strict-peer-dependencies Fail on missing or invalid peer dependencies ---use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail ---use-stderr Divert all output to stderr ---use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory ---workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build ---fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm -flagPrefix: -Adding completion: --aggregate-output:Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules -Adding completion: --dev:Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) -Adding completion: --fix-lockfile:Fix broken lockfile entries automatically -Adding completion: --force:Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) -Adding completion: --global-dir:Specify a custom directory to store global packages -Adding completion: --help:Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules -Adding completion: --ignore-pnpmfile:Disable pnpm hooks defined in .pnpmfile.cjs -Adding completion: --ignore-scripts:Don't run lifecycle scripts -Adding completion: --ignore-workspace:Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. -Adding completion: --lockfile-only:Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. -Adding completion: --merge-git-branch-lockfiles:Merge lockfiles were generated on git branch be installed (instead of node_modules) requests -Adding completion: --no-hoist:Dependencies inside the modules directory will have access only to their listed dependencies -Adding completion: --no-lockfile:Don't read or generate a `pnpm-lock.yaml` file -Adding completion: --no-optional:`optionalDependencies` are not installed -Adding completion: --offline:Trigger an error if any required dependencies are not available in local store -Adding completion: --optimistic-repeat-install:Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store -Adding completion: --prefer-frozen-lockfile:If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation -Adding completion: --prefer-offline:Skip staleness checks for cached data, but request missing data from the server -Adding completion: --prod:Packages in `devDependencies` won't be installed pattern to the root of the modules directory -Adding completion: --recursive:Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" -Adding completion: --resolution-only:Re-runs resolution: useful for printing out peer dependency issues -Adding completion: --shamefully-hoist:All the subdeps will be hoisted into the root node_modules. Your code will have access to them -Adding completion: --side-effects-cache:Use or cache the results of (pre/post)install hooks -Adding completion: --side-effects-cache-readonly:Only use the side effects cache if present, do not create it for new packages are saved on the disk -Adding completion: --stream:Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. -Adding completion: --strict-peer-dependencies:Fail on missing or invalid peer dependencies -Adding completion: --use-running-store-server:Only allows installation with a store server. If no store server is running, installation will fail -Adding completion: --use-stderr:Divert all output to stderr -Adding completion: --use-store-server:Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory -Adding completion: --workspace-root:Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build -Adding completion: --fail-if-no-match:If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm -Calling _describe -_describe found some completions - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm -Truncated words[*]: pnpm , -lastParam: , lastChar: -Adding extra empty parameter -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- '' '' -completion output: add Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency -import Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file -i Install all dependencies for a project -install Install all dependencies for a project -it Runs a pnpm install followed immediately by a pnpm test -install-test Runs a pnpm install followed immediately by a pnpm test -ln Connect the local project to another one -link Connect the local project to another one -prune Removes extraneous packages -rb Rebuild a package -rebuild Rebuild a package -rm Removes packages from node_modules and from the project's package.json -remove Removes packages from node_modules and from the project's package.json -unlink Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link -up Updates packages to their latest version based on the specified range -update Updates packages to their latest version based on the specified range -audit Checks for known security issues with the installed packages -licenses Check licenses in consumed packages -ls Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -list Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -outdated Check for outdated packages -exec Executes a shell command in scope of a project -run Runs a defined package script -start Runs an arbitrary command specified in the package's "start" property of its "scripts" object -t Runs a package's "test" script, if one was provided -test Runs a package's "test" script, if one was provided -cat-file Prints the contents of a file based on the hash value stored in the index file -cat-index Prints the index file of a specific package from the store -find-hash Experimental! Lists the packages that include the file with the specified hash. -pack Create a tarball from a package -publish Publishes a package to the registry -root Prints the effective modules directory -store Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store -:4 -last line: :4 -directive: 4 -completions: add Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency -import Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file -i Install all dependencies for a project -install Install all dependencies for a project -it Runs a pnpm install followed immediately by a pnpm test -install-test Runs a pnpm install followed immediately by a pnpm test -ln Connect the local project to another one -link Connect the local project to another one -prune Removes extraneous packages -rb Rebuild a package -rebuild Rebuild a package -rm Removes packages from node_modules and from the project's package.json -remove Removes packages from node_modules and from the project's package.json -unlink Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link -up Updates packages to their latest version based on the specified range -update Updates packages to their latest version based on the specified range -audit Checks for known security issues with the installed packages -licenses Check licenses in consumed packages -ls Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -list Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -outdated Check for outdated packages -exec Executes a shell command in scope of a project -run Runs a defined package script -start Runs an arbitrary command specified in the package's "start" property of its "scripts" object -t Runs a package's "test" script, if one was provided -test Runs a package's "test" script, if one was provided -cat-file Prints the contents of a file based on the hash value stored in the index file -cat-index Prints the index file of a specific package from the store -find-hash Experimental! Lists the packages that include the file with the specified hash. -pack Create a tarball from a package -publish Publishes a package to the registry -root Prints the effective modules directory -store Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store -flagPrefix: -Adding completion: add:Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency -Adding completion: import:Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file -Adding completion: i:Install all dependencies for a project -Adding completion: install:Install all dependencies for a project -Adding completion: it:Runs a pnpm install followed immediately by a pnpm test -Adding completion: install-test:Runs a pnpm install followed immediately by a pnpm test -Adding completion: ln:Connect the local project to another one -Adding completion: link:Connect the local project to another one -Adding completion: prune:Removes extraneous packages -Adding completion: rb:Rebuild a package -Adding completion: rebuild:Rebuild a package -Adding completion: rm:Removes packages from node_modules and from the project's package.json -Adding completion: remove:Removes packages from node_modules and from the project's package.json -Adding completion: unlink:Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link -Adding completion: up:Updates packages to their latest version based on the specified range -Adding completion: update:Updates packages to their latest version based on the specified range -Adding completion: audit:Checks for known security issues with the installed packages -Adding completion: licenses:Check licenses in consumed packages -Adding completion: ls:Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -Adding completion: list:Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -Adding completion: outdated:Check for outdated packages -Adding completion: exec:Executes a shell command in scope of a project -Adding completion: run:Runs a defined package script -Adding completion: start:Runs an arbitrary command specified in the package's "start" property of its "scripts" object -Adding completion: t:Runs a package's "test" script, if one was provided -Adding completion: test:Runs a package's "test" script, if one was provided -Adding completion: cat-file:Prints the contents of a file based on the hash value stored in the index file -Adding completion: cat-index:Prints the index file of a specific package from the store -Adding completion: find-hash:Experimental! Lists the packages that include the file with the specified hash. -Adding completion: pack:Create a tarball from a package -Adding completion: publish:Publishes a package to the registry -Adding completion: root:Prints the effective modules directory -Adding completion: store:Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store -Calling _describe -_describe found some completions - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm -Truncated words[*]: pnpm , -lastParam: , lastChar: -Adding extra empty parameter -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- '' '' -completion output: add Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency -import Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file -i Install all dependencies for a project -install Install all dependencies for a project -it Runs a pnpm install followed immediately by a pnpm test -install-test Runs a pnpm install followed immediately by a pnpm test -ln Connect the local project to another one -link Connect the local project to another one -prune Removes extraneous packages -rb Rebuild a package -rebuild Rebuild a package -rm Removes packages from node_modules and from the project's package.json -remove Removes packages from node_modules and from the project's package.json -unlink Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link -up Updates packages to their latest version based on the specified range -update Updates packages to their latest version based on the specified range -audit Checks for known security issues with the installed packages -licenses Check licenses in consumed packages -ls Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -list Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -outdated Check for outdated packages -exec Executes a shell command in scope of a project -run Runs a defined package script -start Runs an arbitrary command specified in the package's "start" property of its "scripts" object -t Runs a package's "test" script, if one was provided -test Runs a package's "test" script, if one was provided -cat-file Prints the contents of a file based on the hash value stored in the index file -cat-index Prints the index file of a specific package from the store -find-hash Experimental! Lists the packages that include the file with the specified hash. -pack Create a tarball from a package -publish Publishes a package to the registry -root Prints the effective modules directory -store Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store -:4 -last line: :4 -directive: 4 -completions: add Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency -import Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file -i Install all dependencies for a project -install Install all dependencies for a project -it Runs a pnpm install followed immediately by a pnpm test -install-test Runs a pnpm install followed immediately by a pnpm test -ln Connect the local project to another one -link Connect the local project to another one -prune Removes extraneous packages -rb Rebuild a package -rebuild Rebuild a package -rm Removes packages from node_modules and from the project's package.json -remove Removes packages from node_modules and from the project's package.json -unlink Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link -up Updates packages to their latest version based on the specified range -update Updates packages to their latest version based on the specified range -audit Checks for known security issues with the installed packages -licenses Check licenses in consumed packages -ls Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -list Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -outdated Check for outdated packages -exec Executes a shell command in scope of a project -run Runs a defined package script -start Runs an arbitrary command specified in the package's "start" property of its "scripts" object -t Runs a package's "test" script, if one was provided -test Runs a package's "test" script, if one was provided -cat-file Prints the contents of a file based on the hash value stored in the index file -cat-index Prints the index file of a specific package from the store -find-hash Experimental! Lists the packages that include the file with the specified hash. -pack Create a tarball from a package -publish Publishes a package to the registry -root Prints the effective modules directory -store Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store -flagPrefix: -Adding completion: add:Installs a package and any packages that it depends on. By default, any new package is installed as a prod dependency -Adding completion: import:Generates a pnpm-lock.yaml from an npm package-lock.json (or npm-shrinkwrap.json) file -Adding completion: i:Install all dependencies for a project -Adding completion: install:Install all dependencies for a project -Adding completion: it:Runs a pnpm install followed immediately by a pnpm test -Adding completion: install-test:Runs a pnpm install followed immediately by a pnpm test -Adding completion: ln:Connect the local project to another one -Adding completion: link:Connect the local project to another one -Adding completion: prune:Removes extraneous packages -Adding completion: rb:Rebuild a package -Adding completion: rebuild:Rebuild a package -Adding completion: rm:Removes packages from node_modules and from the project's package.json -Adding completion: remove:Removes packages from node_modules and from the project's package.json -Adding completion: unlink:Unlinks a package. Like yarn unlink but pnpm re-installs the dependency after removing the external link -Adding completion: up:Updates packages to their latest version based on the specified range -Adding completion: update:Updates packages to their latest version based on the specified range -Adding completion: audit:Checks for known security issues with the installed packages -Adding completion: licenses:Check licenses in consumed packages -Adding completion: ls:Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -Adding completion: list:Print all the versions of packages that are installed, as well as their dependencies, in a tree-structure -Adding completion: outdated:Check for outdated packages -Adding completion: exec:Executes a shell command in scope of a project -Adding completion: run:Runs a defined package script -Adding completion: start:Runs an arbitrary command specified in the package's "start" property of its "scripts" object -Adding completion: t:Runs a package's "test" script, if one was provided -Adding completion: test:Runs a package's "test" script, if one was provided -Adding completion: cat-file:Prints the contents of a file based on the hash value stored in the index file -Adding completion: cat-index:Prints the index file of a specific package from the store -Adding completion: find-hash:Experimental! Lists the packages that include the file with the specified hash. -Adding completion: pack:Create a tarball from a package -Adding completion: publish:Publishes a package to the registry -Adding completion: root:Prints the effective modules directory -Adding completion: store:Adds new packages to the pnpm store directly. Does not modify any projects or files outside the store -Calling _describe -_describe found some completions - -========= starting completion logic ========== -CURRENT: 2, words[*]: pnpm ins -Truncated words[*]: pnpm ins, -lastParam: ins, lastChar: s -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- ins -completion output: install Install all dependencies for a project -install-test Runs a pnpm install followed immediately by a pnpm test -:4 -last line: :4 -directive: 4 -completions: install Install all dependencies for a project -install-test Runs a pnpm install followed immediately by a pnpm test -flagPrefix: -Adding completion: install:Install all dependencies for a project -Adding completion: install-test:Runs a pnpm install followed immediately by a pnpm test -Calling _describe -_describe found some completions - -========= starting completion logic ========== -CURRENT: 3, words[*]: pnpm install -- -Truncated words[*]: pnpm install --, -lastParam: --, lastChar: - -About to call: eval node /Users/amir/Desktop/projects/tab/dist/bin/cli.js pnpm complete -- install -- -completion output: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules ---dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) ---fix-lockfile Fix broken lockfile entries automatically ---force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) ---global-dir Specify a custom directory to store global packages ---help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules ---ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs ---ignore-scripts Don't run lifecycle scripts ---ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. ---lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. ---merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests ---no-hoist Dependencies inside the modules directory will have access only to their listed dependencies ---no-lockfile Don't read or generate a `pnpm-lock.yaml` file ---no-optional `optionalDependencies` are not installed ---offline Trigger an error if any required dependencies are not available in local store ---optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store ---prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation ---prefer-offline Skip staleness checks for cached data, but request missing data from the server ---prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory ---recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" ---resolution-only Re-runs resolution: useful for printing out peer dependency issues ---shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them ---side-effects-cache Use or cache the results of (pre/post)install hooks ---side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk ---stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. ---strict-peer-dependencies Fail on missing or invalid peer dependencies ---use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail ---use-stderr Divert all output to stderr ---use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory ---workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build ---fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm -:4 -last line: :4 -directive: 4 -completions: --aggregate-output Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules ---dev Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) ---fix-lockfile Fix broken lockfile entries automatically ---force Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) ---global-dir Specify a custom directory to store global packages ---help Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules ---ignore-pnpmfile Disable pnpm hooks defined in .pnpmfile.cjs ---ignore-scripts Don't run lifecycle scripts ---ignore-workspace Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. ---lockfile-only Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. ---merge-git-branch-lockfiles Merge lockfiles were generated on git branch be installed (instead of node_modules) requests ---no-hoist Dependencies inside the modules directory will have access only to their listed dependencies ---no-lockfile Don't read or generate a `pnpm-lock.yaml` file ---no-optional `optionalDependencies` are not installed ---offline Trigger an error if any required dependencies are not available in local store ---optimistic-repeat-install Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store ---prefer-frozen-lockfile If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation ---prefer-offline Skip staleness checks for cached data, but request missing data from the server ---prod Packages in `devDependencies` won't be installed pattern to the root of the modules directory ---recursive Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" ---resolution-only Re-runs resolution: useful for printing out peer dependency issues ---shamefully-hoist All the subdeps will be hoisted into the root node_modules. Your code will have access to them ---side-effects-cache Use or cache the results of (pre/post)install hooks ---side-effects-cache-readonly Only use the side effects cache if present, do not create it for new packages are saved on the disk ---stream Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. ---strict-peer-dependencies Fail on missing or invalid peer dependencies ---use-running-store-server Only allows installation with a store server. If no store server is running, installation will fail ---use-stderr Divert all output to stderr ---use-store-server Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory ---workspace-root Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build ---fail-if-no-match If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm -flagPrefix: -Adding completion: --aggregate-output:Aggregate output from child processes that are run in parallel, and only print output when child process is finished. It makes reading large logs after running `pnpm recursive` with `--parallel` or with `--workspace-concurrency` much easier (especially on CI). Only `--reporter=append-only` is supported. run parallelly to build node modules -Adding completion: --dev:Only `devDependencies` are installed /Users/amir/Desktop/projects/tab) -Adding completion: --fix-lockfile:Fix broken lockfile entries automatically -Adding completion: --force:Force reinstall dependencies: refetch packages modified in store, recreate a lockfile and/or modules directory created by a non-compatible version of pnpm. Install all optionalDependencies even they don't satisfy the current environment(cpu, os, arch) -Adding completion: --global-dir:Specify a custom directory to store global packages -Adding completion: --help:Output usage information pattern to `node_modules/.pnpm/node_modules`. The default pattern is * and matches everything. Hoisted packages can be required by any dependencies, so it is an emulation of a flat node_modules -Adding completion: --ignore-pnpmfile:Disable pnpm hooks defined in .pnpmfile.cjs -Adding completion: --ignore-scripts:Don't run lifecycle scripts -Adding completion: --ignore-workspace:Ignore pnpm-workspace.yaml if exists in the parent directory, and treat the installation as normal non-workspace installation. pnpm-lock.yaml of the package will be created. Several projects may share a single lockfile. -Adding completion: --lockfile-only:Dependencies are not downloaded. Only `pnpm-lock.yaml` is updated at or higher than the given level will be shown. Levels (lowest to highest): debug, info, warn, error. Or use "--silent" to turn off all logging. -Adding completion: --merge-git-branch-lockfiles:Merge lockfiles were generated on git branch be installed (instead of node_modules) requests -Adding completion: --no-hoist:Dependencies inside the modules directory will have access only to their listed dependencies -Adding completion: --no-lockfile:Don't read or generate a `pnpm-lock.yaml` file -Adding completion: --no-optional:`optionalDependencies` are not installed -Adding completion: --offline:Trigger an error if any required dependencies are not available in local store -Adding completion: --optimistic-repeat-install:Skip reinstall if the workspace state is up-to-date selected method depends from the file system the store -Adding completion: --prefer-frozen-lockfile:If the available `pnpm-lock.yaml` satisfies the `package.json` then perform a headless installation -Adding completion: --prefer-offline:Skip staleness checks for cached data, but request missing data from the server -Adding completion: --prod:Packages in `devDependencies` won't be installed pattern to the root of the modules directory -Adding completion: --recursive:Run installation recursively in every package found in subdirectories. For options that may be used with `-r`, see "pnpm help recursive" -Adding completion: --resolution-only:Re-runs resolution: useful for printing out peer dependency issues -Adding completion: --shamefully-hoist:All the subdeps will be hoisted into the root node_modules. Your code will have access to them -Adding completion: --side-effects-cache:Use or cache the results of (pre/post)install hooks -Adding completion: --side-effects-cache-readonly:Only use the side effects cache if present, do not create it for new packages are saved on the disk -Adding completion: --stream:Stream output from child processes immediately, prefixed with the originating package directory. This allows output from different packages to be interleaved. -Adding completion: --strict-peer-dependencies:Fail on missing or invalid peer dependencies -Adding completion: --use-running-store-server:Only allows installation with a store server. If no store server is running, installation will fail -Adding completion: --use-stderr:Divert all output to stderr -Adding completion: --use-store-server:Starts a store server in the background. The store server will keep running after installation is done. To stop the store server, run `pnpm server stop` (default is node_modules/.pnpm). All direct and indirect dependencies of the project are linked into this directory -Adding completion: --workspace-root:Run the command on the root workspace project filtering for changed projects since the specified commit/branch. Usage example: pnpm pattern="**/README.md" build -Adding completion: --fail-if-no-match:If no projects are matched by the command, exit with exit code 1 (fail) \! in zsh), it means the packages matching the selector must be excluded. E.g., "pnpm packages except "foo" under the current working directory indirect dependents of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: ...^foo (...^^foo in Command Prompt) dependents of the matched packages. E.g.: ...foo, "...@bar/*" inside a given subdirectory. E.g.: ./components since the specified commit/branch. E.g.: "[master]", "[HEAD~2]". It may be used together with "...". So, for instance, "...[HEAD~1]" selects all packages changed in the last commit and their dependents under the specified directory. It may be used with "..." to select dependents/dependencies as well. It also may be combined with "[]". For instance, all changed projects inside a directory: "{packages}[origin/master]" names matching the given pattern. E.g.: foo, "@bar/*" dependencies of the matched packages. E.g.: foo... indirect dependencies of the matched packages without including the matched packages themselves. ^ must be doubled at the Windows Command Prompt. E.g.: foo^... (foo^^... in Command Prompt) names matching the given pattern similar to --filter, but it ignores devDependencies when searching for dependencies and dependents. Useful with the changed since filter. When selecting only changed packages and their dependent packages, the dependent packages will be ignored in case a package has changes only in tests. Usage example: pnpm -Calling _describe -_describe found some completions