@pnpm/config.package-is-installable 1100.1.7 → 1100.2.0

package/CHANGELOG.md

@@ -1,5 +1,20 @@
 # @pnpm/package-is-installable
 
+## 1100.2.0
+
+### Minor Changes
+
+- Added the `forceIgnoresPlatform` setting. When it is `false`, `pnpm install --force` skips optional dependencies whose `os`, `cpu` or `libc` do not match the host instead of installing all of them. The default stays `true` [#6133](https://github.com/pnpm/pnpm/issues/6133).
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/cli.meta@1100.1.1
+  - @pnpm/core-loggers@1101.0.1
+  - @pnpm/engine.runtime.system-version@1100.0.12
+  - @pnpm/error@1100.2.0
+  - @pnpm/types@1102.1.1
+
 ## 1100.1.7
 
 ### Patch Changes

package/lib/index.d.ts

@@ -26,6 +26,26 @@ export declare function checkPackageInstallability(pkgId: string, pkg: Installab
     pnpmVersion?: string;
     supportedArchitectures?: SupportedArchitectures;
 }): null | UnsupportedEngineError | UnsupportedPlatformError;
+export interface ForcedInstallabilityOptions {
+    engineStrict: boolean;
+    /**
+     * Install every package the lockfile names, whatever its `os`, `cpu`,
+     * `libc` or `engines` say: the installability check is skipped entirely.
+     */
+    includeIncompatiblePackages: boolean;
+}
+/**
+ * How `--force` changes the installability check. It lifts `engineStrict`,
+ * as npm's does, so an `engines` mismatch on a required package warns
+ * instead of failing. Under `forceIgnoresPlatform` (the default) it also
+ * skips the check altogether, so optional dependencies for other platforms
+ * are installed instead of skipped.
+ */
+export declare function installabilityUnderForce(opts: {
+    engineStrict?: boolean;
+    force?: boolean;
+    forceIgnoresPlatform?: boolean;
+}): ForcedInstallabilityOptions;
 export declare function packageIsInstallable(pkgId: string, pkg: InstallabilityManifest, options: {
     engineStrict?: boolean;
     nodeVersion?: string;

package/lib/index.js

@@ -15,6 +15,20 @@ export { UnsupportedEngineError, UnsupportedPlatformError, };
 export function checkPackageInstallability(pkgId, pkg, options) {
     return checkPackage(pkgId, { engines: pkg.engines, ...effectivePlatform(pkg, options.optional) }, options);
 }
+/**
+ * How `--force` changes the installability check. It lifts `engineStrict`,
+ * as npm's does, so an `engines` mismatch on a required package warns
+ * instead of failing. Under `forceIgnoresPlatform` (the default) it also
+ * skips the check altogether, so optional dependencies for other platforms
+ * are installed instead of skipped.
+ */
+export function installabilityUnderForce(opts) {
+    const force = opts.force === true;
+    return {
+        engineStrict: opts.engineStrict === true && !force,
+        includeIncompatiblePackages: force && opts.forceIgnoresPlatform !== false,
+    };
+}
 export function packageIsInstallable(pkgId, pkg, options) {
     const warn = checkPackageInstallability(pkgId, pkg, options);
     if (warn == null)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pnpm/config.package-is-installable",
-  "version": "1100.1.7",
+  "version": "1100.2.0",
   "description": "Checks if a package is installable on the current system",
   "keywords": [
     "pnpm",
@@ -27,11 +27,11 @@
     "!*.map"
   ],
   "dependencies": {
-    "@pnpm/cli.meta": "1100.1.0",
-    "@pnpm/core-loggers": "1101.0.0",
-    "@pnpm/engine.runtime.system-version": "1100.0.11",
-    "@pnpm/error": "1100.1.4",
-    "@pnpm/types": "1102.1.0",
+    "@pnpm/cli.meta": "1100.1.1",
+    "@pnpm/core-loggers": "1101.0.1",
+    "@pnpm/engine.runtime.system-version": "1100.0.12",
+    "@pnpm/error": "1100.2.0",
+    "@pnpm/types": "1102.1.1",
     "detect-libc": "^2.1.2",
     "execa": "npm:safe-execa@0.3.0",
     "memoize": "^11.0.0",
@@ -42,7 +42,7 @@
   },
   "devDependencies": {
     "@jest/globals": "30.4.1",
-    "@pnpm/config.package-is-installable": "1100.1.7",
+    "@pnpm/config.package-is-installable": "1100.2.0",
     "@pnpm/logger": "1100.0.0",
     "@types/semver": "7.8.0"
   },