@teambit/dependency-resolver 1.0.727 → 1.0.729

package/dist/dependency-resolver-workspace-config.d.ts

@@ -115,4 +115,5 @@ export interface DependencyResolverWorkspaceConfig {
      * set this to the desired range symbol.
      */
     componentRangePrefix?: ComponentRangePrefix;
+    externalPackageManager?: boolean;
 }

package/dist/dependency-resolver-workspace-config.js.map

@@ -1 +1 @@
-{"version":3,"names":[],"sources":["dependency-resolver-workspace-config.ts"],"sourcesContent":["import type { PeerDependencyRules } from '@pnpm/types';\nimport type { WorkspacePolicyConfigObject } from './policy';\nimport type { PackageImportMethod } from './package-manager';\n\nexport type NodeLinker = 'hoisted' | 'isolated';\n\nexport type ComponentRangePrefix = '~' | '^' | '+' | '-';\n\nexport interface DependencyResolverWorkspaceConfig {\n  policy: WorkspacePolicyConfigObject;\n  /**\n   * choose the package manager for Bit to use. you can choose between 'npm', 'yarn', 'pnpm'\n   * and 'librarian'. our recommendation is use 'librarian' which reduces package duplicates\n   * and totally removes the need of a 'node_modules' directory in your project.\n   */\n  packageManager?: string;\n\n  /**\n   * A proxy server for out going network requests by the package manager\n   * Used for both http and https requests (unless the httpsProxy is defined)\n   */\n  proxy?: string;\n\n  /**\n   * A proxy server for outgoing https requests by the package manager (fallback to proxy server if not defined)\n   * Use this in case you want different proxy for http and https requests.\n   */\n  httpsProxy?: string;\n\n  /**\n   * A path to a file containing one or multiple Certificate Authority signing certificates.\n   * allows for multiple CA's, as well as for the CA information to be stored in a file on disk.\n   */\n  ca?: string;\n\n  /**\n   * Whether or not to do SSL key validation when making requests to the registry via https\n   */\n  strictSsl?: string;\n\n  /**\n   * A client certificate to pass when accessing the registry. Values should be in PEM format (Windows calls it \"Base-64 encoded X.509 (.CER)\") with newlines replaced by the string \"\\n\". For example:\n   * cert=\"----BEGIN CERTIFICATE-----\\nXXXX\\nXXXX\\n-----END CERTIFICATE----\"\n   * It is not the path to a certificate file (and there is no \"certfile\" option).\n   */\n  cert?: string;\n\n  /**\n   * A client key to pass when accessing the registry. Values should be in PEM format with newlines replaced by the string \"\\n\". For example:\n   * key=\"----BEGIN PRIVATE KEY-----\\nXXXX\\nXXXX\\n-----END PRIVATE KEY----\"\n   * It is not the path to a key file (and there is no \"keyfile\" option).\n   */\n  key?: string;\n\n  /**\n   * A comma-separated string of domain extensions that a proxy should not be used for.\n   */\n  noProxy?: string;\n\n  /**\n   * The IP address of the local interface to use when making connections to the npm registry.\n   */\n  localAddress?: string;\n\n  /**\n   * How many times to retry if Bit fails to fetch from the registry.\n   */\n  fetchRetries?: number;\n\n  /*\n   * The exponential factor for retry backoff.\n   */\n  fetchRetryFactor?: number;\n\n  /*\n   * The minimum (base) timeout for retrying requests.\n   */\n  fetchRetryMintimeout?: number;\n\n  /*\n   * The maximum fallback timeout to ensure the retry factor does not make requests too long.\n   */\n  fetchRetryMaxtimeout?: number;\n\n  /*\n   * The maximum amount of time (in milliseconds) to wait for HTTP requests to complete.\n   */\n  fetchTimeout?: number;\n\n  /*\n   * The maximum number of connections to use per origin (protocol/host/port combination).\n   */\n  maxSockets?: number;\n\n  /*\n   * Controls the maximum number of HTTP(S) requests to process simultaneously.\n   */\n  networkConcurrency?: number;\n\n  /*\n   * Set the prefix to use when adding dependency to workspace.jsonc via bit install\n   * to lock version to exact version you can use empty string (default)\n   */\n  savePrefix?: string;\n\n  /*\n   * in case you want to disable this proxy set this config to false\n   *\n   */\n  installFromBitDevRegistry?: boolean;\n\n  /*\n   * map of extra arguments to pass to the configured package manager upon the installation\n   * of dependencies.\n   */\n  packageManagerArgs?: string[];\n\n  /*\n   * This field allows to instruct the package manager to override any dependency in the dependency graph.\n   * This is useful to enforce all your packages to use a single version of a dependency, backport a fix,\n   * or replace a dependency with a fork.\n   */\n  overrides?: Record<string, string>;\n\n  /**\n   * This is similar to overrides, but will only affect installation in capsules.\n   * In case overrides is configured and this not, the regular overrides will affect capsules as well.\n   * in case both configured, capsulesOverrides will be used for capsules, and overrides will affect the workspace.\n   */\n  capsulesOverrides?: Record<string, string>;\n\n  /*\n   * Defines what linker should be used for installing Node.js packages.\n   * Supported values are hoisted and isolated.\n   */\n  nodeLinker?: NodeLinker;\n\n  /*\n   * Controls the way packages are imported from the store.\n   */\n  packageImportMethod?: PackageImportMethod;\n\n  /*\n   * Use and cache the results of (pre/post)install hooks.\n   */\n  sideEffectsCache?: boolean;\n\n  /*\n   * The list of components that should be installed in isolation from the workspace.\n   * The component's package names should be used in this list, not their component IDs.\n   */\n  rootComponents?: boolean;\n\n  /*\n   * The node version to use when checking a package's engines setting.\n   */\n  nodeVersion?: string;\n\n  /*\n   * Refuse to install any package that claims to not be compatible with the current Node.js version.\n   */\n  engineStrict?: boolean;\n\n  /*\n   * Rules to mute specific peer dependeny warnings.\n   */\n  peerDependencyRules?: PeerDependencyRules;\n\n  /*\n   * This setting is \"true\" by default and tells bit to link core aspects to the node_modules of the workspace.\n   * It only makes sense to set this to \"false\" in a workspace in which core aspects are actually developed.\n   */\n  linkCoreAspects?: boolean;\n\n  /**\n   * When false, Bit will create a shared node_modules directory for all components in a capsule.\n   */\n  isolatedCapsules?: boolean;\n\n  /*\n   * Ignore the builds of specific dependencies. The \"preinstall\", \"install\", and \"postinstall\" scripts\n   * of the listed packages will not be executed during installation.\n   */\n  neverBuiltDependencies?: string[];\n\n  /**\n   * If true, staleness checks for cached data will be bypassed, but missing data will be requested from the server.\n   */\n  preferOffline?: boolean;\n\n  /**\n   * When true, components in capsules are symlinked into their own node_modules.\n   */\n  capsuleSelfReference?: boolean;\n\n  /**\n   * Tells pnpm which packages should be hoisted to node_modules/.pnpm/node_modules.\n   * By default, all packages are hoisted - however, if you know that only some flawed packages have phantom dependencies,\n   * you can use this option to exclusively hoist the phantom dependencies (recommended).\n   */\n  hoistPatterns?: string[];\n\n  /**\n   * When true, dependencies from the workspace are hoisted to node_modules/.pnpm/node_modules\n   * even if they are found in the root node_modules\n   */\n  hoistInjectedDependencies?: boolean;\n\n  /**\n   * Tells pnpm to automatically install peer dependencies. It is true by default.\n   */\n  autoInstallPeers?: boolean;\n\n  /**\n   * By default, Bit saves component dependencies with exact versions (pinned) in the package.json,\n   * even if the dependency-resolver policy specifies a version range.\n   *\n   * To preserve the range defined in the policy, set this value to \"+\".\n   * To apply a predefined range (\"~\" or \"^\") to other component dependencies not covered by the policy,\n   * set this to the desired range symbol.\n   */\n  componentRangePrefix?: ComponentRangePrefix;\n}\n"],"mappings":"","ignoreList":[]}
+{"version":3,"names":[],"sources":["dependency-resolver-workspace-config.ts"],"sourcesContent":["import type { PeerDependencyRules } from '@pnpm/types';\nimport type { WorkspacePolicyConfigObject } from './policy';\nimport type { PackageImportMethod } from './package-manager';\n\nexport type NodeLinker = 'hoisted' | 'isolated';\n\nexport type ComponentRangePrefix = '~' | '^' | '+' | '-';\n\nexport interface DependencyResolverWorkspaceConfig {\n  policy: WorkspacePolicyConfigObject;\n  /**\n   * choose the package manager for Bit to use. you can choose between 'npm', 'yarn', 'pnpm'\n   * and 'librarian'. our recommendation is use 'librarian' which reduces package duplicates\n   * and totally removes the need of a 'node_modules' directory in your project.\n   */\n  packageManager?: string;\n\n  /**\n   * A proxy server for out going network requests by the package manager\n   * Used for both http and https requests (unless the httpsProxy is defined)\n   */\n  proxy?: string;\n\n  /**\n   * A proxy server for outgoing https requests by the package manager (fallback to proxy server if not defined)\n   * Use this in case you want different proxy for http and https requests.\n   */\n  httpsProxy?: string;\n\n  /**\n   * A path to a file containing one or multiple Certificate Authority signing certificates.\n   * allows for multiple CA's, as well as for the CA information to be stored in a file on disk.\n   */\n  ca?: string;\n\n  /**\n   * Whether or not to do SSL key validation when making requests to the registry via https\n   */\n  strictSsl?: string;\n\n  /**\n   * A client certificate to pass when accessing the registry. Values should be in PEM format (Windows calls it \"Base-64 encoded X.509 (.CER)\") with newlines replaced by the string \"\\n\". For example:\n   * cert=\"----BEGIN CERTIFICATE-----\\nXXXX\\nXXXX\\n-----END CERTIFICATE----\"\n   * It is not the path to a certificate file (and there is no \"certfile\" option).\n   */\n  cert?: string;\n\n  /**\n   * A client key to pass when accessing the registry. Values should be in PEM format with newlines replaced by the string \"\\n\". For example:\n   * key=\"----BEGIN PRIVATE KEY-----\\nXXXX\\nXXXX\\n-----END PRIVATE KEY----\"\n   * It is not the path to a key file (and there is no \"keyfile\" option).\n   */\n  key?: string;\n\n  /**\n   * A comma-separated string of domain extensions that a proxy should not be used for.\n   */\n  noProxy?: string;\n\n  /**\n   * The IP address of the local interface to use when making connections to the npm registry.\n   */\n  localAddress?: string;\n\n  /**\n   * How many times to retry if Bit fails to fetch from the registry.\n   */\n  fetchRetries?: number;\n\n  /*\n   * The exponential factor for retry backoff.\n   */\n  fetchRetryFactor?: number;\n\n  /*\n   * The minimum (base) timeout for retrying requests.\n   */\n  fetchRetryMintimeout?: number;\n\n  /*\n   * The maximum fallback timeout to ensure the retry factor does not make requests too long.\n   */\n  fetchRetryMaxtimeout?: number;\n\n  /*\n   * The maximum amount of time (in milliseconds) to wait for HTTP requests to complete.\n   */\n  fetchTimeout?: number;\n\n  /*\n   * The maximum number of connections to use per origin (protocol/host/port combination).\n   */\n  maxSockets?: number;\n\n  /*\n   * Controls the maximum number of HTTP(S) requests to process simultaneously.\n   */\n  networkConcurrency?: number;\n\n  /*\n   * Set the prefix to use when adding dependency to workspace.jsonc via bit install\n   * to lock version to exact version you can use empty string (default)\n   */\n  savePrefix?: string;\n\n  /*\n   * in case you want to disable this proxy set this config to false\n   *\n   */\n  installFromBitDevRegistry?: boolean;\n\n  /*\n   * map of extra arguments to pass to the configured package manager upon the installation\n   * of dependencies.\n   */\n  packageManagerArgs?: string[];\n\n  /*\n   * This field allows to instruct the package manager to override any dependency in the dependency graph.\n   * This is useful to enforce all your packages to use a single version of a dependency, backport a fix,\n   * or replace a dependency with a fork.\n   */\n  overrides?: Record<string, string>;\n\n  /**\n   * This is similar to overrides, but will only affect installation in capsules.\n   * In case overrides is configured and this not, the regular overrides will affect capsules as well.\n   * in case both configured, capsulesOverrides will be used for capsules, and overrides will affect the workspace.\n   */\n  capsulesOverrides?: Record<string, string>;\n\n  /*\n   * Defines what linker should be used for installing Node.js packages.\n   * Supported values are hoisted and isolated.\n   */\n  nodeLinker?: NodeLinker;\n\n  /*\n   * Controls the way packages are imported from the store.\n   */\n  packageImportMethod?: PackageImportMethod;\n\n  /*\n   * Use and cache the results of (pre/post)install hooks.\n   */\n  sideEffectsCache?: boolean;\n\n  /*\n   * The list of components that should be installed in isolation from the workspace.\n   * The component's package names should be used in this list, not their component IDs.\n   */\n  rootComponents?: boolean;\n\n  /*\n   * The node version to use when checking a package's engines setting.\n   */\n  nodeVersion?: string;\n\n  /*\n   * Refuse to install any package that claims to not be compatible with the current Node.js version.\n   */\n  engineStrict?: boolean;\n\n  /*\n   * Rules to mute specific peer dependeny warnings.\n   */\n  peerDependencyRules?: PeerDependencyRules;\n\n  /*\n   * This setting is \"true\" by default and tells bit to link core aspects to the node_modules of the workspace.\n   * It only makes sense to set this to \"false\" in a workspace in which core aspects are actually developed.\n   */\n  linkCoreAspects?: boolean;\n\n  /**\n   * When false, Bit will create a shared node_modules directory for all components in a capsule.\n   */\n  isolatedCapsules?: boolean;\n\n  /*\n   * Ignore the builds of specific dependencies. The \"preinstall\", \"install\", and \"postinstall\" scripts\n   * of the listed packages will not be executed during installation.\n   */\n  neverBuiltDependencies?: string[];\n\n  /**\n   * If true, staleness checks for cached data will be bypassed, but missing data will be requested from the server.\n   */\n  preferOffline?: boolean;\n\n  /**\n   * When true, components in capsules are symlinked into their own node_modules.\n   */\n  capsuleSelfReference?: boolean;\n\n  /**\n   * Tells pnpm which packages should be hoisted to node_modules/.pnpm/node_modules.\n   * By default, all packages are hoisted - however, if you know that only some flawed packages have phantom dependencies,\n   * you can use this option to exclusively hoist the phantom dependencies (recommended).\n   */\n  hoistPatterns?: string[];\n\n  /**\n   * When true, dependencies from the workspace are hoisted to node_modules/.pnpm/node_modules\n   * even if they are found in the root node_modules\n   */\n  hoistInjectedDependencies?: boolean;\n\n  /**\n   * Tells pnpm to automatically install peer dependencies. It is true by default.\n   */\n  autoInstallPeers?: boolean;\n\n  /**\n   * By default, Bit saves component dependencies with exact versions (pinned) in the package.json,\n   * even if the dependency-resolver policy specifies a version range.\n   *\n   * To preserve the range defined in the policy, set this value to \"+\".\n   * To apply a predefined range (\"~\" or \"^\") to other component dependencies not covered by the policy,\n   * set this to the desired range symbol.\n   */\n  componentRangePrefix?: ComponentRangePrefix;\n\n  externalPackageManager?: boolean\n}\n"],"mappings":"","ignoreList":[]}

