/** * JSON schema for pnpm-workspace.yaml files * * @schema PnpmWorkspaceYamlSchema */ export interface PnpmWorkspaceYamlSchema { /** * Workspace package paths. Glob patterns are supported * * @schema PnpmWorkspaceYamlSchema#packages */ readonly packages?: string[]; /** * Define dependency version ranges as reusable constants, * for later reference in package.json files. * This (singular) field creates a catalog named default. * * * @schema PnpmWorkspaceYamlSchema#catalog */ readonly catalog?: { [key: string]: string; }; /** * Define arbitrarily named catalogs * * @schema PnpmWorkspaceYamlSchema#catalogs */ readonly catalogs?: { [key: string]: { [key: string]: string; }; }; /** * Controlling if and how dependencies are added to the default catalog * * @schema PnpmWorkspaceYamlSchema#catalogMode */ readonly catalogMode?: PnpmWorkspaceYamlSchemaCatalogMode; /** * When set to `true`, pnpm will remove unused catalog entries during installation. * * @schema PnpmWorkspaceYamlSchema#cleanupUnusedCatalogs */ readonly cleanupUnusedCatalogs?: boolean; /** * When set to true, pnpm will remove unused catalog entries during installation. `cleanupUnusedCatalogs` is the deprecated spelling of this setting and continues to work; when both are set, `catalogPrune` wins. * * @schema PnpmWorkspaceYamlSchema#catalogPrune */ readonly catalogPrune?: boolean; /** * A list of package names that are allowed to be executed during installation. * * @schema PnpmWorkspaceYamlSchema#onlyBuiltDependencies */ readonly onlyBuiltDependencies?: string[]; /** * Used to override any dependency in the dependency graph. * * @schema PnpmWorkspaceYamlSchema#overrides */ readonly overrides?: any; /** * Used to extend the existing package definitions with additional information. * * @schema PnpmWorkspaceYamlSchema#packageExtensions */ readonly packageExtensions?: any; /** * Per-workspace-project pnpm settings that replace project-specific .npmrc files. * * @schema PnpmWorkspaceYamlSchema#packageConfigs */ readonly packageConfigs?: any; /** * @schema PnpmWorkspaceYamlSchema#peerDependencyRules */ readonly peerDependencyRules?: PnpmWorkspaceYamlSchemaPeerDependencyRules; /** * A list of dependencies to run builds for. * * @schema PnpmWorkspaceYamlSchema#neverBuiltDependencies */ readonly neverBuiltDependencies?: string[]; /** * If set to true, all build scripts (e.g. preinstall, install, postinstall) from dependencies will run automatically, without requiring approval. * * @schema PnpmWorkspaceYamlSchema#dangerouslyAllowAllBuilds */ readonly dangerouslyAllowAllBuilds?: boolean; /** * Specifies a JSON file that lists the only packages permitted to run installation scripts during the pnpm install process. * * @schema PnpmWorkspaceYamlSchema#onlyBuiltDependenciesFile */ readonly onlyBuiltDependenciesFile?: string; /** * A list of package names that should not be built during installation. * * @schema PnpmWorkspaceYamlSchema#ignoredBuiltDependencies */ readonly ignoredBuiltDependencies?: string[]; /** * A list of deprecated versions that the warnings are suppressed. * * @schema PnpmWorkspaceYamlSchema#allowedDeprecatedVersions */ readonly allowedDeprecatedVersions?: { [key: string]: string; }; /** * A list of dependencies that are patched. * * @schema PnpmWorkspaceYamlSchema#patchedDependencies */ readonly patchedDependencies?: { [key: string]: string; }; /** * When true, installation won't fail if some of the patches from the "patchedDependencies" field were not applied. (Previously named "allowNonAppliedPatches") * * @schema PnpmWorkspaceYamlSchema#allowUnusedPatches */ readonly allowUnusedPatches?: boolean; /** * When true, installation won't fail if some of the patches from the "patchedDependencies" field were not applied. * * @schema PnpmWorkspaceYamlSchema#allowNonAppliedPatches */ readonly allowNonAppliedPatches?: boolean; /** * Default is undefined. Errors out when a patch with an exact version or version range fails. Ignores failures from name-only patches. When true, prints a warning instead of failing when any patch cannot be applied. When false, errors out for any patch failure. * * @default undefined. Errors out when a patch with an exact version or version range fails. Ignores failures from name-only patches. When true, prints a warning instead of failing when any patch cannot be applied. When false, errors out for any patch failure. * @schema PnpmWorkspaceYamlSchema#ignorePatchFailures */ readonly ignorePatchFailures?: boolean; /** * @schema PnpmWorkspaceYamlSchema#update */ readonly update?: PnpmWorkspaceYamlSchemaUpdate; /** * @schema PnpmWorkspaceYamlSchema#updateConfig */ readonly updateConfig?: PnpmWorkspaceYamlSchemaUpdateConfig; /** * Config dependencies allow you to share and centralize configuration files, settings, and hooks across multiple projects. They are installed before all regular dependencies ('dependencies', 'devDependencies', 'optionalDependencies'), making them ideal for setting up custom hooks, patches, and catalog entries. * * @schema PnpmWorkspaceYamlSchema#configDependencies */ readonly configDependencies?: any; /** * @schema PnpmWorkspaceYamlSchema#audit */ readonly audit?: PnpmWorkspaceYamlSchemaAudit; /** * @schema PnpmWorkspaceYamlSchema#auditConfig */ readonly auditConfig?: PnpmWorkspaceYamlSchemaAuditConfig; /** * A list of scripts that must exist in each project. * * @schema PnpmWorkspaceYamlSchema#requiredScripts */ readonly requiredScripts?: string[]; /** * Specifies architectures for which you'd like to install optional dependencies, even if they don't match the architecture of the system running the install. * * @schema PnpmWorkspaceYamlSchema#supportedArchitectures */ readonly supportedArchitectures?: PnpmWorkspaceYamlSchemaSupportedArchitectures; /** * A list of optional dependencies that the install should be skipped. * * @schema PnpmWorkspaceYamlSchema#ignoredOptionalDependencies */ readonly ignoredOptionalDependencies?: string[]; /** * @schema PnpmWorkspaceYamlSchema#executionEnv */ readonly executionEnv?: PnpmWorkspaceYamlSchemaExecutionEnv; /** * When true, all dependencies are hoisted to node_modules/.pnpm/node_modules. * * @schema PnpmWorkspaceYamlSchema#hoist */ readonly hoist?: boolean; /** * When true, packages from the workspaces are symlinked to either /node_modules/.pnpm/node_modules or to /node_modules depending on other hoisting settings (hoistPattern and publicHoistPattern). * * @schema PnpmWorkspaceYamlSchema#hoistWorkspacePackages */ readonly hoistWorkspacePackages?: boolean; /** * Tells pnpm which packages should be hoisted to node_modules/.pnpm/node_modules * * @schema PnpmWorkspaceYamlSchema#hoistPattern */ readonly hoistPattern?: string[]; /** * Unlike hoistPattern, which hoists dependencies to a hidden modules directory inside the virtual store, publicHoistPattern hoists dependencies matching the pattern to the root modules directory. * * @schema PnpmWorkspaceYamlSchema#publicHoistPattern */ readonly publicHoistPattern?: string[]; /** * By default, pnpm creates a semistrict node_modules, meaning dependencies have access to undeclared dependencies but modules outside of node_modules do not. * * @schema PnpmWorkspaceYamlSchema#shamefullyHoist */ readonly shamefullyHoist?: boolean; /** * The directory in which dependencies will be installed (instead of node_modules). * * @schema PnpmWorkspaceYamlSchema#modulesDir */ readonly modulesDir?: string; /** * Defines what linker should be used for installing Node packages. * * @schema PnpmWorkspaceYamlSchema#nodeLinker */ readonly nodeLinker?: PnpmWorkspaceYamlSchemaNodeLinker; /** * When true, pnpm injects the generated node_modules/.package-map.json into pnpm-managed Node.js script environments by adding Node's --experimental-package-map option to NODE_OPTIONS. see https://pnpm.io/settings/node-modules#nodeexperimentalpackagemap * * @schema PnpmWorkspaceYamlSchema#nodeExperimentalPackageMap */ readonly nodeExperimentalPackageMap?: boolean; /** * Controls how node_modules/.package-map.json is generated. standard - only declared dependencies are available through the package map. loose - also maps packages that are reachable through the installed node_modules layout, which can allow undeclared hoisted dependencies to resolve. * * @schema PnpmWorkspaceYamlSchema#nodePackageMapType */ readonly nodePackageMapType?: PnpmWorkspaceYamlSchemaNodePackageMapType; /** * When symlink is set to false, pnpm creates a virtual store directory without any symlinks. It is a useful setting together with nodeLinker=pnp. * * @schema PnpmWorkspaceYamlSchema#symlink */ readonly symlink?: boolean; /** * When false, pnpm will not write any files to the modules directory (node_modules). * * @schema PnpmWorkspaceYamlSchema#enableModulesDir */ readonly enableModulesDir?: boolean; /** * The directory with links to the store. * * @schema PnpmWorkspaceYamlSchema#virtualStoreDir */ readonly virtualStoreDir?: string; /** * Sets the maximum allowed length of directory names inside the virtual store directory (node_modules/.pnpm). * * @schema PnpmWorkspaceYamlSchema#virtualStoreDirMaxLength */ readonly virtualStoreDirMaxLength?: number; /** * Determines where the virtual store is located. When set to project, a separate virtual store is created in each project's node_modules/.pnpm. When set to global, a single store is shared by every project on the machine, with each project's node_modules holding only symlinks into it. Added in pnpm v11.23.0. * * @schema PnpmWorkspaceYamlSchema#virtualStoreType */ readonly virtualStoreType?: PnpmWorkspaceYamlSchemaVirtualStoreType; /** * Controls the way packages are imported from the store (if you want to disable symlinks inside node_modules, then you need to change the nodeLinker setting, not this one). * * @schema PnpmWorkspaceYamlSchema#packageImportMethod */ readonly packageImportMethod?: PnpmWorkspaceYamlSchemaPackageImportMethod; /** * The time in minutes after which orphan packages from the modules directory should be removed. * * @schema PnpmWorkspaceYamlSchema#modulesCacheMaxAge */ readonly modulesCacheMaxAge?: number; /** * The time in minutes after which dlx cache expires. * * @schema PnpmWorkspaceYamlSchema#dlxCacheMaxAge */ readonly dlxCacheMaxAge?: number; /** * The location where all the packages are saved on the disk. * * @schema PnpmWorkspaceYamlSchema#storeDir */ readonly storeDir?: string; /** * By default, if a file in the store has been modified, the content of this file is checked before linking it to a project's node_modules. * * @schema PnpmWorkspaceYamlSchema#verifyStoreIntegrity */ readonly verifyStoreIntegrity?: boolean; /** * Deprecated. Only allows installation with a store server. If no store server is running, installation will fail. * * @schema PnpmWorkspaceYamlSchema#useRunningStoreServer */ readonly useRunningStoreServer?: boolean; /** * Makes pnpm install work against a read-only package store (such as a Nix store or OCI image layer). When enabled, pnpm opens the store's SQLite database in immutable mode and never writes to the store. Works best together with --offline and --frozen-lockfile; incompatible with --force. Added in pnpm v11.7.0. * * @schema PnpmWorkspaceYamlSchema#frozenStore */ readonly frozenStore?: boolean; /** * Some registries allow the exact same content to be published under different package names and/or versions. * * @schema PnpmWorkspaceYamlSchema#strictStorePkgContentCheck */ readonly strictStorePkgContentCheck?: boolean; /** * When enabled, node_modules contains only symlinks to a central virtual store, rather than to node_modules/.pnpm. * * @schema PnpmWorkspaceYamlSchema#enableGlobalVirtualStore */ readonly enableGlobalVirtualStore?: boolean; /** * When set to false, pnpm won't read or generate a pnpm-lock.yaml file. * * @schema PnpmWorkspaceYamlSchema#lockfile */ readonly lockfile?: boolean; /** * When set to true and the available pnpm-lock.yaml satisfies the package.json dependencies directive, a headless installation is performed. * * @schema PnpmWorkspaceYamlSchema#preferFrozenLockfile */ readonly preferFrozenLockfile?: boolean; /** * Add the full URL to the package's tarball to every entry in pnpm-lock.yaml. * * @schema PnpmWorkspaceYamlSchema#lockfileIncludeTarballUrl */ readonly lockfileIncludeTarballUrl?: boolean; /** * When set to true, the generated lockfile name after installation will be named based on the current branch name to completely avoid merge conflicts. * * @schema PnpmWorkspaceYamlSchema#gitBranchLockfile */ readonly gitBranchLockfile?: boolean; /** * This configuration matches the current branch name to determine whether to merge all git branch lockfile files. * * @schema PnpmWorkspaceYamlSchema#mergeGitBranchLockfilesBranchPattern */ readonly mergeGitBranchLockfilesBranchPattern?: any[]; /** * Max length of the peer IDs suffix added to dependency keys in the lockfile. If the suffix is longer, it is replaced with a hash. * * @schema PnpmWorkspaceYamlSchema#peersSuffixMaxLength */ readonly peersSuffixMaxLength?: number; /** * The base URL of the npm package registry (trailing slash included). * * @schema PnpmWorkspaceYamlSchema#registry */ readonly registry?: string; /** * The Certificate Authority signing certificate that is trusted for SSL connections to the registry. * * @schema PnpmWorkspaceYamlSchema#ca */ readonly ca?: string; /** * A path to a file containing one or multiple Certificate Authority signing certificates. * * @schema PnpmWorkspaceYamlSchema#cafile */ readonly cafile?: string; /** * A client certificate to pass when accessing the registry. * * @schema PnpmWorkspaceYamlSchema#cert */ readonly cert?: string; /** * A client key to pass when accessing the registry. * * @schema PnpmWorkspaceYamlSchema#key */ readonly key?: string; /** * When fetching dependencies that are Git repositories, if the host is listed in this setting, pnpm will use shallow cloning to fetch only the needed commit, not all the history. * * @schema PnpmWorkspaceYamlSchema#gitShallowHosts */ readonly gitShallowHosts?: string[]; /** * A proxy to use for outgoing HTTPS requests. If the HTTPS_PROXY, https_proxy, HTTP_PROXY or http_proxy environment variables are set, their values will be used instead. * * @schema PnpmWorkspaceYamlSchema#httpsProxy */ readonly httpsProxy?: string; /** * A proxy to use for outgoing HTTP requests. If the HTTP_PROXY or http_proxy environment variables are set, proxy settings will be honored by the underlying request library. * * @schema PnpmWorkspaceYamlSchema#httpProxy */ readonly httpProxy?: string; /** * npm's legacy proxy setting, used as the fallback for both httpsProxy and httpProxy. If the HTTP_PROXY or http_proxy environment variables are set, proxy settings will be honored by the underlying request library. * * @schema PnpmWorkspaceYamlSchema#proxy */ readonly proxy?: string; /** * The IP address of the local interface to use when making connections to the npm registry. * * @schema PnpmWorkspaceYamlSchema#localAddress */ readonly localAddress?: string; /** * The maximum number of connections to use per origin (protocol/host/port combination). * * @schema PnpmWorkspaceYamlSchema#maxsockets */ readonly maxsockets?: number; /** * A comma-separated string of domain extensions that a proxy should not be used for. * * @schema PnpmWorkspaceYamlSchema#noProxy */ readonly noProxy?: string; /** * Whether or not to do SSL key validation when making requests to the registry via HTTPS. * * @schema PnpmWorkspaceYamlSchema#strictSsl */ readonly strictSsl?: boolean; /** * Controls the maximum number of HTTP(S) requests to process simultaneously. * * @schema PnpmWorkspaceYamlSchema#networkConcurrency */ readonly networkConcurrency?: number; /** * How many times to retry if pnpm fails to fetch from the registry. * * @schema PnpmWorkspaceYamlSchema#fetchRetries */ readonly fetchRetries?: number; /** * The exponential factor for retry backoff. * * @schema PnpmWorkspaceYamlSchema#fetchRetryFactor */ readonly fetchRetryFactor?: number; /** * The minimum (base) timeout for retrying requests. * * @schema PnpmWorkspaceYamlSchema#fetchRetryMintimeout */ readonly fetchRetryMintimeout?: number; /** * The maximum fallback timeout to ensure the retry factor does not make requests too long. * * @schema PnpmWorkspaceYamlSchema#fetchRetryMaxtimeout */ readonly fetchRetryMaxtimeout?: number; /** * The maximum amount of time to wait for HTTP requests to complete. * * @schema PnpmWorkspaceYamlSchema#fetchTimeout */ readonly fetchTimeout?: number; /** * A warning message is displayed if a metadata request to the registry takes longer than the specified threshold (in milliseconds). Added in pnpm v10.18.0. * * @schema PnpmWorkspaceYamlSchema#fetchWarnTimeoutMs */ readonly fetchWarnTimeoutMs?: number; /** * A warning message is displayed if the download speed of a tarball from the registry falls below the specified threshold (in KiB/s). Added in pnpm v10.18.0. * * @schema PnpmWorkspaceYamlSchema#fetchMinSpeedKiBps */ readonly fetchMinSpeedKiBps?: number; /** * When true, any missing non-optional peer dependencies are automatically installed. * * @schema PnpmWorkspaceYamlSchema#autoInstallPeers */ readonly autoInstallPeers?: boolean; /** * When this setting is set to true, packages with peer dependencies will be deduplicated after peers resolution. * * @schema PnpmWorkspaceYamlSchema#dedupePeerDependents */ readonly dedupePeerDependents?: boolean; /** * If this is enabled, commands will fail if there is a missing or invalid peer dependency in the tree. * * @schema PnpmWorkspaceYamlSchema#strictPeerDependencies */ readonly strictPeerDependencies?: boolean; /** * When enabled, dependencies of the root workspace project are used to resolve peer dependencies of any projects in the workspace. * * @schema PnpmWorkspaceYamlSchema#resolvePeersFromWorkspaceRoot */ readonly resolvePeersFromWorkspaceRoot?: boolean; /** * Controls colors in the output. * * @schema PnpmWorkspaceYamlSchema#color */ readonly color?: PnpmWorkspaceYamlSchemaColor; /** * Any logs at or higher than the given level will be shown. * * @schema PnpmWorkspaceYamlSchema#loglevel */ readonly loglevel?: PnpmWorkspaceYamlSchemaLoglevel; /** * Allows you to customize the output style of the logs. * https://pnpm.io/cli/install#--reportername * * @schema PnpmWorkspaceYamlSchema#reporter */ readonly reporter?: PnpmWorkspaceYamlSchemaReporter; /** * Experimental option that enables beta features of the CLI. * * @schema PnpmWorkspaceYamlSchema#useBetaCli */ readonly useBetaCli?: boolean; /** * If this is enabled, the primary behaviour of pnpm install becomes that of pnpm install -r, meaning the install is performed on all workspace or subdirectory packages. * * @schema PnpmWorkspaceYamlSchema#recursiveInstall */ readonly recursiveInstall?: boolean; /** * If this is enabled, pnpm will not install any package that claims to not be compatible with the current Node version. * * @schema PnpmWorkspaceYamlSchema#engineStrict */ readonly engineStrict?: boolean; /** * The location of the npm binary that pnpm uses for some actions, like publishing. * * @schema PnpmWorkspaceYamlSchema#npmPath */ readonly npmPath?: string; /** * If this setting is disabled, pnpm will not fail if a different package manager is specified in the packageManager field of package.json. When enabled, only the package name is checked (since pnpm v9.2.0), so you can still run any version of pnpm regardless of the version specified in the packageManager field. * * @schema PnpmWorkspaceYamlSchema#packageManagerStrict */ readonly packageManagerStrict?: boolean; /** * When enabled, pnpm will fail if its version doesn't exactly match the version specified in the packageManager field of package.json. * * @schema PnpmWorkspaceYamlSchema#packageManagerStrictVersion */ readonly packageManagerStrictVersion?: boolean; /** * When enabled, pnpm will automatically download and run the version of pnpm specified in the packageManager field of package.json. * * @schema PnpmWorkspaceYamlSchema#managePackageManagerVersions */ readonly managePackageManagerVersions?: boolean; /** * Do not execute any scripts defined in the project package.json and its dependencies. * * @schema PnpmWorkspaceYamlSchema#ignoreScripts */ readonly ignoreScripts?: boolean; /** * Do not execute any scripts of the installed packages. Scripts of the projects are executed. * * @schema PnpmWorkspaceYamlSchema#ignoreDepScripts */ readonly ignoreDepScripts?: boolean; /** * The maximum number of child processes to allocate simultaneously to build node_modules. * * @schema PnpmWorkspaceYamlSchema#childConcurrency */ readonly childConcurrency?: number; /** * Use and cache the results of (pre/post)install hooks. * When a pre/post install script modify the contents of a package (e.g. build output), pnpm saves the modified package in the global store. On future installs on the same machine, pnpm reuses this cached, prebuilt version. * An object is the canonical way to declare the remote tier; `sideEffectsCache: true` is the shorthand for reading and writing. * * @schema PnpmWorkspaceYamlSchema#sideEffectsCache */ readonly sideEffectsCache?: any; /** * Only use the side effects cache if present, do not create it for new packages. The older spelling of sideEffectsCache: { read: true, write: false }. * * @schema PnpmWorkspaceYamlSchema#sideEffectsCacheReadonly */ readonly sideEffectsCacheReadonly?: boolean; /** * Set to true to enable UID/GID switching when running package scripts. If set explicitly to false, then installing as a non-root user will fail. * * @schema PnpmWorkspaceYamlSchema#unsafePerm */ readonly unsafePerm?: boolean; /** * Options to pass through to Node.js via the NODE_OPTIONS environment variable. * * @schema PnpmWorkspaceYamlSchema#nodeOptions */ readonly nodeOptions?: string; /** * This setting allows the checking of the state of dependencies before running scripts. * * @schema PnpmWorkspaceYamlSchema#verifyDepsBeforeRun */ readonly verifyDepsBeforeRun?: any; /** * When strictDepBuilds is enabled, the installation will exit with a non-zero exit code if any dependencies have unreviewed build scripts (aka postinstall scripts). * * @schema PnpmWorkspaceYamlSchema#strictDepBuilds */ readonly strictDepBuilds?: boolean; /** * Specifies which exact Node.js version should be used for the project's runtime. * * @schema PnpmWorkspaceYamlSchema#useNodeVersion */ readonly useNodeVersion?: string; /** * The Node.js version to use when checking a package's engines setting. * * @schema PnpmWorkspaceYamlSchema#nodeVersion */ readonly nodeVersion?: string; /** * If this is enabled, locally available packages are linked to node_modules instead of being downloaded from the registry. * * @schema PnpmWorkspaceYamlSchema#linkWorkspacePackages */ readonly linkWorkspacePackages?: PnpmWorkspaceYamlSchemaLinkWorkspacePackages; /** * Enables hard-linking of all local workspace dependencies instead of symlinking them. * * @schema PnpmWorkspaceYamlSchema#injectWorkspacePackages */ readonly injectWorkspacePackages?: boolean; /** * Injected workspace dependencies are collections of hardlinks, which don't add or remove the files when their sources change. * * @schema PnpmWorkspaceYamlSchema#syncInjectedDepsAfterScripts */ readonly syncInjectedDepsAfterScripts?: string[]; /** * If this is enabled, local packages from the workspace are preferred over packages from the registry, even if there is a newer version of the package in the registry. * * @schema PnpmWorkspaceYamlSchema#preferWorkspacePackages */ readonly preferWorkspacePackages?: boolean; /** * If this is enabled, pnpm creates a single pnpm-lock.yaml file in the root of the workspace. * * @schema PnpmWorkspaceYamlSchema#sharedWorkspaceLockfile */ readonly sharedWorkspaceLockfile?: boolean; /** * This setting controls how dependencies that are linked from the workspace are added to package.json. * * @schema PnpmWorkspaceYamlSchema#saveWorkspaceProtocol */ readonly saveWorkspaceProtocol?: PnpmWorkspaceYamlSchemaSaveWorkspaceProtocol; /** * When executing commands recursively in a workspace, execute them on the root workspace project as well. * * @schema PnpmWorkspaceYamlSchema#includeWorkspaceRoot */ readonly includeWorkspaceRoot?: boolean; /** * When set to true, no workspace cycle warnings will be printed. * * @schema PnpmWorkspaceYamlSchema#ignoreWorkspaceCycles */ readonly ignoreWorkspaceCycles?: boolean; /** * Adding a new dependency to the root workspace package fails, unless the --ignore-workspace-root-check or -w flag is used. * * @schema PnpmWorkspaceYamlSchema#ignoreWorkspaceRootCheck */ readonly ignoreWorkspaceRootCheck?: boolean; /** * When set to true, installation will fail if the workspace has cycles. * * @schema PnpmWorkspaceYamlSchema#disallowWorkspaceCycles */ readonly disallowWorkspaceCycles?: boolean; /** * Set the maximum number of tasks to run simultaneously. For unlimited concurrency use Infinity. You can set the value to <= 0 and it will use amount of CPU cores of the host minus the absolute value of the provided number as: max(1, (number of cores) - abs(workspaceConcurrency)). * * @schema PnpmWorkspaceYamlSchema#workspaceConcurrency */ readonly workspaceConcurrency?: number; /** * Configure dependency relationships and per-task concurrency limits for recursive runs (`pnpm -r run