package/dist/{preview-1756159462281.js → preview-1756240845322.js}

@@ -1,5 +1,5 @@
-import * as compositions_0 from '/home/circleci/Library/Caches/Bit/capsules/8891be5ad/teambit.dependencies_dependency-resolver@1.0.727/dist/dependency-resolver.composition.js';
-import * as overview_0 from '/home/circleci/Library/Caches/Bit/capsules/8891be5ad/teambit.dependencies_dependency-resolver@1.0.727/dist/dependency-resolver.docs.mdx';
+import * as compositions_0 from '/home/circleci/Library/Caches/Bit/capsules/8891be5ad/teambit.dependencies_dependency-resolver@1.0.729/dist/dependency-resolver.composition.js';
+import * as overview_0 from '/home/circleci/Library/Caches/Bit/capsules/8891be5ad/teambit.dependencies_dependency-resolver@1.0.729/dist/dependency-resolver.docs.mdx';
 
 export const compositions = [compositions_0];
 export const overview = [overview_0];

package/package.json

@@ -1,12 +1,12 @@
 {
   "name": "@teambit/dependency-resolver",
-  "version": "1.0.727",
+  "version": "1.0.729",
   "homepage": "https://bit.cloud/teambit/dependencies/dependency-resolver",
   "main": "dist/index.js",
   "componentId": {
     "scope": "teambit.dependencies",
     "name": "dependency-resolver",
-    "version": "1.0.727"
+    "version": "1.0.729"
   },
   "dependencies": {
     "chalk": "4.1.2",
@@ -52,14 +52,14 @@
     "@teambit/component-issues": "0.0.162",
     "@teambit/component-package-version": "0.0.441",
     "@teambit/legacy-bit-id": "1.1.3",
-    "@teambit/toolbox.object.sorter": "0.0.2",
     "@teambit/legacy.consumer-config": "0.0.69",
     "@teambit/toolbox.crypto.sha1": "0.0.8",
-    "@teambit/component": "1.0.727",
-    "@teambit/envs": "1.0.727",
-    "@teambit/aspect-loader": "1.0.727",
-    "@teambit/objects": "0.0.234",
-    "@teambit/graphql": "1.0.727"
+    "@teambit/toolbox.object.sorter": "0.0.2",
+    "@teambit/component": "1.0.729",
+    "@teambit/envs": "1.0.729",
+    "@teambit/aspect-loader": "1.0.729",
+    "@teambit/objects": "0.0.236",
+    "@teambit/graphql": "1.0.729"
   },
   "devDependencies": {
     "@types/fs-extra": "9.0.7",